Vtl Legato in Datadomain

NetWorker and the Data Domain VTL Option

9/19/07 1 of 31

Legato NetWorker and the Data Domain VTL Option

The instructions provided in this document by Data Domain are for customer convenience and are not warranted or supported by Data Domain. Data Domain expects users to customize installation of third-party software for use at a particular site, but Data Domain is not responsible for the usability of third-party software after installation. Copyright Data Domain, Inc. 2005 - 2006


9/19/07 2 of 31

Table of Contents

1. Preparing and Configuring the Restorer VTL Feature ............................................................ 3 1.1. VTL Guidelines.............................................................................................................. 4

1.1.1. Tape Model Names.................................................................................................... 4 1.1.2. Virtual Tape Cartridges ............................................................................................. 5 1.1.3. LUN Masking ............................................................................................................ 6

1.2. Detailed VTL Setup Example ........................................................................................ 6 2. Host Configuration and Setup ................................................................................................. 7

2.1. Windows HBA Setup Notes .......................................................................................... 7 2.2. Solaris HBA Setup Notes............................................................................................... 9 2.3. Set Up for Windows Backup Servers........................................................................... 10 2.4. Setup for a Solaris Backup Server with a QLogic or Emulex HBA ............................ 13 2.5. RedHat Linux Setup Guidelines .................................................................................. 16

2.5.1. Troubleshooting Tips............................................................................................... 18 2.6. NetWorker 7.3 and NDMP on Windows using VTL................................................... 18

3. Tuning NetWorker Tape Devices.......................................................................................... 27 4. Replication and the VTL Feature .......................................................................................... 27

4.1. Performing a VTL Replication with NetWorker ......................................................... 28 4.2. Save Set Cloning Using a Destination VTL ................................................................ 30


9/19/07 3 of 31

The Data Domain Virtual Tape Library (VTL) feature makes disk storage appear to be physical tape drives when seen from various operating systems, backup software products, and industry-standard protocols. For other vendors' products, set up for the Data Domain VTL feature is done in the same way as set up for tape devices and media changers. Your sites needs the following licenses to use the Data Domain VTL feature:

o StorageTek ACS Library o IBM Ultrium LTO Drives o NetWorker licenses for the number of slots (tape drives) that you set up on the restorer.

This document provides basic instructions for setting up the Data Domain VTL feature with Legato NetWorker. Always read and be familiar with the NetWorker Multiplatform Version Administration Guide. Assume that the NetWorker guide, release notes, and other NetWorker documentation are more up-to-date, detailed, and accurate than this document. NOTE: The NetWorker 7.3 graphical user interface for Windows changes from earlier releases. See NetWorker 7.3 and NDMP on Windows using VTL on page 18 for details.

1. Preparing and Configuring the Restorer VTL Feature

This section provides Data Domain restorer VTL setup notes and guidelines, SAN configuration guidelines, and a detailed example that illustrates all of the required steps to configure a Data Domain VTL. 1. Before configuring the backup software to recognize a restorer VTL, install Fibre Channel

Host Bus Adapters (HBAs) in the restorer and in the backup server that is to access the restorer.

Be sure to view the latest Data Domain VTL compatibility matrix, posted on

https://support.datadomain.com In the restorer, use only an HBA supplied by Data Domain. The HBA must be in slot 3 of

the PCI card array and can be purchased separately. Be sure that the HBA driver in a Windows 2000 backup server is an up-to-date

driver. The- driver supplied with the operating system is out-of-date and can cause problems.

See the Windows HBA Setup Notes (page 7) and Solaris HBA Setup Notes (page 9) sections of this document for specific setup and troubleshooting instructions.

2. The VTL feature is a separately licensed feature. Use the following commands to display

licenses and then install the license if needed:

# license show # license add license code

3. On the restorer, define the VTL tape devices and medium changers. For details, see the Data Domain User Guide that is appropriate for your restorer.


9/19/07 4 of 31

4. On the restorer, enter commands similar to the following. The second command is an example of importing tapes into a VTL. The third command displays port and world-wide-name information for the restorer HBA and the storage node HBA. For example:

# vtl enable # vtl add VTL1 model L180 # vtl tape add TST0101L1 count 5 # vtl import VTL1 barcode TST010L1 count 5 # san show summary

5. On restorers running DD OS 3.x, set the following registry variable with a value of nw1 (n-w-one).

# reg set system.CS_MARKER_ALGO = nw1

For DD OS 4.x use the following command:

# filesys option set marker-type nw1

6. For direct attach configurations, use a fiber cable between the restorer and backup server

