StorNext: Added Tapes Are Moved to Scratch

StorNext: Added Tapes Are Moved to Scratch


Symptom:
Tapes added are moved to scratch.

Cause:
When media is cleaned using the fsclean command, it is returned to the general scratch pool in the system. This is the default behavior for StorNext. If the customer uses specific barcodes to separate stored data for different end users/policies or controls, media allocation based on these barcodes (such as Sony data) is kept in its own class, with barcodes beginning with 's'.

You can modify this default behavior to ensure that cleaned media will be reused by the correct policy.

Action:
To change the default behavior, edit the following parameter in the fs_sysparm configuration file (/usr/adic/TSM/config/fs_sysparm_override):

#CLASS_MEDIA_CLEANUP : Default media cleanup action (C or S).
# When a medium becomes logically blank,
# the medium may return to the class blank
# media pool (C) or to the system blank
# media pool (S).
CLASS_MEDIA_CLEANUP=S;

Change CLASS_MEDIA_CLEANUP=S to CLASS_MEDIA_CLEANUP=C. Cleaned media will then remain in the Policy Class and will not be placed in the scratch pool. The file /usr/adic/TSM/config/fs_sysparm.README describes each of the values.

Note: Changes made to the fs_sysparm file should be placed in the fs_sysparm.OVERRIDE file. On startup, TSM reads fs_sysparm and then applies any changes made in fs_sysparm.OVERRIDE. Parameters that may be modified are found in fs_sysparm.README.

KEYWORDS: SNSM, TSM, SN5, SN4, SN3

Audience: 
Public Unrestricted
Review/Evaluate: 
2016-02-23
Document Type: