Disk Libraries - Troubleshooting

Table of Contents

MM0009: Backup Jobs using Disk Library with iBRIX CIFS/NFS Mount Paths Fail

For more information, see KB Article MM0009.

MM0011: Cannot Configure a Disk Library

Cause

When you configure a disk library, it might fail if:

  • You cannot access the location from the MediaAgent that you want to provide
  • If you have provided the wrong user credentials for the location

Resolution

Make sure that:

  • The location is accessible from the MediaAgent.
  • You have provided correct user credentials for the location.

MM0012: Mount Failures in a Job That Accesses a Shared Disk Library

Verify whether the status of the disk library, mount path, and the device is Online.

Cause

If the status is Online, the mount failure might occur if there are no drive letters are available in the operating system to mount the volume for the job.

Resolution

  1. Make sure that there are sufficient drive letters available in the operating system for each device to mount the volume.
  2. If all the drive letters are used, disconnect and make some drive letter available before resuming the job.

MM0013: Login and Password Prompt Is Always Displayed When You Access the Index Cache, Disaster Recovery Backup, and/or Mount Path

Cause

If you access a UNC path that is in different domain, that domain might not have trust relationships established with the domain where the computer is located. This causes the software to prompt  for the User name and Password each time the UNC is accessed.

Resolution

Contact your Network Administrator to set up trust relationships between the domains.

MM0014: Free Space Value for Mounted LUN Disk in Windows 2003 MediaAgent Lists Incorrectly

Cause

When you use LUN Disk Array as UNC path from Windows 2003 machine, the free space from Windows 2003 machine is shown about parent directory instead of actual mounted LUN.

Resolution

You should share the mounted LUN, and then use that as the UNC path.

For example, your disk array is mounted on the remote machine machine1 in the C:\ drive under Folder1 as C:\Folder1\LUN. For a Windows 2003 machine, when you use the UNC path \\machine1\c$\Folder1\LUN as the mount path, the free space that is available for the C drive appears instead of the free space for the mount path. You have to share the folder LUN and use that as the UNC path. That is, \\machine1\LUN.

MM0015: Mount Paths Configured on Isilon Shares Are Marked Offline

Cause

If you use an Isilon device to host a disk library, the mount path might go offline when the user name or password is changed.

Resolution

Upgrade to the EMC Isilon OneFS operating system version 7.0.1.8 or later.

MM0016: SnapProtect Cannot Access the CV_MAGNETIC Folder

Cause

When your antivirus security software is in the process of scanning the CV_MAGNETIC folder on library mount paths, SnapProtect cannot access the folder.

Resolution

Exclude the CV_MAGNETIC folder from the antivirus security software scan.

MM0017: Performance Decreases on NetApp Disk Libraries When Space Usage Exceeds 85%

Cause

This is a known issue with NetApp's Data ONTAP. For more information, see http://support.netapp.com/NOW/cgi-bin/bugrellist?bugno=588941.

Resolution

Upgrade to the most recent version of NetApp's Data ONTAP. Contact your NetApp vendor to make sure that the most recent version of Data ONTAP is recommended for your NetApp device.

Resolution

If you cannot upgrade to the most recent version of NetApp’s Data ONTAP, set the reserve space thresholds on the NetApp devices that are managed by Data ONTAP to 15%. Monitor those devices to make sure that disk usage does not exceed 85%.

  1. From the CommCell Browser, expand to Storage Resources | Libraries | <Library>.
  2. Right-click the appropriate mount path, and then click Properties.
  3. Click the Allocation Policy tab.
  4. In the Space Allocation section, select Do not consume more than n GB, and then enter a value that is 85% of the total disk space.
  5. Click OK.

MM0019: Disk Library Runs Out of Space After the MediaAgent is Upgraded to SnapProtect Version 10

Symptom

After you upgrade the MediaAgent to SnapProtect version 10, the disk library runs out of space prematurely. An error similar to the following appears in the CVMA.log file:

28532 6f9c 12/05 12:08:45 ------ WORKER [ ] CVMAMagneticWorker.cpp:5479: Error while opening the mount path label [<disk_library_location>\CV_MAGNETIC\MOUNTPATH_LABEL], error=0xECCC0002:{QiFile.cpp[CQiFile::Open(92)]} + {utfFsUtils.cpp[CQiUTFOSAPI::open(85)]/ErrNo.2.(No such file or directory)-Open failed, File=\\?\<disk_library_location>\CV_MAGNETIC\MOUNTPATH_LABEL, OperationFlag=0x8000, PermissionMode=0x100}

Cause

The input file (mount path label file) is missing from the mount path. This prevents aged data from being pruned.

Resolution

To avoid this you can do the following:

  • Use the CreateMountPathLabel tool to identify which mount paths do not have a label.
  • Create an input file.
  • Use the CreateMountPathLabel tool to place the input file in the appropriate mount path.

    Note: For windows, only local mount paths are supported for this procedure.

For more information, see Creating Mount Path Label.

Before you begin

To create an input file, you will need the CommCell number. To view the CommCell number:

  1. On the ribbon in the CommCell Console, click the Tools tab, and then click License Administration.
  2. Click the License Summary tab.
  3. CommCell number is the decimal value displayed for Server id.

    For Example:

    Server Id: 14325 (0x37F5)

    In this example, CommCell number is 14325.

To create an input file, you will need the library id. To view the library id:

  1. Use the GxTail tool from the <software installation\Base> folder to retrieve the MediaManager.logs. (See GxTail - Overview for more information.)
  2. The library id is displayed along with the library alias name.

    For Example:

    [DiskLibrary334<DiskLib1>]

    In this example the library alias name is DiskLib1 and the corresponding library id is 334.

Procedure

  1. On the MediaAgent computer, type the following at the command prompt:

    For Windows

    >cd <software installation path>\Base
    >CreateMountPathLabel.exe -report -inst <instance_ID>

    For Unix

    [root@user-xxx Base]# /opt/<software installation path>/Base/CreateMountPathLabel -report -inst <instance_ID>

  2. A list appears that includes the mount path ID and the mount path name.

    For Windows

    MountPathLabel does not exist in the following Paths:

    42 E:\MountPath\Folder_11.30.2013_04.55\CV_MAGNETIC
    46 E:\MountPath_1\Folder_04.09.2014_12.30\CV_MAGNETIC

    For Unix

    MountPathLabel does not exist in the following Paths:

    92 /home/Maglib/Folder_11.30.2013_04.55/CV_MAGNETIC

  3. Create an input file (in .txt file format).

    The input includes the parameters that are required to create a mount path label. The parameters must be entered in the following order:

    • CommCell number
    • Complete file path to the mount path
    • Library ID
    • Mount path ID

    Each parameter is separated by a comma. There must be no spaces before or after each comma. For example:

    For Windows

    14325,E:\MountPath\Folder_11.30.2013_04.55\CV_MAGNETIC,44,42

    For UNC Mount Paths

    Create a temporary folder on the MediaAgent. For example: For example: D:\TEST\CV_MAGNETIC

    Create the input file to point to the temporary folder location.

    14325,D:\TEST\CV_MAGNETIC,44,42

    For Unix

    14325,/disk/mountpath1/CV_MAGNETIC,23,45

  4. Add as many input as you require.

    Each input must be entered on a separate line. For example:

    For Windows

    14325,E:\MountPath\Folder_11.30.2013_04.55\CV_MAGNETIC,44,42
    14325,E:\MountPath_1\Folder_04.09.2014_12.30\CV_MAGNETIC,23,46

    For UNC Mount Paths

    14325,D:\TEST\CV_MAGNETIC,44,42
    14325,E:\TEST\CV_MAGNETIC,23,46

    For Unix

    14325,/disk/mountpath1/CV_MAGNETIC,23,45
    14325,/disk/mountpath2/CV_MAGNETIC,23,46

  5. Save the input file to a location on the MediaAgent computer.
  6. Type the following at the command prompt:

    For Windows

    >CreateMountPathLabel.exe -if <input file location>\InputFile.txt

    For UNC Mount Paths

    >CreateMountPathLabel.exe -if <input file location>\InputFile.txt

    For Unix

    [root@user-xxx Base]# /opt/<software installation path>/Base/CreateMountPathLabel -if /<input file location>/InputFile.txt

    You receive a message that the operation was successful. The CV_MAGNETIC folder is updated and the input file is located within it.

  7. For UNC mount paths follow the steps:
    • Edit the MOUNTPATH_LABEL file available in the local directory by replacing the local paths with the network paths.
    • Copy the MOUNTPATH_LABEL file on the network mount path in the CV_MAGNETIC folder.

      For example:

      Edit the MOUNTPATH_LABEL file in the D:\TEST\CV_MAGNETIC folder with the correct mount path location, which should be a UNC path.

      Copy the MOUNTPATH_LABEL file on the network mount path in the CV_MAGNETIC folder.

  8. Restart the MediaAgent services.

    Aged data is pruned as expected and the space on the disk library is reclaimed.