HBAs. With a Solaris server using a QLogic HBA, do not connect the cable at this time. 7. For SAN attached configurations, make the following physical connections:

a) Use a fiber cable to connect the restorer HBA to a port on the SAN fabric. b) Use a fiber cable to connect the backup server HBA port to the SAN fabric. (With a

Solaris server using a QLogic HBA, do not connect the cable to the card at this time.)

8. For SAN attached, configure zoning: a) Identify the devices to be configured. Use the device World Wide Port Name (WWPN)

or configure by Domain, Port. Normally the ports are a Data Domain restorer VTL port and a backup server HBA port.

b) On a Fibre Channel switch, create a zone that contains the Data Domain VTL and backup server HBA. Again, use either WWPN or Domain, Port.

c) Save the new zoning configuration. d) Activate the new zoning configuration.

NOTE: Data Domain highly recommends using a single backup server HBA in a zone. The technique is called single initiator zoning. Data Domain also recommends that the HBA access only the restorer VTL devices. In other words, do not share SAN-attached disks or tape and the SAN-attached restorer VTL tape LUNs on the same backup server HBA.

1.1. VTL Guidelines This section identifies guidelines to install and manage the Data Domain VTL feature.

1.1.1. Tape Model Names The current supported tape model names are L180 and RESTORER-L180. Both models emulate an STK L180. The L180 tape library model name presents itself as an STK L180, which is a widely deployed tape library that is recognized by all major backup applications. The model name is used by the backup application to determine the physical device and characteristics that the backup application uses. Some backup application providers require the RESTORER-L180


9/19/07 5 of 31

model name. When using the RESTORER-L180 name, you may need to update the backup application software to recognize the restorer VTL as an emulated STK L180 and to assign the appropriate functionality. If the update is not done, the backup application may not use the restorer VTL properly. NetWorker does not require the RESTORER-L180 tape library model name. Data Domain recommends using the L180 tape library model name with a restorer and NetWorker.

1.1.2. Virtual Tape Cartridges

1.1.1.1. Barcodes Data Domain recommends creating virtual tape cartridges only with unique barcodes. An error appears during an attempt to create a duplicate barcode in the same tape pool, but no error appears when creating a duplicate barcode in different tape pools. However, duplicate barcodes in different pools can result in operator confusion and anomalous backup application behavior.

1.1.1.2. Virtual Tape Cartridge Re-use The size and quantity of tapes created impact the utilization of restorer disk and CPU resources. For the efficient reuse of restorer disk space after data is obsolete (and the restorer cleaning process marks data for removal), Data Domain recommends setting capacity to 100 GB or less and creating only the number of virtual tape cartridges needed to support the defined backup retention policies. Many backup applications continue to utilize new tapes even though tapes with expired data are available for use. Once all data streams on a piece of media have expired, that media is marked as recyclable (reusable or scratch). This approach only overwrites data when no new tapes are available and in some cases only when explicitly configured to do so. With this approach, high utilization of restorer disk resources may occur if too many tapes are defined. Several options exist to reduce such disk utilization. The first step in optimizing restorer disk utilization is to create only the quantity of virtual tape cartridges needed to support the defined backup retention policies. To recycle expired media cartridges and therefore free up restorer disk space, the following options are available: Manually recycle the media. With some backup applications, re-labeling the virtual tape

cartridge recycles the media. Configure the backup application to re-use media. Many backup applications by default set

policies to not overwrite media. Reconfigure the policies to re-use media.

1.1.1.3. Replicated Virtual Tape Cartridges Backup application behavior for handling Data Domain replicated tapes varies. To minimize unexpected behavior or error conditions, virtual tape cartridges should remain imported in the destination libraries only for as long as needed. Once a replicated virtual tape cartridge is imported at the destination, follow the procedures identified by the backup application to re-use the replicated tapes. The replicated tapes should then be exported from the destination library.


9/19/07 6 of 31

The objective of this recommendation is to ensure that at any time only one instance of a replicated tape is visible to the backup application. Steps specific to utilizing replicated virtual tape cartridges with NetBackup are detailed in section 4 Replication and the VTL Feature on page 27.

1.1.3. LUN Masking In most cases, a virtual tape library needs to be accessed by only one client (a host or media server). However, some issues, such as licensing, may call for multiple clients access the same VTL. Under such circumstances, an important point is that only one LUN mask exists for each virtual tape drive and the virtual media changer. Anomalous and unexpected behavior can result if multiple clients access the same virtual tape drive or virtual media changer (that is, more than one LUN mask per virtual tape drive or virtual media changer exists), possibly resulting in loss of data or data corruption. Data Domain recommends assigning one VTL per client.

