Loading...

Disk Libraries - Frequently Asked Questions

Table of Contents

How do I include the CV_Magnetic folder in the backup operations?

The CV_MAGNETIC folder (which is created when a mount path is configured) is, by default, excluded from backup operations if a MediaAgent and the Windows File System iDataAgent are installed on a computer. The CV_MAGNETIC folder must be associated with the MediaAgent that is installed on the computer.

To include this folder in backup operations:

  1. From the CommCell Browser, expand to Storage Resources | MediaAgents.
  2. Right-click the appropriate MediaAgent, and then click Properties.
  3. Click the Additional Settings tab.
  4. Click Add.
  5. In the Name box, type nDoNotFilterGalaxyMagneticMountPaths, and then press Enter.

    The values for all fields fill automatically.

  6. In the Value box, type 1.
  7. Click OK.
  8. Click OK.

What is the default chunk size and block size to read or write data from disk libraries?

By default, the system uses 4 GB as the chunk size and 64 KB as the block size to read/write data from disk libraries. If necessary, you can change these values in the Data Path Properties dialog box for each data path. Access the Data Path Properties dialog box from the Data Paths tab of the Copy Properties dialog box for the selected data path. For more information about using chunk and block sizes, see Performance Tuning.

Can I create a disk library using SMB3 for Windows 2012?

Yes, you can create a disk library using SMB3 on Windows 2012.

After you create a disk library, make sure to select the Prevent accidental deletion of data from mountpaths check box to protect your mount path contents from being deleted accidentally from outside of the CommCell Console. See Prevent Accidentally Deleting the Contents of a Mount Path for more information.

Can I create a disk library using ReFS for Windows 2012?

Yes, you can create a disk library using ReFS on Windows 2012.

What are the recommended settings for EMC® Data Domain® disk libraries?

SnapProtect works best with EMC Data Domain disk libraries if you minimize how often SnapProtect accesses the disk library.

Apply the following recommended settings to each MediaAgent associated with the disk library:

Reduce Access Frequency During Backup Operations

  1. From the CommCell Browser, expand Storage Resources | MediaAgents.
  2. Right-click the appropriate MediaAgent, and then click Properties.
  3. Click the Additional Settings tab.
  4. Click Add.

    The Add Additional Settings dialog box appears.

  5. In the Name box, type DMDontUpdateVolumeSizeDuringBackup.

    The Category and Type details fill automatically.

  6. In the Value box, type 1.
  7. Click OK.
  8. Click OK.

Prevent Data Pruning During Peak Backup Times

This procedure prevents physical pruning of data during peak backup times. However, it provides enough time for pruning to run outside of the peak times so that the disk library does not run out of space.

  1. From the CommCell Browser, right-click the CommServe node, and then click Properties.
  2. On the Additional Settings tab of the CommCell Properties dialog box, click Add.
  3. In the Add Additional Settings dialog box, enter the following:

    1. In the Name box, type sMMDoNotPruneInterval.

      The Category and Type details fill automatically.

    2. In the Value box, enter the appropriate time interval in hours.

      For example:

      To prevent pruning from 10:00 AM to 12:00 PM, and from 8:00 PM to 11:00 PM type 10-12, 20-23.

      To prevent pruning from 6:00 PM to 7:00 AM the next day, type 18-7.

    3. Click OK.
  4. Click OK.

Minimize the Number of Volumes on the MediaAgent and the Frequency of Volume Size Updates

  1. On the ribbon in the CommCell Console, click the Storage tab, and then click Media Management.

    The Media Management Configuration dialog box appears.

  2. On the Service Configuration tab, set both of the following parameters:

    Note: If you have upgraded from V 9.0 to the current version, the Interval between volume size update requests and the Number of volumes for size update parameters are available on the Data Aging tab.

    • For Number of volumes for size update, type 50.

      You can use a value other than 50, but it should be a small value.

    • For Interval between volume size update requests, type 2880.

      The value 2880 minutes = 2 days.

  3. Click OK.

