name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=0 lun=2;
Topics | How To | Troubleshoot | Support | Related Topics
Device Detection on AIX MediaAgent is Slow
Tape Spanning failure on AIX MediaAgents with Native Drivers
Job Failures in Solaris MediaAgents using Native Drivers
Adjust Timeout Value for SCSI Commands on UNIX MediaAgents
Work-Around for a Failed MediaAgent
Move a Library to Another MediaAgent Without Data Loss
Move a MediaAgent Without Data Loss
Separate the CommServe from a CommServe - MediaAgent Computer
Windows 2008 x64 MediaAgent is Out of Physical Memory and is Unresponsive
This might occur for the following reason:
Cause: On AIX MediaAgents, the presence of a number of SCSI adaptors may result in slowing down the detection process. If you know that some of these adaptors are not required by the MediaAgent, you can skip them during the detection process as described in below.
Create the following file:
<software installation path>/Base/detectdevices.skip
Use the following format to add the list of adapters that must be skipped during device detection.
adapter <adapter name>
For example:
adapter scsi2
adapter fscsi1
Note the following:
This might occur for the following reason:
Cause: On AIX MediaAgents with IBM library and ATAPE drivers and if Use Native device driver for data transfer for tape media option in the MediaAgent Properties is enabled, the MediaAgent software sets the drive attribute for trailer_labels to yes when a data protection operation is initiated. If this attribute is set to no, (For example, by other applications sharing the library) data protections operations may fail when the operation spans to another tape.
Use the following command to see the drive attribute for trailer_labels.
lsattr –El rmtX
Use the following steps if you find Data Protection Operation failing on Solaris MediaAgents when Native Drivers are enabled.
To configure native tape drive support on Solaris the native ST device nodes should be added to /kernel/drv/st.conf and bound to all the tape drive LUNs which are to be used.
For example:
name="st" class="scsi" target=0 lun=1;
name="st" class="scsi" target=0 lun=2;
Also make sure to reload the ST drivers using the following commands:
rem_drv st
add_drv st
If you see devices timing out (in MediaManager.log file) and jobs failing as a result, you may want to adjust the timeout value for SCSI commands to these devices.
On Windows, the system uses native drivers and the timeout values are determined by the drivers.
On UNIX it's possible to specify timeout values for any SCSI command as long as the command is delivered using the pass-through driver as arm changers are always accessed using pass-through nodes on all UNIX platforms.
Tape drives by default are accessed using native drivers on AIX, Solaris, HP-UX, Linux and Tru64. Native drivers do not offer a way to customize SCSI timeouts. However, it is possible to enable pass-through mechanism from the CommCell Console by disabling the Use Native device driver for data transfer for tape media option in the MediaAgent Properties.
Once this is done pass through SCSI timeouts can be customized by modifying the following registry values:
/etc/CommVaultRegistry/Galaxy/Instance<xxx>/ScsiTimeouts
.internal.unique_id 1124467005_16773_40966_392845154
DEFAULT *120*
ERASE *18000*INITIALIZE_ELEMENT_STATUS *600*
INITIALIZE_ELEMENT_STATUS_WITH_RANGE *600*
LOAD *900*
MOVE_MEDIUM *1500*
READ *900*
READ_ELEMENT_STATUS *600*
RESERVE *1200*
REWIND *1800*
SEEK_BLOCK *900*
SPACE *900*
WRITE *900*
WRITE_FILEMARKS *900*
These are the rules that should be observed while making the changes:
If a MediaAgent has failed and there are other MediaAgents in the CommCell, you can re-establish backup/restore operations for the affected client computers. Use any one of the following solutions.
To reestablish client operations when a MediaAgent has failed:
Once the subclients of the affected client computers are associated to working libraries, you can resume backup operations.
----------------------------------------------------
For tape libraries, ensure that the MediaAgent(s) that control both the library and target drive pool are in working order. (For shared libraries, different MediaAgents can control the library and a given drive pool. To identify these MediaAgents, check both the Library Properties and Drive Pool Properties dialog boxes.)
For magnetic disk libraries, ensure the MediaAgent that controls the magnetic disk library is in working order. (To identify the MediaAgent, check the related Library Properties dialog box.)
- From the CommCell Browser, open the Subclient Properties dialog box.
- Click the Storage Devices tab and select one of the newly created storage policies.
Once the subclients of the affected client computers are associated to working libraries, you can resume backup operations.
----------------------------------------------------
If a storage policy has a secondary copy and this copy points to another MediaAgent, and if Auxiliary Copies are performed regularly (therefore making available backed up data in an additional manner), promote the secondary copy to a primary copy.
In some situations you may have the need to move a library from one MediaAgent to another due to re-configuration or other requirements.
The following procedure provides step-by-step instructions on how to perform this operation.
In some situations you may have the need to move a MediaAgent from one computer to another. For example:
You will require an additional MediaAgent license to perform this operation. |
The following procedure provides step-by-step instructions on how to perform this operation.
WARNING Do not deconfigure the library at any point. Also do not uninstall the old MediaAgent until the devices start functioning in the new MediaAgent. |
In some situations you may want to separate the CommServe from a MediaAgent computer, (with or without a File system iDataAgent) if they were installed together. For example, you may want to move the CommServe to a more powerful computer or such similar re-configuration needs.
The following procedure provides step-by-step instructions on how to perform this operation.
You can also use this procedure to relocate a CommServe and MediaAgent which are installed together, to two separate computers.
You will require an additional MediaAgent license to perform this operation. |
Source Computer |
||
1. | Copy the index cache folder (and the job results folder if the (File system iDataAgent is installed) to another location. | |
2. |
Perform a Disaster Recover Backup. Verify and ensure that the Disaster Recovery Backup completes successfully. Also note down the location of the disaster recovery backup file. (For a more detailed discussion, see Phases of Disaster Recovery Backups.) |
See Starting a Disaster Recovery Backup for step-by-step instructions. |
3. | Uninstall the software from the original computer. | See Uninstalling Components for more information. |
WARNING Do not deconfigure the libraries (tape/optical/magnetic libraries, etc.) when you uninstall the MediaAgent software. |
||
Establishing the New CommServe Computer |
||
4. | Install only the CommServe software in the new computer. | See CommServe Deployment for information on installing the CommServe software. |
5. | Restore the CommServe database using the CommServe Disaster Recovery Tool. | See Restore a Disaster Recovery Backup for step-by-step instructions. |
6. | Change the name of the CommServe computer using the CommServe Disaster Recovery Tool. | See Change the Name of the CommServe Computer for step-by-step instructions. |
7. | Inform the Client and MediaAgent computers of the new CommServe name. This can be done from the CommCell Console. | See Informing Clients of CommServe Name Change for step-by-step instructions. |
Establishing the New MediaAgent Computer |
||
8. |
Install only the MediaAgent software in the old computer. (You can also relocate the MediaAgent to another computer, if necessary.) |
See MediaAgent Deployment for more information. |
9. | During MediaAgent installation make sure to specify the index cache to the location in which it was copied in step 1. If you are unable to do so, perform the steps described in Manually Relocate the Index Cache. | |
10. | Open the CommCell Console and change the MediaAgent name associated with the library. | See Changing the MediaAgent (Host) Associated with a Library for step-by-step instructions. |
If you have a magnetic library, make sure that the mount path is pointing to the appropriate location. If necessary move the mount path to the appropriate location and then change the location of the mount path. | See Move a Mount Path for step-by-step instructions. | |
11. | Deconfigure the original MediaAgent from the CommCell Console. | See Deconfigure a Client, MediaAgent, Agent, or Enabler for step-by-step instructions. |
Establishing the File System iDataAgent in the MediaAgent Computer (if it was originally installed) |
||
12. | Capture the metadata records associated only with this client on the CommServe. | See Capturing Metadata Records for step-by-step instructions. |
13. | Deconfigure the Client from the CommCell Console. | See Deconfigure a Client, MediaAgent, Agent, or Enabler for step-by-step instructions. |
14. | Delete the Client in the CommCell Console. | See Delete a Client Computer for step-by-step instructions. |
15. | Change the name of the client back to the original name by editing the answer file (.xml file) that was obtained when the metadata records was captured in step12. | See Edit the Answer File Before Merging Data in the Destination CommCell for step-by-step instructions. |
16. | Merge the metadata records (that was captured in step 12) associated with the client computer in the CommServe. | See Merging Metadata Records for step-by-step instructions. |
17. | Reinstall the file system iDataAgent on the computer. | See Deployment - Windows File System iDataAgent for more information. |
On Windows 2008 x64 MediaAgent computers, excessive growth of the Windows System File Cache might result in slower or unresponsive backup jobs. To avoid this issue, you can use the Microsoft Windows Dynamic Cache Service to manage the working set size of the Windows System File Cache. The recommended cache size is 20% of the maximum RAM capacity. See
Perform the following tasks in the MediaAgent computer to set the cache file growth:
sc create DynCache binpath= %SystemRoot%\System32\DynCache.exe start= auto type= own DisplayName= "Dynamic Cache Service"