1.2. Detailed VTL Setup Example This section illustrates the setup of a new VTL with 4 drives and 80 slots with 20 newly imported tape volumes. 1. As sysadmin or as another user with administrative rights, add the VTL license:

# license add XXXX-XXXX-XXXX-XXXX 2. Verify that the new VTL license is installed:

# license show ## License Key Feature -- ------------------- ------- 1 XXXX-XXXX-XXXX-XXXX VTL -- ------------------- -------

3. Activate the VTL processes:

# vtl enable Starting VTL, please wait..... VTL is enabled.

4. Create a new VTL with the vtl add command:

# vtl add vtl01 model L180 drives 4 slots 80 VTL created. Use vtl show config vtl01' to view it.

5. Display the configuration with the following command:

# vtl show config Library Name Library Model Drive Model Slots Drives ------------ ------------- ----------- ----- ------ vtl01 L180 LTO-1 80 4 ------------ ------------- ----------- ----- ------


9/19/07 7 of 31

6. Create 20 virtual tapes and put the tapes into the virtual vault:

# vtl tape add TST000L1 count 20 ... created 20 of 20 tapes...

7. Import all 20 tapes from the vault to the new VTL:

# vtl import vtl01 barcode TST000L1 count 20 ..imported 20 of 20 tapes...

8. Display the imported tape volumes:

# vtl tape show all ... processed 20 tapes... Barcode Location Type Size Used Compression -------- -------- ----- -------- ------ ----------- TST000L1 vtl01 LTO-1 100.0 GB 0.0 GB 0x TST001L1 vtl01 LTO-1 100.0 GB 0.0 GB 0x

2. Host Configuration and Setup

This section details configuration and setup steps for hosts that run the NetWorker backup application.

2.1. Windows HBA Setup Notes Data Domain has tested the VTL feature with various HBA cards and drivers. See the Data Domain Support web site, Compatibility Matrices, DD400 Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php) for supported HBA combinations. Note: When the VTL devices are discovered, Data Domain recommends configuring the driver for persistent binding. QLogic SANBlade Series Use the SCSI Miniport driver for both Windows 2000 servers and Windows 2003 servers. The driver needs no specific set up for use with a restorer.


9/19/07 8 of 31

EMULEX LP Series When using the EMULEX FC Port Driver on the Windows server, run the EMULEX configuration utility. 1. From the Start menu, select elxconfig. 2. In the Adapter Controls section, select the controls (or accept the defaults) shown below:

The controls to set are: Automatically Map SCSI Devices Query name server for all N-Ports Register For State Change Lun Mapping Disable Target Reset for Tape Devices Scan in Device ID Order Enable FCP-2 Recovery

3. The World Wide Port Name section of the configuration tool displays external HBAs known

to the system. Select the entry for the Data Domain HBA. The Lun Map button becomes active.


9/19/07 9 of 31

4. Click on Lun Map. A window similar to the following appears.

5. Select one drive and click Add. 6. One drive at a time, select the next drive and click Add for every drive. Do the same with the

media changer until you have added the controls to every device. 7. Click Done. 8. Click Apply Changes. 9. Reboot the Windows server.

2.2. Solaris HBA Setup Notes Before setting up an HBA card in the Solaris backup server, complete the VTL configuration on the Data Domain restorer. Note: After the VTL devices are discovered, Data Domain recommends configuring the driver for persistent binding. Emulex LP Series HBA Download Emulex drivers from:

http://www.emulex.com/ts/downloads/solpci/sol.html Uncompress or untar the driver and use the pkgadd utility to add the driver.


9/19/07 10 of 31

QLogic SANBlade Series HBA You can download QLogic driver packages from:

ftp://download.qlogic.com/drivers/ To set up a QLogic HBA: 1. Log into the Solaris system as root. 2. Download the QLogic driver package. 3. Run the following two commands:

> uncompress qla2300.sparc_pkg.Z > pkgadd -d qla2300.sparc_pkg

2.3. Set Up for Windows Backup Servers After configuring VTL on the restorer and connecting the restorer and backup server HBAs, do the following procedures on Windows backup servers. Note: If you are using the EMULEX FC Port Driver for the HBA in the Windows system, see Windows HBA Setup Notes on page 7 and configure the FC Port Driver now. Other HBA drivers do not need manual configuration. Install a Tape Drive and Medium Changer Device Driver 1. Obtain a tape device driver for both Windows 2000 and Windows 2003. For NetWorker, use

the IBM LTO tape driver. Note that if a prior version of the IBM LTO tape driver was loaded previously, you must unload the earlier version prior to loading the later version (uninstall.exe)