Prevent SMB/CIFS Session Leaks on the Windows Operating System

In addition to the recommended settings for each MediaAgent, consult the following Microsoft Knowledge Base article:

"SMB/CIFS sessions leak in Windows Vista, in Windows Server 2008, in Windows 7 and in Windows Server 2008 R2", http://support.microsoft.com/kb/2537589

Can I configure Data Domain Boost (DD Boost) on Disk Libraries using EMC® Data Domain®?

Yes, Data Domain Boost on Data Domain physical boxes and Data Domain Virtual Edition is supported on Linux MediaAgents. (The product was tested using Red Hat Enterprise Linux Server release 6.5 (Santiago) with Kernel Version: 2.6.32-431.el6.x86_64*.)

Configuration

Use the following steps to make sure that the device is mounted in the MediaAgent, before configuring the library.

  1. Install the FUSE File system and its dependencies on the MediaAgent. (The product was tested using FUSE version: fuse-2.8.3-4.el6.x86_64.rpm*.)

    Note: Make sure that the FUSE version is compatible with the DD Boost File system version.

  2. Install the DD Boost file system RPM on the MediaAgent. (The product was tested using DD Boost file system versions: DDBoostFS-1.0.0.1-539441.rhel.x86_64.rpm and DDBoostFS-1.0.0.2-542445.rhel.x86_64.rpm*.)

    You can verify the installation from the following location:

    /opt/emc/boostfs

  3. Run the following commands from the following location:

    /opt/emc/boostfs/bin

    Set the lock box between the Data Domain storage unit and MediaAgent using the following command:

    boostfs lockbox set -s <Storage-unit> -d <data-domain-system> -u <storage-unit-username>

    Mount this storage unit on the MediaAgent using the following command:

    boostfs mount -d <data-domain-system> -s <Storage-unit> <mount-point>

  4. Configure a disk library using the above storage unit mount point as the mount path for the library.

Known Issues

When you backup data to the Data Domain Virtual Edition, the post compression space is reported incorrectly.

* If you have a different version, contact SnapProtect to verify compatibility.

What are the recommended settings for EMC Isilon disk libraries running OneFS?

EMC and Microsoft support the following Server Message Block (SMB) protocol versions.

For questions regarding the support of device software, operating system levels, and the Server Message Block (SMB) protocol contact EMC or Microsoft support. NetApp offers the following support information only as guidelines for hosting Isilon disk devices on a NetApp MediaAgent.

Supported Server Message Block (SMB) versions for Isilon OneFS

Isilon OneFS version SMB 1 SMB 2 SMB 2.1 SMB 3 SMB 3.02
6.5      
7.0    
7.1    
7.2  

Supported Server Message Block (SMB) versions for Windows Server

Microsoft Windows Server version SMB 1 SMB 2 SMB 2.1 SMB 3 SMB 3.02
2000        
2003        
2003 R2        
2008      
2008 R2    
2012  
2012 R2

For more information on the supported versions, see the Isilon Supportability and Compatibility Guide, on the EMC Support Web site at https://support.emc.com/.

Important: SMB 2.1 applies caching of folders or file properties or directory leasing related to the Opportunistic Locking (oplock) leasing model. For other disk array hardware vendors and devices, contact the appropriate hardware vendor for its best practices regarding SMB and Opportunistic Locking.

Why are some MediaAgents shared automatically as Data Server IP on the mount paths?

If a library with multiple mount paths is associated with a Network Storage Pool, and MediaAgents are added to a mount path or a mount path is added to the library, then all the associated MediaAgents are shared automatically with all the other existing mount paths by using the DataServer-IP. This eliminates the need of manually sharing the mount paths to allow for reading the deduplicated data from the other MediaAgents.

For example, on a library lib1 there are 2 mount paths mp1 and mp2. On mp1, if you have newly associated MediaAgent MAn, then MAn will automatically get added to mp2 using the Data Server IP transport type. This is so that without manual sharing, the deduplication references on mp1 that are required by data being read on mp2, can be read by MAn.