MM0021: Chunk Errors Occur on Nexsan Devices

Symptomm

Chunk errors occur on Nexsan devices with the following errors:

Error Code 40:91:
Failed to Copy or verify Chunk [] in media [], Storage Policy [], Copy [], Host [], Path [], File Number [], Backup Jobs [].\].Data read from media appears to be corrupted. Data read from media appears to be corrupted.

Error Code 62:469:
Data read from media appears to be corrupted.

Log files might include entries similar to the following:

AuxCopy.log located on the corresponding MediaAgent:

[F:\MAG11-F\BASE-F\CV_MAGNETIC\V_6561581\CHUNK_5847058\CHUNK_META_DATA_5847058] file
14490301-16560393 [DM_BASE ] DataMoverSingleInstancer::OpenChunkSpecific: Not honoring readless mode because this job type is [13]. Dest Copy Id [0]
14490301-16560393 [DM_BASE ] Readless mode [false]
CCVAPipelayer::SetEncryptProps() - Entered
CCVAPipelayer::SendCommandToDSBackup() - Sent Command 156 to MediaAgent, Waiting for Response...
[PIPELAYER ] Tail response = Get PL_SET_ENC_PROPS Message Status = 0 dwCode = 0 MsgType = 16 MsgSubType = 156 EventError = 0
Successfully opened the archive files on the media...going to read data.
###### [ NULL] invalid tag header
14490301-16560393 [DM_BASE ] **ERROR** DataMoverSingleInstancer::ReadTagHeader: Failed to convert the tag header to Host byte order. Tag header got =

JobManager.log located on the corresponding MediaAgent:

Scheduler Set pending cause [Failed to Copy or verify Chunk [5847058] in media [CV_MAGNETIC], Storage Policy [...], Copy [1:Primary Disk], Host [...], Path [F:\MAG11-F\BASE-F\CV_MAGNETIC\V_6561581], File Number [121], Backup Jobs [ ].Data read from media appears to be corrupted.aData read from media appears to be corrupted.a]::Client [...] Application [AuxCopy] Message Id [671088731] RCID [14490301] ReservationId [0]. Level [0] flags [0] id [0] overwrite [0] append [1] CustId[1040187861].

Resolution

Older Nexsan firmware must be updated. Use the appropriate version based on your storage device type.

  • For SATABeast 2.5, use firmware version Pp70 or later.
  • For SATABeast 2, use firmware version Nj67 or later.
  • For other devices, contact Nexsan.

A list of the latest firmware release is available at www.nexsan.com/support/latest-firmware.aspx.

MM0023: Initiating a Backup Job Displays "No (subclient) data paths were found for the copy" Error

Symptom

After migrating a shared disk library to another MediaAgent within the CommCell, initiating a backup job may display the following error:

No (subclient) data paths were found for the copy. Probably a library has been deconfigured.

Cause

Only one disk library was configured as the data path on the storage policy copy, and that disk library was deconfigured prior to assigning a new disk library as the data path.

Resolution

Change the data path of the associated storage policy copy by following the steps described in Change Default Data Path.

MM0063: Error Code: [62:311]: Failed to Mount Media [name]with Mount Path[location] on MediaAgent [MA name]

For more information, see KB Article MM0063.