Go to the following URL:

http://www-1.ibm.com/support/docview.wss?rs=543&uid=ssg1S4000189

2. Data Domain suggests obtaining a medium changer device driver for both Windows 2000 and Windows 2003. For NetWorker, use the STK Library Changer Driver (L-Series).

Go to the following URL: http://www.storagetek.com/support/drivers.html

3. Data Domain suggests installing the medium changer device driver on the Windows system. 4. Install NetWorker software on the Windows system. 5. Reboot the Windows system (reboot even if Networker was previously installed).


9/19/07 11 of 31

6. To check that the Windows server sees all the Data Domain devices, open Device Manager on the Windows server. Look at Tape Drives for drives and Medium Changers for the medium changer. The final display should show a tape drive for each virtual tape drive that you created on the restorer and the medium changer, as shown below:

7. Right click on any one of the tape drives and select Properties. 8. Click on the Driver tab. The drive information should be the same as in the examples below:


9/19/07 12 of 31

9. Right click on any one of the medium change and select Properties. 10. Click on the Driver tab. The drive information should be the same as in the examples below:

11. On the Windows system, open a command window. 12. Enter the inquire command (a NetWorker command). The output includes tape drive

names that start with a double backslash, such as \\.\Tape0.

Tape drive names


9/19/07 13 of 31

13. In the command window, enter the NetWorker jbconfig command.

14. Select 2) Configure an Autodetected SCSI Jukebox. Use the tape drive names displayed by

the inquire command to configure the library.

2.4. Setup for a Solaris Backup Server with a QLogic or Emulex HBA This section provides setup notes for Solaris Backup servers and assumes that the HBAs are already installed and the drivers configured properly. 1. If the NetWorker software is not already installed on the Solaris system, install NetWorker.

When the installation for LGTOserv? asks for tape drive names, do not enter any names. 2. On the Solaris system, edit the file /kernel/drv/st.conf. Change the line:

name="st" parent="qla2300" target=0;

to 32 lines in the following format starting with lun=0. The target=0 in the example is for systems with no targets previously defined. The target number is the same for all entries from one restorer. (After adding the lines, remain in the editor as the next steps in this procedure require further editing of /kernel/drv/st.conf.)

name="st" parent="qla2300" target=0 lun=0; name="st" parent="qla2300" target=0 lun=1; name="st" parent="qla2300" target=0 lun=2; . . .

3. While still editing /kernel/drv/st.conf, find the tape-config-list line at the

start of the device list. The line is usually commented out. Uncomment the line and add a line for the IBM ULTRIUM as shown below:

tape-config-list= "IBM ULTRIUM-TD1", "IBM Ultrium-1", "LTO-1";

4. In /kernel/drv/st.conf, the end of device list is similar to the following:

#"Seagate STT3401A", "Seagate Hornet Travan 40", "T40", #"OnStreamADR Series", "On Stream USB Tape", "OnStream";


9/19/07 14 of 31

Add the following two lines after the end of the device list and then save and quit editing the file:

## from ftp://ftp.legato.com/pub/HW_Support/compatguide/st.conf.supp.txt LTO-1 = 1, 0x36, 0, 0x29639, 1, 0x40, 0x00;

NOTE: The following step, 5. Update the Solaris system , is not done with Solaris 8 systems. Reboot a Solaris 8 system at this time and then go to step 6. Reboot with the command:

> reboot -- -r 5. Update the Solaris system (except for Solaris 8) with the following commands to read the

changed configuration files. Solaris 8 systems must be rebooted.

> update_drv st > devfsadm -C > devfsadm -c 'scsi'

6. Use the lusbinfo command to identify the QLogic HBA and the state of the HBA.

NOTE: With Solaris 10, skip this step and go to the next numbered step.

With a single-port QLogic HBA and Solaris 9, the display should be similar to the output shown below. The second entry in the display, Bus #1, is the QLogic HBA card (identified as pci1077,1000).

# lusbinfo # busses: 4 Bus #0 is 'ide0', dma_max=16777216, initiator ID=127, ntargets=126, nluns=0 Bus #1 is 'pci1077,1000', dma_max=16777216, initiator ID=127, ntargets=126, nluns=32, lus cloning enabled

If the QLogic HBA card entry from the above command output does not include the lus cloning enabled tag, edit the file /usr/kernel/drv/lus.conf and, for any of the QLogic 2300 series, make the following entry in the list of known-scsi-adapters:

pci1077,100:126-32C

With a dual-port QLogic HBA and Solaris 9, the display should be similar to the output

