Tools > Storage Manager > Media Actions
The Tools menu's Media Actions option enables you to perform various actions on the storage media in your library.
To access the Tools > Storage Manager > Media Actions page, choose Media Actions from the Tools > Storage Manager menu.
Imagine a case where a tape is holding the first segments of 20 files. Each of those 20 files contain 12 segments that collectively span 100 different tapes. If you export that tape as ANTF, does StorNext instantly grab and try to load all those tapes or does it grab just the first 12 that make up the first file?
All source tapes are marked as EXPORT to avoid them being used for any other purposes while the export process is underway. However, the source tapes are processed one at a time. The export operation uses at most two tape drives at any given time, one for the source tape and one for the destination tape.
Export has two primary modes of operation:
- Export
- Export Copy
Assume this is an Export Copy scenario in which you want the export process to make copies of tapes and export those copies (retaining the original tapes in the system).
For the case in which you identify one tape you wish to copy-export, the export process discovers all the files that reside on that tape and identifies segments of those files that reside on other tapes. It then determines if all the necessary tapes have been listed as part of the export command to account for all segments. If it determines that not all tapes have been listed, it ends prematurely and inform you of the necessary media IDs that need to be included in the command.
Unfortunately, this can result in a cascading effect because as you add media IDs to the list, the files for those media are also checked to make sure all segments on other tapes are accounted for.
There is a way to avoid this cascading effect. In addition to supporting the export of data on a media ID basis, the fsexport command supports exporting data on a file name basis. You can specify a list of files or directories to copy-export. When run in this manner, the export process finds all the media on which the file segments reside and copy only the specified files to new tapes. Those copies are exported.
If I update the segment size in the fs_sysparm_override file, does the export process use the new segment size?
No, the new segment size does not have an effect on the export process. The export process uses the segment size of the source file when it copies the data.
Are all versions of a file be exported?
If there are multiple versions of a file, only the most recent version is copied and exported.
Is there a way to know ahead of time how many tapes are required when files are segmented across several different tapes?
The fsexport command does support a report mode, but it only lists the files that would be exported. Currently, it does not specify all the media IDs that are needed to complete the segments.
How are all the needed tapes flagged in the export process?
All the source tapes that are needed and all the destination tapes that are selected are marked as EXPORT to avoid them being used for any other purposes while the export process is underway. The EXPORT flag is removed from each source tape after it is processed.
What does the import at the destination site look like for segmented files?
The export process generates a manifest file for each tape that is exported. These manifest files assist fsimport in reconciling all the segments for the files. If there are any media IDs unaccounted for, the fsimport process informs you. Without the manifest file, the fsimport process cannot reconcile file segments residing on separate tapes, and the import process fails to import files that have missing segments.
Does the export process write out the manifest file to go along with the new tape it creates?
Yes, the export process generates a manifest file for every new tape it creates; it generates a manifest file for every tape that is exported out of the system, whether it is a tape copy that it creates (Export Copy scenario) or an original source tape that is exported (Export scenario).
You can find the manifest files at:
Which version of StorNext supports these manifest files?
The media manifest files are supported beginning with the StorNext 6.2.0 release, as part of the ANTF Export/Import feature enhancement.
Assuming you have segmented files and wants to perform an Export Copy operation on the command line using fsexport with a batch file, does the operation also generate the necessary manifest files so that the destination site can perform the import?
Yes, for every flavor of fsexport (except report mode), a manifest file is created for every tape that is exported out of the system.
Note: After the fsexport process completes, you must use the StorNext Library Operator Interface to physically move the media to the tape library's I/E port.
After you choose the Media Actions option, the following information about all of the storage media appears:
-
Media ID: The unique identifier for the media
-
Library: The name of the library in which the media currently resides
-
Media Type: The type of media
-
Media Format: The format of the media
-
Formatted: Displays whether the media is formatted (true if the media is formatted, or false if the media is not formatted).
-
Status: Displays the status of the media.
-
Media Class: The media class to which the media belongs
-
Policy Class: The policy class to which the media belongs
-
Mark Status: Displays whether the media is marked or unmarked.
-
Suspectt: Indicates whether the media is considered suspect (possibly unreliable or defective)
-
Write Protected: Indicates whether the media is write protected
-
File Segment Count: The number of files saved on the media
-
% Used: Indicates the percentage of the media which is currently used
-
Copy: Indicates the policy class copy number on the media
-
Mounted in Drive: Indicates whether the media is currently mounted in a drive
-
Last Accessed: Indicates the date and time when the media was last accessed
Most Media Actions screens contain a filtering feature that allows you to restrict the available media to those whose media ID match the string you specify. Follow these steps to filter media:
-
At the Media ID Filter field, enter the string you want all available media IDs to match. Wildcards can be used in the string.
-
Click Set Filter.
-
Click Refresh to update the list of available media. Only media whose IDs match the string you entered will be shown.
-
To reset the filter string, click Clear Filter. If desired, repeat steps 1 - 3 to use a new filter string.
At the top of the page is a drop-down list of actions you can perform for selected media. First choose one of these options from the Available Actions list. After the desired action is selected, a new page appears displaying the necessary information to perform the action.
Select this option to add media to a library via bulk loading. Before running this action, you must first add the new media into the desired library through a manual process. The media must be inserted through internal slots, not into the mailbox. (That is, you must open the library door and put new media in the internal slots, close the library, allow it to do an audit, and then run this action.)
-
Select from the Library drop-down list the library into which you want to bulk load media.
-
Click Apply.
-
When the confirmation message appears, click Yes to proceed, or No to abort.
Select this option to add media through a library mailbox. Depending on how your library works, you may need to manually load media into the library mailbox prior to running this action. Or, after running this action you may be prompted to load media into the mailbox. This action is library dependent.
-
In the Library list, select the library into which you want to add a media mailbox.
-
In the Add Media Mailbox Parameters section, select the Port from the list.
-
Click Apply.
-
When the confirmation message appears, click Yes to proceed, or No to abort.
-
When a message informs you that the operation was successful, click OK.
After you see this message you are ready to load media through the library mailbox. If an error message appears and indicates "Failed to import Media from Mailbox", the new media needs to be inserted into the mailbox prior to running this action. Click OK, add new media to the mailbox, and rerun this action.
If a message informs you that the operation was successful, click OK. After you see this message you are ready to load media into the library mailbox.
Select this option to assign media to a previously created policy class. This media action operates only on media that is currently blank, whether it is assigned to a policy class or is scratch. All media that contain data are filtered from this action.
-
Select one or more media to assign, or check the box to the left of the Media ID heading to assign all media.
-
Select from the Destination Policy Class drop-down list the policy class to which you want to assign the selected media.
-
Click Apply.
-
When the confirmation message appears, click Yes to assign the selected media, or No to abort.
Select this option if you want to select media for cleaning based on the file system with which media are associated. When you run this function, the StorNext Storage Manager removes from the file system inactive files that have not been accessed since the specified endtime. This process does not affect current file versions on the media. Periodic cleaning helps prevent inactive information from growing to an unmanageable size.
Caution: Inactive file versions cleaned from the media cannot be recovered or used again.
-
Select from the Managed and Mounted File Systems drop-down list the file system to be cleaned.
-
At the End Time field, enter the date and time you want the cleaning process to stop. The default is the current date and time.
-
Click Apply.
-
When the confirmation message appears, click Yes to begin cleaning media, or No to abort.
Select this option if you want to select media for cleaning based on media ID. When you run this function, the StorNext Storage Manager removes inactive files from the media that have not been accessed since the specified end time. This process does not affect current file versions on the media. Periodic cleaning helps prevent inactive information from growing to an unmanageable size.
Caution: Inactive file versions cleaned from the media cannot be recovered or used again.
-
Select one or more media you want to clean, or check the box to the left of the Media ID heading to select all media.
-
At the End Time field, enter the date and time you want the cleaning process to stop. The default is the current date and time.
-
Click Apply.
-
When the confirmation message appears, click Yes to begin cleaning media, or No to abort.
Select this option if you want to select media for cleaning based on the policy class with which media are associated. When you select this option all media on the selected file system are cleaned. When you run this function, the StorNext Storage Manager removes inactive files associated with the selected policy class that have not been accessed since the specified end time. This process does not affect current file versions on the media. Periodic cleaning helps prevent inactive information from growing to an unmanageable size.
Caution: Inactive file versions cleaned from the media cannot be recovered or used again.
-
Select from the Policy Classes drop-down list the policy class whose media you want to clean.
-
At the End Time field, enter the date and time when you want the cleaning processing to stop. The default is the current date and time.
-
Click Apply.
-
When the confirmation message appears, click Yes to begin cleaning media, or No to abort.
Select this option to manually dismount a piece of previously mounted media from a drive.
-
Select the media you want to dismount.
-
Click Apply.
-
When the confirmation message appears, click Yes to dismount the media, or No to abort.
Select this option to export storage media that contain file data from the Tertiary Manager system. After performing this action, the media can be physically removed either by using Media Manager commands or by using the Library Operator Interface (LOI) in the StorNext GUI. Once media are exported from one Tertiary Manager system, they may be imported into another Tertiary Manager system using the Import Media action.
As part of the export process, the Export Media action also provides the option to automatically remove any non-truncated files from disk if the exported media represents the only existing copies of those files. Once the export process completes successfully, any exported media cease to be known to the Tertiary Manager system.
The Export Media action generates a manifest file for each media that is exported. These manifest files are used by the Import Media action to aid in the import process. A listing of the manifest files can be found in the Media Manifests panel in the StorNext GUI. By default, the manifest files are deposited in the /usr/adic/TSM/internal/manifests directory. It is your responsibility to manage and remove any files from this directory as needed.
-
Select the media you want to export.
-
(Optional) Click Remove Resident (Non-truncated) Disk Files to remove non-truncated files on the file system from the media.
Caution: Use caution when selecting this option as data loss may occur. Files on this media that do not have existing copies on other media are removed from the disk, whether they are truncated or not.
-
Click Apply.
-
When the confirmation message appears, click Yes to export the media, or No to abort.
Select this option to export a copy of each media. The Tertiary Manager system mounts the media, copies all active file versions from each source media to a destination media, unmounts the media, and exports all destination media from the system. After performing this action, the media can be physically removed either by using Media Manager commands or by using the Library Operator Interface (LOI) in the StorNext GUI. Once media are exported from one Tertiary Manager system, they may be imported into another Tertiary Manager system using the Import Media action.
Note: Currently the Tertiary Manager system does not support LTFS segmented files. Therefore, any multiple-segment files residing on ANTF source media cannot be exported to LTFS destination media.
- The source media may be in either LTFS or ANTF format.
- You can select a specific destination media instead of blank media for export.
- The source media will remain within TSM.
- The exported media will not contain any inactive file copy versions.
- For each file on each source media, files will not be removed from the file system, whether they are truncated or not.
The Export Copy of Media action will generate a manifest file for each media that is exported. These manifest files are used by the Import Media action to aid in the import process. A listing of the manifest files can be found in the Media Manifests panel in the StorNext GUI. By default, the manifest files are deposited in the /usr/adic/TSM/internal/manifests directory. It is your responsibility to manage and remove any files from this directory as needed.
-
Select the media you want to export as a copy.
- (Optional) Select Copy Equivalent to create a one-to-one copy of the media when exporting multiple media. If you select this option, the Destination Media option becomes disabled.
-
Select Destination Media Format as either ANTF or LTFS.
-
Select the Destination Media, either Any Available Blank LTO Media or Specific LTO Media.
- If available, select the Destination Media ID.
- (Optional) Select the Source Drive Pool and Destination Drive Pool.
-
Click Apply.
-
When the confirmation message appears, click Yes to export the copy of the media, or No to abort.
Select this option to import media after the media has been physically inserted into the I/E port (mailbox) of the tape library. The Tertiary Manager system mounts the tape and populates the file system with the files from the tape. Two types of data ingest options are available:
-
File Ingest: For file ingest, the contents of the media are copied into a destination directory. There are no references kept in the Tertiary Manager system of the imported media, allowing the media to be removed from the system immediately after the file ingest is complete.
- Media Ingest: For media ingest, media are scanned and database entries are added for the files on the media. The destination directory is then populated with truncated files, which may later be retrieved from the ingested media after the ingest operation is complete. The media is retained by the Tertiary Manager system after the media ingest is complete.
To aid in the import process, the Import Media action makes use of manifest files that are generated by the Export Media and Export Copy of Media actions. It is highly recommended that manifest files always be used when available. If a manifest file is not specified, a Media Ingest operation:
-
Imports all files on the media regardless of whether the files were deleted from the source file system.
- Does not import file checksums.
- Does not inform you which media IDs you need to completely ingest segmented files that span media.
- Might take longer to complete its operations.
-
Select the tape library from the Library drop-down list.
- (Optional) Click Show previously imported media to display previously imported media that you can retry in the event of a partial (or a full) import operation failure.
- If the media of interest are not listed in the Media section, select Scan Mailbox to populate the list.
-
Select the media you want to import.
-
(Optional) Select Use Media Manifest. If manifests files are available for all media, this option will be automatically selected. If any manifest files are unavailable for the selected media, this option will be unavailable.
-
Select the Media Format as either ANTF or LTFS.
Note: Importing ANTF media is limited to the Media Ingest option.
-
Select the Ingest Type.
-
For Media Ingest:
Note: Importing ANTF media is limited to only this ingest type.
- (Optional) Select Media Manifest. The default is None if a media manifest does not exist.
-
Select the Media Format.
Note: Importing ANTF media is limited to only the Media ingest type.
-
Select the Ingest Type.
Note: Importing ANTF media is limited to only the Media ingest type.
- Select the File System.
- Select the Relation Point.
- (Optional) Select Directory Filter.
- (Optional) Select Directory.
- (Optional) Select Strip Path.
- (Optional) Select Drive Pool.
- (Optional) Select Copy Number.
- (Optional) Select User ID (Numeric).
- (Optional) Select Group ID (Numeric).
- (Optional) Select File Permissions (Octal).
- (Optional) Select Populate Filesystem. This option allows you to recover files to the file system and is enabled by default.
-
For File Ingest:
Note: This ingest type is only supported for LTFS media.
- (Optional) Select Media Manifest. The default is None if a media manifest does not exist.
-
Select the Media Format.
Note: The Files ingest type is only supported for LTFS media.
-
Select the Ingest Type.
Note: The Files ingest type is only supported for LTFS media.
- Select File System.
- (Optional) Select Directory Filter.
- (Optional) Select Directory.
- (Optional) Select Strip Path.
- (Optional) Select Drive Pool.
- (Optional) Select User ID (Numeric).
- (Optional) Select Group ID (Numeric).
- (Optional) Select File Permissions (Octal).
- (Optional) Select Eject Media After Ingest.
-
-
Click Apply.
-
When the confirmation message appears, click Yes to import the media, or No to abort.
Manual Steps to Achieve File Ingest for ANTF Media
The Import Media action supports Media Ingest for ANTF media, but it does not support File Ingest for ANTF media. Below are the manual steps you can perform to effectively achieve a File Ingest:
- Run the Media Ingest operation on the ANTF media as described above.
-
After the Media Ingest operation has completed, change the media ownership status from Imported to Owned by running the following CLI command:
fschmedstate -s owned 000089 -
Set the media to write protected status by running the following CLI command:
fschmedstate -s protect 000089 -
Retrieve all the files that were imported by running the following CLI command:
fsretrieve -R /stornext/snfs1/antf/import/Important Consideration About The Recursive Retrieve Command
There are two phases when you invoke a recursive retrieve command:
- Phase 1: Mapping of the directory and the files to determine which files are retrieved.
- Phase 2: The actual retrieves from tape, sdisk, and object storage.
During Phase 1 you can only execute one recursive retrieve command at a time. If you execute multiple recursive retrieve commands concurrently, the processes fail and you are notified that an existing recursive retrieve command is in progress.
For example, if a recursive retrieve is currently running Phase 1 and an additional recursive retrieve is invoked, the second request fails
However, if that same recursive retrieve is currently running Phase 2, and an additional recursive retrieve is invoked, the second request is processed without any errors.
-
Remove all the tape copies for the files that were imported by running the following CLI command:
fsrmcopy -a -R /stornext/snfs1/antf/import/ -
Clean the media to make it go blank by running the following command:
fsclean -t -P -m 000089 -
Remove the media from TSM by running the following command:
fsmedout 000089 - Eject the media using the Tools > Storage Manager > Library Operator Interface.
Select this option to manually move media from one library to another. This media action is typically used to move media to a new archive from a dead or offline archive.
-
Select from the Library drop-down list the library containing the media you want to move.
-
Select one or more media to move, or check the box to the left of the Media ID heading to select all media.
-
At the Move Media Parameters > Destination Library field, select the destination library to which you want to manually move the selected media.
-
Click Apply.
-
Complete the process by manually moving the media you specified to the destination library.
Select this option to view the attributes currently assigned to your media, or to change attributes.
-
If desired, filter the displayed list of media by selecting one or more of the following media attribute filters: Suspect, Marked, Full, Unavailable, or Write Protected. The list refreshes each time you select a media attribute filter.
-
Suspect means the media might not be physically sound, and could be in a potentially damaged or unusable condition.
- Marked means the media should be made inaccessible.
- Full means the media has reached capacity and should not be available for further writing.
- Unavailable means the media is not available for writing or reading.
-
Write Protected means the media is protected against further writing and cannot be overwritten or have data added.
-
-
Select from the list one or more media whose attributes you want to change, or click All to select all media.
-
Select from the New Media State drop-down the desired attribute to apply to the selected media.
-
Click Apply.
-
When the confirmation message appears, click Yes to move the selected media, or No to abort.
-
Repeat Step 3 through Step 5 to apply additional attributes to the selected media.
Select this option to manually mount a piece of storage media into a drive.
-
Select from the Library list the library containing the media you want to mount.
-
Select the media to mount.
-
Select from the Drive list the drive in which the media is to be mounted.
- Click Apply.
-
When the confirmation message appears, click Yes to mount the media, or No to abort.
Select this option to move media from one library to another. This media action will retain all information about the data contained on the media being moved.
-
Select from the Librarylist the library containing the media you want to move.
-
At the Media Class field, select the desired media class or choose Show All Media Classes.
-
If desired, specify a search filter for media IDs at the Media ID Filter field. When you specify a filter, only media IDs containing the filter string will be displayed. After you enter the filter string, click Set Filter to apply your entry. If necessary, click Refresh to update the display. To remove the filter at any time, click Clear Filter.
-
Select one or more media to move, or check the box to the left of the Media ID heading to select all media.
-
At the Move Media Parameters > Destination Library field, select the destination library to which you want to move the selected media.
-
Click Apply.
-
When the confirmation message appears, click Yes to move the selected media, or No to abort.
-
Use the Library Operator Interface feature to complete the actual physical move of the media. See Tools > Storage Manager > Library Operator Interface for more information.
Select this option to purge media from the StorNext Storage Manager. All files are removed from the selected media, and then the media is removed from the StorNext Storage Manager and is physically ejected from the library.
Caution: This media action removes all data and information about the data contained on the media prior to it being removed from the library. This information cannot be restored once it is removed.
-
Select from the Library list the library containing the media you want to purge.
-
Select one or more media to purge, or check the box to the left of the Media ID heading to select all media.
-
Click Apply.
-
When the confirmation message appears, click Yes to purge the selected media, or No to abort.
-
Use the Library Operator Interface feature to complete the actual physical removal of the media. See Tools > Storage Manager > Library Operator Interface for more information.
Select this option to re-assign orphaned media (for example, media currently in transit, with no current or pending archive ID set) to the intended archive.
-
Select from the Library list the library containing the orphaned media you want to reassign.
-
Select one or more media, or check the box to the left of the Media ID heading to select all media.
-
At the Reassign Orphaned Media Parameters > Destination Library field, select the destination library to which you want to reassign the selected media.
-
At the Reassign Orphaned Media Parameters > Current Media Location field, select the location where the selected media is currently located.
-
Click Apply.
-
Complete the process by reassigning the media you specified to the destination library.
Select this option to change the media classification.
-
Select from the Media Class drop-down list the current media class designation you want to change. After you select the desired class, all media that currently have this classification appear in the Media section.
-
Select one or more media to reclassify, or check the box to the left of the Media ID heading to select all media.
-
Select from the Destination Media Class drop-down list the new media class designation for the selected media. Select one of these options:
- DATA: This media class means that media are candidates for read/write operations. Most media residing in the library have this classification unless they are full.
- ADDBLANK: This is the default class with which media are associated when they are added to StorNext MSM. Running the Fsmedin command pulls media from this class and changes the classification to DATA.
- IMPORT: Before running the fsmedin command on TSM-exported media, the classification should be changed to IMPORT.
- CHECKIN: This classification is used for re-entering media which have been checked out. Media must be reclassified with CHECKIN prior to TSM performing fsmedin with the checkin option.
- MIGRATE: TSM reclassifies media to this classification when
the media becomes full according to the
FS_PERCENT_FULL
system parameter. Media with this classification can still be read. - CLEAN: Media in the class are cleaning media. If the barcode of a media ends with CLN, MSM imports the media into this class instead of ADDBLANK.
- REMOVE: Media get reclassified to REMOVE when fsmedout is used.
- BACKUP: Media with this classification were used for backups before backups were managed by StorNext storage polices. Consequently, this classification is rarely used.
-
Click Apply.
-
When the confirmation message appears, click Yes to reclassify the selected media, or No to abort.
Select this option to remove media from the StorNext Storage Manager. Only media which do not contain data can be selected for removal. The media is removed from the system and is physically ejected from the library.
-
Select from the Library list the library containing the media you want to remove.
-
Select one or more media to remove, or check the box to the left of the Media ID heading to select all media.
-
Click Apply.
-
When the confirmation message appears, click Yes to remove the selected media, or No to abort.
-
Use the Library Operator Interface feature to complete the actual physical removal of the media. See Tools > Storage Manager > Library Operator Interface for more information.
This option allows you to set the availability of namespaces that have been added to existing Object Storage destinations. The options are Available and Unavailable.
-
In the Available Media Actions list, click Set Object Storage Media Availability. The GUI page displays a list of namespaces that exist under different Object Storage destinations.
-
In the Media table, click a namespace.
-
In theNew Object Storage Media State list, click Available or Unavailable.
-
To accept your selection, click Apply.
To view the availability of the Object Storage media, perform the following procedure:
-
In the Reports menu, click Media to display the details for all media (including cleaning media) in a selected library or all libraries.
-
To view a report for a particular piece of media, select the desired media from the list:
-
To select multiple media, hold down the Ctrl key while you click additional media.
-
- To select all media, click the check-box to the left of the Name heading.
- After you have selected media, click View Media Information Report. The Media Information Report page appears. This report allows you to see all files on the selected media. The availability attribute (Available or Unavailable) is displayed next toMedia Status.
- (Optional) Save the report output as a CSV file (Microsoft Excel format) by clicking Download.
- When you are finished viewing the information report, click Done.
Transcribe (copy) the contents of one media to another media (such as scratch), or reclaim (defragment) media. During the transcription or reclamation process, StorNext uses two drives to transcribe one media to another media, file by file.
Caution: For StorNext to successfully transcribe one media to another media, two drives must be online. If only one drive is online, the transcription or reclamation process fails.
The following table displays the support matrix for transcribe operations:
Destination | ||||||
---|---|---|---|---|---|---|
Object Storage | Tape | Storage Disk | Q-Cloud Archive | Q-Cloud Vault | ||
Source |
Object Storage | Yes | No | No | Yes | Yes |
Tape | Yes | Yes | No | Yes | Yes | |
Storage Disk | Yes | No | No | Yes | Yes | |
Q-Cloud Archive | Yes | No | No | Yes | Yes | |
Q-Cloud Vault | No | No | No | No | No |
Based on the selected source media type(s), the StorNext GUI will display the appropriate transcribe options.
Special Considerations for the Transcribe Media Action
- The Source Policy Class Filter is grayed out when transcribing tapes as tapes can only contain a single policy class.
- The Destination Media Type is specified by selecting one of the following:
- Any Available Media for the selected Media Type.
- Any Available Blank Media for the selected Media Type.
- Specific Media ID of the selected Media Type.
- Manually enter the desired Media ID.
-
Select one or more media to transcribe, or check the box to the left of the Media ID heading to select all media.
-
(Optional) In the Transcribe Media Parameters section, you can copy only data file(s) belonging to the specified class in the Source Policy Class Filter list. Alternatively, in the Source Policy Class Filter list, select All Policy Classes to copy all the files to the destination media.
Additional parameters include:
- Inactive File Versions: Click this option to copy all files (active and inactive versions) from the source medium. After all versions are copied, the source medium reverts to blank status.
- Destination Media Type: Select the type of destination medium to use. Depending on the platform used, the following media types are supported by Tertiary Manager software:
- AWS
- AZURE
- LATTUS
- GOOGLES3
- QVAULT
- S3
- S3COMPAT
- LTO
- LTOW
- 3592
- T10K
- SDISK
Note: If you do not select the destination media type, then the policy class definition is used.
-
Destination Media Format: Select the media format type to use when formatting or selecting media.
- ANTF is the Quantum internal tape format. A value of ANTF formats media with a single partition containing ANTF volume labels. This data partition stores StorNext file data
- LTFS is the Linear Tape File System specification tape format. A value of LTFS formats media with two partitions containing LTFS volume labels. The index partition stores LTFS metadata and the data partition stores StorNext file data. The LTFS media format type is only applicable to LTO media generation 5 and beyond (for example, LTO-5, LTO-6, and so on). If you assign LTFS to non-LTO media types, then the action results in an error.
- NONE is displayed if your Destination Media Type is Object Storage (S3).
If you do not specify a format, then the default is determined as follows:
- A media type that does not support LTFS defaults to ANTF.
- A media type that supports LTFS defaults to the policy class copy definition.
-
Encryption Type: Select the encryption algorithm to apply to the content of files stored into an Object Storage system. This option is ignored for all other media types. The following encryption types are supported:
- none: No encryption.
- client: Client-side AES256 encryption. The client encryption type is supported only on Object Storage systems from providers QCV1 and QVV1.
- SSE_S3: Server-side AES256 encryption with S3-managed keys. The SSE_S3 encryption type is valid only if supported by the Object Storage system.
- SSE_KMS: Server-side AES256 encryption using the AWS Key Management Service (KMS). For the SSE_KMS encryption type, you can use the default customer master key (CMK) for encryption or you can create a CMK using the AWS Key Management Service and specified with the Encryption Master Key option.
If you do not specify the Encryption Type, then the encryption type is set to none. Copying a file that had client-side encryption enabled from the source media to the destination media with client-side encryption enabled is not supported. All other copying combinations involving client-side encryption are supported.
- Encryption Master Key: Select the Master Key name that is required by and used for the client-side encryption service or has been created using the AWS Key Management Service and requested for server-side encryption. To create a Master Key name for client-side encryption, see the fskey(1) command in the StorNext 6 Man Pages Reference Guide.
-
Compression Type: Select the compression algorithm to apply to the content of the file stored into Object Storage systems. This option is ignored for all other media types. Furthermore, this option is only supported on Object Storage system from providers QCV1 and QVV1. The following compression type values are supported:
- none: No compression.
- client_lz4: Client-side LZ4 compression.
If you do not specify the Compression Type, then the compression type is set to none. Copying a file that had client-side compression enabled from the source media to the destination media with client-side compression enabled is not supported. All other copying combinations involving client-side compression are supported.
- Destination Media: Specify the destination media.
- Destination Media ID: Use the given media ID as the destination medium.
-
Click Apply.
-
When the confirmation message appears, click Yes to dismount the media, or No to abort.
Use this option to recreate files on the medium from alternate media which have different copies of the files. For instance, when there are issues with a medium such that files can not be read from it.
Note: The Source Copy Number option allows you to specify which copy to use.
Note: SDISK and object storage media not supported.
Example
If medium A is bad and contains Copy 1 files, and you specify Source Copy Number as 2, then you use Copy 2 media to recreate a new Copy 1 instance of medium A files on other Copy 1 media.
If you specify Source Copy Number as Any, then you can use the media associated with any other copy. In other words, you can use the media from different copies to recreate new copies of the bad source medium files.
Special Considerations for the Recreate Media Action
- The media being replaced must have an unavailable status.
- If any alternate source media are in an unusable state or vaulted, then they are not used.
-
The size of the file segments on the alternate source media being used and the media being recreated must be the same, or those segments are not copied.
Note: Typically, this only occurs when the media types are different for the alternate source media and the media being recreated.
-
In the Unavailable Tape Media table, select one or more media to recreate, or check the box to the left of the Media ID heading to select all media.
-
In the Recreate Media Parameters section, you can specify which copy of the media to use in the Source Copy Number list. Alternatively, in the Source Copy Number list, select Any to use the media associated with any other copy.
Additional parameters include:
- Inactive File Versions: Click this option to copy all files (active and inactive versions) from the source medium. After all versions are copied, the source medium reverts to blank status.
- Destination Media Type: Select the type of destination medium to use. Depending on the platform used, the following media types are supported by Tertiary Manager software:
- AWS
- AZURE
- LATTUS
- GOOGLES3
- QVAULT
- S3
- S3COMPAT
- LTO
- LTOW
- 3592
- T10K
- SDISK
Note: If you do not select the destination media type, then the policy class definition is used.
-
Destination Media Format: Select the media format type to use when formatting or selecting media. ANTF is the Quantum internal tape format. LTFS is the Linear Tape File System specification tape format. A value of ANTF formats media with a single partition containing ANTF volume labels. This data partition stores StorNext file data. A value of LTFS formats media with two partitions containing LTFS volume labels. The index partition stores LTFS metadata and the data partition stores StorNext file data. The LTFS media format type is only applicable to LTO media generation 5 and beyond (for example, LTO-5, LTO-6, and so on). If you assign LTFS to non-LTO media types, then the action results in an error.
If you do not specify a format, then the default is determined as follows:
- A media type that does not support LTFS defaults to ANTF.
- A media type that supports LTFS defaults to the policy class copy definition.
-
Encryption Type: Select the encryption algorithm to apply to the content of files stored into an Object Storage system. This option is ignored for all other media types. The following encryption types are supported:
- none: No encryption.
- client: Client-side AES256 encryption. The client encryption type is supported only on Object Storage systems from providers QCV1 and QVV1.
- SSE_S3: Server-side AES256 encryption with S3-managed keys. The SSE_S3 encryption type is valid only if supported by the Object Storage system.
- SSE_KMS: Server-side AES256 encryption using the AWS Key Management Service (KMS). For the SSE_KMS encryption type, you can use the default customer master key (CMK) for encryption or you can create a CMK using the AWS Key Management Service and specified with the Encryption Master Key option.
If you do not specify the Encryption Type, then the encryption type is set to none. Copying a file that had client-side encryption enabled from the source media to the destination media with client-side encryption enabled is not supported. All other copying combinations involving client-side encryption are supported.
- Encryption Master Key: Select the Master Key name that is required by and used for the client-side encryption service or has been created using the AWS Key Management Service and requested for server-side encryption. To create a Master Key name for client-side encryption, see the fskey(1) command in the StorNext 6 Man Pages Reference Guide.
-
Compression Type: Select the compression algorithm to apply to the content of the file stored into Object Storage systems. This option is ignored for all other media types. Furthermore, this option is only supported on Object Storage system from providers QCV1 and QVV1. The following compression type values are supported:
- none: No compression.
- client_lz4: Client-side LZ4 compression.
If you do not specify the Compression Type, then the compression type is set to none. Copying a file that had client-side compression enabled from the source media to the destination media with client-side compression enabled is not supported. All other copying combinations involving client-side compression are supported.
- Destination Media: Specify the destination media.
- Destination Media ID: Use the given media ID as the destination medium.
-
Click Apply. The Recreate Media dialog appears, and you are prompted to confirm if you want to recreate the specified media.
-
Click Yes to recreate the media, or No to abort the operation and return to the previous page.