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


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


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.


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.


  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


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.


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


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.


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


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.


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

MM0016: SnapProtect Cannot Access the CV_MAGNETIC Folder


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


Exclude the CV_MAGNETIC folder from the antivirus security software scan.

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


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


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.


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 or Later


After you upgrade the MediaAgent to SnapProtect , 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}


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


You can create mount path label files using the workflow. For more information, see Predefined Workflow - Create Mount Path Labels.

MM0021: Chunk Errors Occur on Nexsan Devices


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].


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


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.


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.


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

MM0024: Cannot connect to DataServer, please make sure destination MediaAgent is up and running and there is no network / connectivity issue between source and destination MediaAgent


If the Data Server IP configured on a mount path , then the data protection jobs might go in a pending state with the following error:

Cannot connect to DataServer, please make sure destination MediaAgent is up and running and there is no network / connectivity issue between source and destination MediaAgent

Cause 1

The native NFS service is running on the data server MediaAgent.

Resolution 1

  1. On the data server MediaAgent, navigate to the Services (Local).
  2. Verify if the NFS local services are running.
  3. Stop the NFS local services and restart the  SnapProtect  services.

Cause 2

SnapProtect  services on the data server MediaAgent are offline.

Resolution 2

Restart the  SnapProtect  services. For more information, see Restarting a Service.

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.