shown below. The second and third entries in the display, Bus #1 and Bus #2, are the QLogic HBA ports (identified as pci1077,1010 and pci1077,1011).

# lusbinfo # busses: 4 Bus #0 is 'ide0', dma_max=16777216, initiator ID=127, ntargets=126, nluns=0 Bus #1 is 'pci1077,1010', dma_max=16777216, initiator ID=255, ntargets=126, nluns=32, lus cloning enabled


9/19/07 15 of 31

Bus #1 is 'pci1077,1011', dma_max=16777216, initiator ID=255, ntargets=126, nluns=32, lus cloning enabled

If the QLogic HBA card entries from the above command output do not include the lus cloning enabled tag, edit the file /usr/kernel/drv/lus.conf and, for the dual-port QLogic series, make the following entry in the list of known-scsi-adapters:

pci1077,101:126-32C

With a QLogic HBA and Solaris 8, the display should be similar to the output shown

below. The second entry in the display, Bus #1, is the QLogic HBA card (identified as pci1077,90

# lusbinfo # busses: 4 Bus #0 is 'ide0', dma_max=16777216, initiator ID=127, ntargets=126, nluns=0 Bus #1 is 'pci1077,90', dma_max=16777216, initiator ID=127, ntargets=126, nluns=32, lus cloning enabled Bus #2 is 'pci1000,210', dma_max=16777215, initiator ID=7, ntargets=8, nluns=7 Bus #3 is 'pci1000,211', dma_max=16777215, initiator ID=7, ntargets=8, nluns=7

If the QLogic HBA card entry from the above command output does not include the lus cloning enabled tag, edit the file /usr/kernel/drv/lus.conf and, for any of the QLogic 2300 series, make the following entry in the list of known-scsi-adapters:

pci1077,9:126-32C

7. Connect the fiber cabling for physical connectivity between the Solaris system and the

restorer. 8. For systems using Solaris 7, 8, and 9, update the system with the following commands. Do

not do the update with Solaris 10.

> reboot -- -r > update_drv lus > devfsadm -C > devfsadm -c 'scsi'

9. Enter the following command to display the known tapes:

> ls -l /dev/rmt lrwxrwxrwx 1 root other 49 Aug 15 14:26 /dev/rmt/0 -> ../../devices/pci@1f,2000/fibre-channel@1/st@0,6: lrwxrwxrwx 1 root other 49 Aug 15 14:26 /dev/rmt/1 -> ../../devices/pci@1f,2000/fibre-channel@1/st@0,7:


9/19/07 16 of 31

10. Enter the NetWorker jukebox configuration command:

> jbconfig 11. Select 2) Configure an Autodetected SCSI Jukebox. 12. Configure the library as appropriate for your site. Manually enter the tape drives as part of the

configuration (automatic detection does not work). Tape drive entries are similar to:

/dev/rmt/0cbn 13. Load a tape into a VTL virtual drive, drive 2 for example. On the storage node, enter a

command similar to the following to check that drive 2 is seen:

# mt -f /dev/rmt/1 status IBM Ultrium LTO tape drive: sense key(0x0)= No Additional Sense residual= 0 retries= 0 file no= 0 block no= 0

2.5. RedHat Linux Setup Guidelines For RedHat releases that are supported with the restorer VTL feature, see the Data Domain Support web site, Compatibility Matrices, DD400 Backup Software compatibility using VTL entry (https://support.datadomain.com/compat_matrix.php). Take the following actions on the RedHat system (with some exceptions as noted) before configuring backup software or otherwise trying to access a restorer as a tape device. Note: If the RedHat kernel on your backup server is not already enabled to handle multiple LUNs, follow either the procedure in the next heading, Enable Multiple LUNs in the Kernel or the procedure in Search for Multiple LUNs with no Kernel Changes at the bottom of this page. Enable Multiple LUNs in the Kernel With multiple LUNs, the Linux kernel on your backup server must recognize multiple LUNs. By default, most Linux kernels do not recognize multiple LUNs. Note: The procedure and commands in this section are general guidelines to reach a specific end result -- enable multiple LUNs. Because of the fluid nature of Linux releases and patch levels, the procedure and commands may not be appropriate for your Linux system. If the general procedure and commands in this section for making kernel changes are not familiar to you or do not apply to your specific Linux release, please contact your Linux vendor for detailed instructions. Data Domain cannot assume any responsibility for the accuracy and usability of the procedure and commands with a specific Linux release. 1. Obtain and install kernel sources for your Linux release. If needed, contact your Linux

vendor for assistance. 2. On your Linux backup server, go to the directory: /usr/src/linux.


9/19/07 17 of 31

3. Run one of the following commands as appropriate for your system:

# make xconfig # make meunconfig

4. Select Device Drivers. 5. Look at SCSI Device Support for (depending on the Linux release) something similar to

Probe all Luns on each SCSI device or SCSI-multi-LUN. 6. Make sure that the checkbox for SCSI Device Support is checked. Search for Multiple LUNs with no Kernel Changes 1. From the web, find the open source script rescan-scsi-bus.sh and put the script on the

backup server under the /etc directory. 2. Create the file /etc/rc.modules. Add the following lines to the file to automatically

load the HBA (assumed to be a QLogic 2300) driver at boot time and to have the system scan for multiple LUNs.

modprobe qla2300 modprobe st /etc/rescan-scsi-bus.sh -l -w -r -c

1. Do a standard compile and install of the Linux kernel. If needed, contact your Linux vendor

for assistance. 2. On the restorer, create the library and tapes and import the tapes into the library. 3. Make the network connection between the restorer and the Linux system. 4. Boot the Linux system with the new kernel. 5. On the Linux system, enter the following command. The command output should include

entries for each restorer tape device and for the restorer library. If the /proc/scsi/scsi file exists and includes the restorer device entries, then you are done.

# cat /proc/scsi/scsi

6. If the /proc/scsi/scsi file does not exist or if the file does not have the restorer device

entries, then continue with the next step in this series. 7. On the Linux system, create a file /etc/rc.modules with + x permission. Enter the

following three lines in the file:

modprobe qla2300 modprobe sg modprobe st

8. Reboot the system.


9/19/07 18 of 31

9. Run the following command again to see the restorer devices.

# cat /proc/scsi/scsi 10. Change directory to:

# cd /proc/scsi/sg 11. Enter the following command to check the LUNs and library. Type 1 (one) devices are tape

drives and type 8 devices are libraries.

# cat device_hdr devices host chan id lun type opens qdepth busy online 0 0 0 0 1 0 64 0 1 0 0 0 1 1 0 64 0 1 0 0 0 2 1 0 64 0 1 0 0 0 3 1 0 64 0 1 0 0 0 4 8 0 64 0 1

12. Look in the /dev directory, which should contain:

An sgX file for each device. The files should have the same numbering as listed under the lun column of the cat device_hdr devices command. For example, /dev/sg0 through /dev/sg4. An stX and an nstX file for each type 1 device. The files should have the same numbering as listed under the lun column of the cat device_hdr devices command. For example, /dev/st0 through /dev/st3 and /dev/nst0 through /dev/nst3.

2.5.1. Troubleshooting Tips NetWorker returns "end of tape" messages when attempting to backup to a restorer that is full. On the restorer, run the filesys clean command to clear space used by stale data. The NetWorker messages are similar to: nsrjb: Jukebox error: Thu 10:16:46 AM label write, Physical end of tape encountered

2.6. NetWorker 7.3 and NDMP on Windows using VTL The NetWorker 7.3 graphical user interface for Windows changes from earlier releases. This section describes the settings needed to make a Data Domain VTL visible to NetWorker 7.3 when using a Network Appliance filer. The following graphic shows a configuration with a NetWorker storage node, Network Appliance filer, and a Data Domain restorer.


9/19/07 19 of 31

For a Network Appliance filer to discover virtual devices on a restorer, the restorer must have at least one library and a LUN0 (LUN zero) must exist in one library. On the restorer, use the vtl lunmask show command to list libraries and LUNs. If no LUN masks exist, all restorer VTL libraries reside in the Default LUN mask group with a media changer assigned to LUN0. When a filer and restorer are connected through a Cisco MDS Fibre Channel switch, any VTL changes on the restorer, such as the creation or deletion of VTLs or LUN masks, are not dynamically updated by the filer. To force the filer to discover changes:

Run the following commands on the restorer after changes and to check that VTL is enabled:

# vtl disable Disabling VTL, please wait VTL is disabled. # vtl enable Starting VTL, please wait VTL is enabled. # vtl status VTL admin_stat: enabled, process_state: running

In some cases, the switch port where the restorer is attached may need to be disabled and

enabled.

To discover and configure a restorer VTL attached to a Network Appliance filer, perform the following steps. 1. Open the NetWorker Administration interface. Right click on Clients and select New.

NetApp 1 Storage Node

DDR1


9/19/07 20 of 31

2. In the Create Client window, enter the fully-qualified domain name of the Network

Appliance filer, vader.datadomain.com in this example.

3. In the Group area, accept the default or select a group. Groups can be added later. 4. Select Apps & Modules from the tabs at the top of the window. 5. In the Access area, enter the name and password of the NDMP user


9/19/07 21 of 31

6. In the Backup command box, enter the command: nsrndmp_save -T dump. 7. In the Backup area, select (activate) the Ndmp checkbox. 8. Select the Globals (2 of 2) tab from the top of the window. 9. In the Storage nodes area, enter the fully-qualified domain name of the Network Appliance

filer. The filer is seen as the storage node because it handles the Data Domain restorer's VTL.

10. Click OK at the bottom of the Create Client window. The new client should now show in the

Clients list in the main NetWorker Administration window.


9/19/07 22 of 31

11. Select Devices from the icons at the top of the administration window. 12. Right click on Storage Nodes and select New. 13. In the Identity area, enter the fully-qualified domain name of the filer.

14. In the Identity area, click the ndmp button. 15. Click OK at the bottom of the Create NSR Storage Node window.


9/19/07 23 of 31

16. Right click the new storage node

(vader.datadomain.com in this example) and select Scan for devices.

17. Select the new storage node 18. Enter the NDMP user name and password in the

appropriate boxes. 19. Click Start Scan at the bottom of the window. 20. To track the scan, select the Monitoring icon at

the top of the administration window and select Log.

21. After the scan completes, select the Devices icon at the top of the administration window.


9/19/07 24 of 31

22. Expand Libraries and the new storage node entries in the left panel to see the discovered device list. The wrench icon in front of each device means that the device is not configured.

23. Right click on the new library entry ([email protected] in the example above) and

select Configure library.

24. Click on the Check All button. 25. Click Start Configuration at the bottom of the Configure Library window. 26. The configuration may take a few minutes. The administration window display updates when

configuration is done.

27. Right click on the configured library ([email protected] in the example above) and select

Properties.


9/19/07 25 of 31

28. Under the General tab, click the Auto clean checkbox to disable the feature. After clicking,

the box should not show a check mark. 29. Select the Configuration tab at the top of the Properties window.

30. Click on the Barcode reader and Match bar code labels checkboxes to activate the features.

After clicking, the boxes should show check marks. 31. Click OK at the bottom of the Properties window. 32. In the administration window, click on the configured library under Libraries in the left

panel, [email protected] in the example below.


9/19/07 26 of 31

33. Under Device in the center panel, right click on one of the devices and select Label.

Click on the Fast/Silent button to activate the feature.

Click OK at the bottom of the Label Library Media window.


9/19/07 27 of 31

Click OK at the bottom of the Library Operation window that appears. As noted in the window, you can select the Monitoring icon at the top of the administration window and then the Operations tab to monitor progress in creating the library.

3. Tuning NetWorker Tape Devices

Use the nwadmin or nsradmin tool to make the following changes to increase backup performance and realized compression:

Change the default target sessions for each NetWorker tape device to 1 (one). The default is 4. The change forces one stream for each device. Originally used to stop the shoe-shining effect for low performance tape streams, the feature is not an issue when using a disk-based restorer VTL.

4. Replication and the VTL Feature

Figure 1 shows the recommended configuration for replication with the Data Domain VTL feature. VTL replication is set up as one-to-one, meaning that one replication source sends data to one replication destination. The destination MUST BE a destination only. The destination cannot act as a source. Also, be aware of the following items: Replication is set up as one-to-one, meaning that one replication source sends data to one

replication destination and the destination does not act as a source. Both storage nodes use the same version of NetWorker and are in the same domain. Figure 1 Reference Configuration

Storage Node A Storage Node B

DDR1 Source

DDR2 Destination

Replication


9/19/07 28 of 31

Configuration Notes: The file index, media database, and resource database have the following attributes: All are exported and imported from the source side to the destination side as needed. All are stored on a disk storage unit on the restorer accessed through CIFS or NFS. All are replicated along with backup data. Also, the following apply: The NetWorker file index, media database, and resource database are stored as an advanced

file type on the Data Domain restorer accessed through CIFS or NFS. The NetWorker file index, media database, and resource database are replicated along with

backup data. Throughout this section, such information is referred to as metadata. The backup schedule is weekly fulls and daily incrementals.

4.1. Performing a VTL Replication with NetWorker This section provides an example of how to replicate the originator VTL tape cartridges and clone to physical tape from the replica VTL using the reference configuration (above) as a guide. For detailed information on tape cloning, see Chapter 9 of the NetWorker Multiplatform Version Administration Guide. The procedure is: 1. Configure replication for /backup/vtc/Default from the source restorer, DDR1, to the

destination restorer, DDR2. 2. Initialize replication for /backup/vtc/Default and wait for initialization to complete.

The amount of time to complete depends on a number of factors, the most important being the amount of data and total bandwidth available.

3. On the source DDR1, create the VTL and tapes. 4. On the destination DDR2, create the VTL (which may have a different number of tape drives

than the DDR1 VTL and may have greater than or equal number of slots). 5. On the source DDR1, import tapes from the DDR1 virtual vault to the VTL. For example,

vtl import vtl01 barcode TST000L1 count 20. The command imports 20 tapes from the virtual vault into the VTL named vtl01.

6. Configure NetWorker to use the source VTL on DDR1 and label/inventory tapes. Use the

jbconfig command line utility. Include the file index, media database, resource database, and backup policy.


9/19/07 29 of 31

7. Configure NetWorker to backup the file index, media database, and resource database to a DDR1 filesystem. The configuration includes creating an advanced file type on storage node 1. Include the backup policy. Use a location on DDR1 similar to: /backup/storage _node_one/metadata1_backup to store the file index, media and resource databases.

8. Perform backup(s) and NetWorker metadata backup(s) to the DDR1 VTL. Wait for the

backups of both the catalog and source data to complete. 9. On DDR1, enter the command replication sync for /backup/vtc/Default. This

ensures that the VTL cartridges are in sync on the replica. Be sure to wait for the command to complete.

10. On DDR1, enter the command replication sync for the NetWorker file index, media,

and resource databases, for example /backup/storage_node_one/metadata1 _backup. The command ensures that the NetWorker metadata is in sync on the replica.

11. To prevent media ID duplication:

a. On DDR1, use the vtl export command to move the virtual tapes into the DDR1 virtual vault.

b. On DDR2, use the vtl import command to move the virtual tapes from the DDR2

virtual vault to the DDR2 VTL. 12. Re-assign the tape cartridges to the destination VTL to prevent media ID conflicts. Use

NetWorker and the nwadmin GUI to transfer ownership. The transfer includes re-inventorying the virtual tape volumes.

13. Perform a volume or save set clone. Use DDR2 VTL and virtual tape volumes as the source

and the physical tape library as the destination. See chapter 9 of the NetWorker Multiplatform Version Administration Guide. Keep the following in mind:

A minimum of two storage devices must be enabled: one to read the existing data and one

to write the cloned data. If libraries with multiple devices are used, the NetWorker server mounts the volumes

required for cloning automatically. If stand-alone devices are used, mount the volumes manually. A message displays in the Alert tab of the Monitoring option that indicates which volumes to mount.

The destination volume must be a different volume from the source volume, and must belong to a clone pool.

The source volume is the original volume, and the destination volume is the volume to which data is cloned.

You must be a member of the NetWorker Administrators group.


9/19/07 30 of 31

4.2. Save Set Cloning Using a Destination VTL Save sets or volumes can be automatically or manually cloned. The following is an example of a manual clone. To manually clone a save set, first query the media database to locate the correct save set. After querying the database, select the save set and begin the cloning operation. Again, see Chapter 9 of the NetWorker Multiplatform Version Administration Guide for all of the details and options for tape cloning. To manually clone a save set: 1. From the nwadmin Administration window, click Media. 2. In the expanded left pane, select Save Sets. 3. In the right pane, select the Query Save Set tab. Use the Query Save Set tab to specify options to limit the range of save sets displayed. All query options are optional except for the date. A date range must be selected. 4. Enter values in any of the following attributes to limit the search: Client Name, Save Set, Save Set ID, Volume, Pool. 5. Use the Copies attribute to limit the search to only those save sets that are already cloned.

Select a value of greater than (>), equal to (=), or less than (


9/19/07 31 of 31

9. Click the Save Set List tab. The save sets that fit the criteria appear in the Save Sets list. For example, to sort the list in alphabetical order by client name, click the top of the Client column. 10. Select the save sets to clone from the Save Set list. 11. From the Media menu, select Clone. 12. From the Target Clone Media Pool list, select a clone pool. 13. Click OK and then click Yes on the confirmation screen. The cloning process begins. Watch the process to ensure that it finishes successfully. When the initial clone is complete, do the following: After the next incremental or full backup, ensure that the NetWorker metadata is backed-up to the advanced file type and the source data is backed-up to the DDR1 VTL. On DDR1, enter the command replication sync for /backup/vtc/Default to

see that the VTL cartridges replicate to DDR2. Wait for the command to complete. On DDR1, enter the command replication sync for the metadata: /backup/

storage_node_one/metadata1_backup. to see that the NetWorker metadata replicates to DDR2.

With large amounts of data, Data Domain recommends defining volume pools to track the save sets.

Documents

Vtl Legato in Datadomain