Configuring Your IP4700 Device for Use with Backup Software P/N 069001088-00 This document is for customers who have an IP4700 NAS storage device system and want to use backup software with it. While it is beyond the scope of this document to explain how to use the Legato™ NetWorker® and Veritas NetBackup™ applications, it provides tips and supplemental information for configuring and using these third-party backup applications with the IP4700 system.
Backup Terminology This document assumes the following: • NetBackup 3.4 DataCenter server software and the Network Data Management Protocol (NDMP) option, or NetWorker V6.0.1-001 with nsrndmp_recover is installed on your system. (For more information about NDMP, see your backup software documentation.) • The network is configured properly. • Your IP4700 system is properly configured on the network, including hostname resolution. • The EMC NDMP license is installed on your IP4700 system.
Backup Terminology Term Definition Backup software The software running on the backup server that controls the flow of backup data from backup clients to the backup media. Also, backup agent software usually runs on the backup clients. Catalog or Index A collection of meta-data that identifies the details of a backup, for example, the names of the clients backed up, the names, file sizes, and dates of the data backed up, and the location of the files on the backup media. Used to restore files.
Backup Configurations Backup Configurations This section lists all the configurations and components that EMC CLARiiON® backup and restore environments for network attached storage (NAS) devices support. Each IP4700 has two storage processors (SPs). Each SP has one SCSI host bus adapter (HBA), for connection to tape drives and tape libraries.
Backup Configurations NDMP Local Backup In an NDMP local backup configuration, shown below, zero, one, or more tape drive(s) per SP is connected directly to the SCSI HBA in the IP4700 system, and backup data flows from the IP4700 system directly to the tape drive. Using the LAN, the backup server uses NDMP to instruct the IP4700 system to perform the backup. The backup server can also back up LAN clients. The backup server still manages the index, or catalog data.
Backup Configurations NDMP Local Library Backup In an NDMP local library configuration, as shown below, the tape drives and the library changer device in a tape library are connected to SCSI HBAs in the IP4700 system. The backup server controls the library changer device attached to the IP4700 via a SCSI pass-through function in the IP4700 system. IP4700 backup data flows from the IP4700 system directly to the tape drive.
Backup Configurations NDMP Local Shared Library Backup In an NDMP local shared library configuration, as shown below, one or more tape drives in a shared library are connected to SCSI HBAs in the IP4700 system. The backup server controls the library changer within the library. The backup server can also be connected to other tape drives within the library. NAS backup data flows from the IP4700 system directly to the tape drive.
Backup Configurations NDMP Remote Backup Only Legato NetWorker supports NDMP remote backup. In an NDMP remote backup configuration, a backup server directs an NDMP host to send NDMP data over the network to a backup server that writes this data to a tape drive connected to the backup server.
Backup Configurations NDMP Three-Way Backup In an NDMP three-way backup configuration, a backup server directs one IP4700 system, without a local tape drive, to send NDMP data over the network to another IP4700 system with a local tape drive. NAS backup data flows from the primary IP4700 system, which is the device attached to the tape drive, directly to the tape drive.
Backup Configurations LAN IP4700 Application server IP4700 Legend Backup server Backup data Backup control Index Primary backup data paths: IP over Ethernet, then SCSI over SCSI cables Non-NDMP NFS or CIFS-Specific Public LAN 10 EMC1734 A non-NDMP Network File Server (NFS®) or Common Internet File System (CIFS)-specific public LAN configuration, also called an IP4700 network drive backup, is similar to a standard LAN-based backup.
Backup Configurations backup data from the IP4700 system and then retransmit this data to the backup server. The backup server then sends the data to the tape library. This method retains only the file system attributes that the backup client uses. Therefore, if NFS and CIFS clients usually access the backup data and the NFS client is used for backup, the CIFS attributes are lost on the backed up copy. The non-NDMP NFS or CIFS-specific public LAN configuration is shown below.
Backup Configurations Non-NDMP NFS or CIFS-Specific Private LAN A non-NDMP NFS or CIFS-specific private LAN configuration, also called IP4700 network drive backup, is available only with NetBackup. It is similar to a standard private LAN backup in that the backup server communicates with the client computer systems to control the backup. The main difference is that the client systems must first retrieve their backup data from the IP4700 system, and then retransmit this data to the backup server.
Backup Configurations Private LAN LAN IP4700 IP4700 Application server (NFS) UNIX Application server (CIFS) Windows Legend Backup data Backup server Backup control Index Primary backup data paths: IP over Ethernet Configuring Your IP4700 Device for Use with Backup Software EMC1736 13
Configuring Your Backup Hardware Configuring Your Backup Hardware You will need to add the devices you need to support your backup configuration. This section explains how to add standalone tape drives, local shared libraries, and local tape libraries to your IP4700 system. Adding a Standalone Tape Drive To use NetBackup NDMP with the IP4700 system, you must connect a tape drive directly to one of its SCSI buses. The IP4700 provides one low voltage differential (LVD) SCSI bus per SP.
Configuring Your Backup Hardware Adding a Local Tape Library To use a tape library connected directly to an IP4700 SP’s SCSI bus, you need the following: • IP4700 1.1 software • an LVD/SE-to-HVD SCSI bus converter if the drive in the library is differential (HVD) For more information about the LVD/SE-to-HVD SCSI bus converter, refer to the IP4700 Quick Start Guide. A tape library contains as many SCSI devices as there are tape drives, as well as the library changer or “robot.
Configuring Veritas NetBackup Software The IP4700 Administration screen displays the tape drives or libraries that are connected to the system, as shown in the following example. This example shows one DLT7000 drive on SP A and two tape drives on SP B, one DLT7000 and one AIT-2. SP A’s drive has Quantum firmware V95; whereas, SP B’s DLT has Quantum firmware V100. The AIT-2 drive has firmware 2.00.
Configuring Veritas NetBackup Software The following table defines some key NetBackup concepts. Concept Definition Storage unit A collection of standalone tape drives or drives in a tape library that have similar characteristics. Robot A tape library. Master server A server that retains the catalog or index of backed up files. The master server controls all backups. Media server A system with direct access to tape drives for backup.
Configuring Veritas NetBackup Software Configuring NetBackup for Standalone Tape Drives Setting Up an NDMP Login This section describes how to set up an NDMP login and create a device, storage unit, and class when configuring NetBackup for standalone tape drives. It also describes how to test the tape drive and perform a test backup after you have configured the NetBackup software. You must inform NetBackup how to log in to the NDMP hosts. For each IP4700 SP, set up the NDMP login as follows: 1.
Configuring Veritas NetBackup Software 3. In the Add Drive window, make sure that the NetBackup master server is listed as device host, and specify the following: a. In the Drive Type field, select the correct drive for your configuration, for example, DLT or 8mm Cartridge. b. In the Drive Name field, type a descriptive name for the drive, for example, dlt-1. c.
Configuring Veritas NetBackup Software 5. Click the Storage Unit Type Properties tab, and then: a. make sure that the correct NetBackup media server is in the NetBackup media server field. b. Make sure that the storage unit lists the same type of tape drive you selected when you created the device in the previous section, for example, 8mm Cartridge. c. If using a robot, make sure that the correct robot type is indicated. d. Click OK.
Configuring Veritas NetBackup Software The Add New Class window appears, where you will specify the attributes, schedules, backup files, and clients for the class. 4. In the Add New Class window, select the Attributes tab, and make sure that the class type is NDMP. 5. In the Host Name tab, specify the hostname for the client, and make sure that it is the type NDMP. 6. In the Files tab, specify the name of the IP4700 volume, for example, /A0, that you want to back up.
Configuring Veritas NetBackup Software The Backup Policy Management window looks something like the following. The SET HIST=Y line in the files definition of the class is superfluous because the NDMP HIST variable is set to Y by default. You can set it to N to disable the NDMP host from sending file history information to the backup server. In this case, you cannot restore file by file. 8.
Configuring Veritas NetBackup Software You can have only one NDMP backup session running on a given IP4700 SP at a time because only one NDMP session is supported in the IP4700 software. Testing the Tape Drive Now that you have configured the NetBackup software for a standalone tape drive, test the tape drive to make sure it works properly by following these steps: 1. From the NetBackup Administration window, click Device Monitor. The Device Monitor displays your configured drives. 2.
Configuring Veritas NetBackup Software b. Click the drive row again, and then right-click and choose UP Drive to enable the drive. Within a few seconds the tape drive’s “busy” or “in use” LED (depending on the drive type) should flash as NetBackup reads the first block to determine the tape label. In another few seconds the drive LEDs should stop flashing, and the Device Manage columns for the drive’s Ready and Writable state indicate “Yes,” and the drive state remains as AVD. c.
Configuring Veritas NetBackup Software The following table explains the states shown above. Performing a Test Backup State Reason The first two drives are DOWN. Assuming everything else is set up properly, this usually indicates a hardware problem. In this case these two drives were removed from the SCSI bus. The third drive is ready and writable, but no media ID is listed. A blank tape is in the drive. The fourth drive is ready and writable, and the media ID is listed.
Configuring Veritas NetBackup Software 4. To see details, double-click the line, and then select the Detailed Status tab to see further information about the progress of the job, including transfer rate, as shown below.
Configuring Veritas NetBackup Software Troubleshooting The following table lists some of the more common error codes you may see if various problems occur. It also explains each error code and suggests what you can do to resolve it. Error Code Cause Action 219 The specified storage is not available, or all drives in the required storage unit are DOWN. Note: Sometimes the cause of this error is unrelated to tape drives. Stop and restart the NetBackup daemons using stoptlid, then tlid.
Configuring Veritas NetBackup Software Error Code Cause Action 96 No media is available. Make sure there is a tape in the drive, and the drive state is AVD, as indicated by the Device Manager. Assuming the data on the tape is not required, allow NetBackup to use the tape by specifying bpmedia -unfreeze -ev media_id, where media_id, is the ID assigned to the tape by NetBackup. Also try forcing NetBackup to reuse the tape by specifying bpexpdate -d 0 -ev media_id.
Configuring Veritas NetBackup Software Sometimes NetBackup cannot successfully use tapes. The tapes may be in another format and cannot overwrite them. You can specify that NetBackup overwrite them. On a Windows system, from the main GUI, select Start → Configure NetBackup. Right-click the master server, select Read/Write Properties from the expanded menu, select the Media tab, and then click all the overwrite options. On a Solaris system, add to the bp.
Configuring Veritas NetBackup Software NetBackup troubleshooting documentation. In the server’s Global NetBackup Attributes screen, you can reduce the length of time logs are retained; otherwise, your system may run out of space. If there is a problem that you have not been able to resolve, you can create additional log files to further investigate the problem. In the volmgr/database directory, create a file called ndmp_debug, and using the text editor, type 65535 in the file.
Configuring Veritas NetBackup Software When you click Tape Drives in the IP4700 Administration window, you will see all five devices reported, as shown in the following example. In this example, the library controller (the robot) and two drives are on SP A; the other two drives are on SP B. 3. To determine whether your hardware and software configurations are okay, run set_ndmp_attr -verify.
Configuring Veritas NetBackup Software This process attempts NDMP login the same way it does for standalone tape drives, opens the robot device, sends a SCSI Inquiry command to it, and reports information similar to that in the following example. C:\Program Files\VERITAS\Volmgr\bin>set_ndmp_attr -verify dakota11-1a Connecting to host "dakota11-1a" as user "Administrator"... Waiting for connect notification message... Opening session with NDMP protocol version 2...
Configuring Veritas NetBackup Software 2. Select the robot type as TLD for a DLT library or TL8 for an 8mm library. The robot number is global across the NetBackup configuration; therefore, select an appropriate number if the backup system already has one or more libraries. 3. Click the Robot control is attached to an NDMP host radio button. 4. In the NDMP host name field, type the IP4700 SP’s hostname. 5. Click Browse. The Robot popup window appears. 6.
Configuring Veritas NetBackup Software The Add Drive window appears, as shown in the following example. 2. Select the device host, which is your NetBackup Master Server. 3. Select the drive type that is appropriate to the robot type (DLT drive for a TLD robot, and 8mm drive for TL8 robot). 4. Type any name you want for the drive name. 5. For the device name, type ndmp-hostname:tape-drive, the same as for standalone drives. 6. Check the box, Drive is in a robotic library since this drive is in a library.
Configuring Veritas NetBackup Software Testing the Library To make sure there is communication with the robot, follow these steps: 1. In the Media and Device Management window, right-click the robot, and select Inventory. 2. Click Inventory Robot. 3. Click Start. Within about 15 seconds the robot contents should scroll by. This display lists each slot and whether it is empty or full and shows the bar code label of the tape (if present). We strongly recommend that you use bar codes on library tapes.
Configuring Veritas NetBackup Software C:\Program Files\VERITAS\Volmgr\bin>tsdtest -r dakota11-1a:/dev/c0b0t0d0 -d1 dakota111a:/dev/c0b0t1d0 Opening C:\Program Files\VERITAS\Volmgr\database\ndmp.dakota11-1a._dev_c0b0t0d0 Enter tsd commands (? returns help information) ? To exit the utility, type q or Q.
Configuring Veritas NetBackup Software Setting Up Storage Units and Classes You set up storage units and classes the same way you do for standalone tape drives. Refer to the sections about creating a storage unit and class for standalone tape drives. The only difference is that you need one storage unit for drives of the same type on each SP. In our example, we need a storage unit on SP A for its two tape drives and another storage unit on SP B for its two tape drives.
Configuring Veritas NetBackup Software Configuring NetBackup for Mapped Network Drive Backup You can also back up IP4700 volumes as network drives, but at a high cost in network traffic. Also, this backup method does not save UNIX and Windows file attributes. Restoring a file backed up via a network drive eliminates the UNIX file attributes and vice versa. Network drive backup is not appropriate when the same IP4700 files are shared by UNIX and Windows systems.
Configuring Veritas NetBackup Software the snap. The backup provides a consistent image with none of the file changes that take place during the backup. Be sure to define enough space for the snap area. Other applications can also use the copies. Fast incremental, described in the next section, and SnapView use the same area. Up to 85% of the volume can be a reserve area.
Configuring Legato NetWorker Backup Software Using the Fast Incremental Option for Backup The Fast Incremental option reduces the backup time and makes it easy to manage and move files. The Fast Incremental option allows the IP4700 file system to retain a file that describes which files have changed. It uses this file to determine which files to back up rather than requiring meta-data for each file be read to determine when it was last modified.
Configuring Legato NetWorker Backup Software • Name: use rd=systemname:devicename, where systemname is the name of the system with the tape drive attached to it (either an IP4700 SP or a NetWorker system), and devicename is the name of the device on that system. To find out the name of the device on an IP4700 system, use the IP4700 web administration program and look in the Tape Drives area. • Media type: Type DLT7000 or AIT-2, as appropriate. • Target sessions: 1. • NDMP: yes.
Configuring Legato NetWorker Backup Software If you want to use different NDMP jukebox configuration file, use -f option, or set the environment variable LGTO_NDMP_LIBSCSI_CONFIG_FILENAME to the path of the NDMP jukebox config file. Enter ‘Administrator’ password on NDMP host ‘dakota11-2a’ (characters will not be echoed): _____ Communicating to devices on NDMP Server 'dakota11-2a', this may take awhile... Note: we cannot retrieve device file names for NDMP devices. scsidev@1024.1.0:ATL P1000 62200502.
Configuring Legato NetWorker Backup Software Enter NDMP user name: ? Administrator Enter NDMP password (characters will not be echoed): _____ Enter NDMP jukebox handle: ? /dev/c0b0t1d0 What is the NDMP type of ‘dakota11-2a’? 1) One of the Standard NDMP Servers. 2) NetApp or Celestra HP. Choice? 1 Communicating to devices on NDMP Server ‘dakota11-2a’, this may take awhile... These are the SCSI Jukeboxes currently attached to your system: 1) scsidev@1025.1.
Configuring Legato NetWorker Backup Software This media device has not been configured yet. Please select a media device type for rd=dakota11-2a/dev/c0b0t2d0.
Configuring Legato NetWorker Backup Software 10)8mm 11)8mm 5GB 12)8mm 20gb 13)8mm AIT 14)8mm AIT-2 15)8mm Mammoth-2 16)9490 17)9840 18)dlt 19)dlt1 20)dlt7000 21)dlt8000 31) 32) 33) 34) 35) 36) 37) 38) 39) 40) 41) 42) dst dtf himt LTO Ultrium qic SD3 vhs SLR VXA file logical optical Choice? 20 Enter hostname that owns media drive 3: ? [sunnw] dakota11-2a Enter pathname of media drive 2: ? /dev/c0b0t4d0 using ‘rd=kadota11-2a:/dev/c0b0t4d0’ as device name Should the drive be configured as a NDMP device? (
Configuring Legato NetWorker Backup Software Enter hostname that owns media drive 4: ? [sunnw] dakota11-2a Enter pathname of media drive 2: ? /dev/c0b0t5d0 using ‘rd=kadota11-2a:/dev/c0b0t5d0’ as device name Should the drive be configured as a NDMP device? (yes/no) yes This media device has not been configured yet. Please select a media device type for rd=dakota11-2a/dev/c0b0t5d0.
Configuring Legato NetWorker Backup Software auto clean: Yes default cleanings: 20 cleaning slots: 30 cleaning cartridge volumes Slot number Cleaning tape (20 uses left) 30 Make sure that the slots set aside for cleaning cartridges contain cleaning cartridges. NetWorker must know the number of times it can use each cleaning cartridge.
Configuring Legato NetWorker Backup Software Verify that the values for these attributes are appropriate for your installation. If not, check documentation on how to set up automated cleaning cartridge support. Jukebox has been added successfully. Would you like to configure another jukebox? (yes/no) no % Configuring Three-Way Backup For a three-way backup, enter the name of the IP4700 SP with the tape drive that backups will be sent to in the Storage Node field in the client resource.
Configuring Legato NetWorker Backup Software • Remote user and Password: the username and password of the IP4700. Specify Administrator and the password. These fields are case-sensitive. • Backup command: nsrndmp_save -T dump. Do not use tar. • Application information: Type any needed NDMP environment variables. (For more information, see your IP4700 documentation.) The following table lists the NDMP environment variables to use with NetWorker.
Configuring Legato NetWorker Backup Software NDMP Environment Variable Valid Parameters Default Value Use NO_ACLS T/F or Y/N F Do not use this environment variable. If you do, backups will not save access control list information for either CIFS or NFS file systems. We do not recommend using this variable. SNAPSHOT T/F or Y/N F (unless FAST_INCREMENTAL =T) If you use this, ensure that the volume has snapshot enabled in the IP4700 web interface. (In Volume...
Configuring Legato NetWorker Backup Software • Devices: Select all the NDMP devices that will receive IP4700 backups. Next, create a schedule. Make sure that incremental backups are not selected; these will result in full backups. Use level 1 through level 9 backups instead. For more information on levels, refer to your NetWorker Administrator’s Guide.
Configuring Legato NetWorker Backup Software e. Change the Save set field if you want, and type A0 or B0, or another appropriate value. f. In the Group field, select Test. g. Click the Preferences tab. h. In the Server Network Interface field, add the private LAN IP name or the private LAN IP address for the adapter (if you are using private LANs). For the private LAN IP name, use the short host name, not the fully qualified host name. 9. Start the Test group. 10.
Configuring Legato NetWorker Backup Software You can find further details in NetWorker’s log files, which are in the D:\nsr\logs directory where NetWorker was installed. See the following log files: Filename Description daemon.log contains the NetWorker actions with time stamps, such as when a backup started and when it ended. You can copy daemon.log to another file and open it with WordPad. messages describes each client in each backup when the backup completes. savegrp.
Best Practices Best Practices This section lists some recommended practices for backup; they apply to various systems, including Windows and UNIX systems as well as the IP4700 system. The following are general practices that we recommend: Automatic Synchronization • When connecting a tape library, do not reserve a SCSI channel for the autochanger device. Since the autochanger receives much less data than the tape drives, put the autochanger on the first SCSI bus, along with that SCSI bus’ tape drives.
Best Practices best backup and restore performance, and does not degrade the network performance of the clients while backup or restore is occurring. We also recommend that each client have a dedicated network adapter, either 100 Mbytes per second or 1000 Mbytes per second, that is connected to the private network. Some adapters and/or operating systems do not support link aggregation.
Monitoring your Backup Performance jukebox has changed. Otherwise, the backup software must put each tape into a drive in order to identify a tape. Tape Handling Do not affix labels to any part of the tape cartridge other than the bar code. Such labels can fall off inside the drive and damage it. “Swallowed leaders” can result when a loop on the end of the leader in the DLT tape cartridge has been damaged or worn.
Monitoring your Backup Performance AIT-2 Tape Drive Performance The AIT-2 tape drive performance is similar to the DLT7000 tape drive performance, except that the native throughput for the AIT-2 tape drive is 6 Mbytes per second, increasing to 12 Mbytes per second with very compressible data. Disk Performance The tape drive is often blamed for poor backup performance, when the root of the problem may actually be the disk. Older disks have slower transfer rates and slower seek times.
Monitoring your Backup Performance session may be left at the end. If the client is slow, its low backup throughput can swamp the overall backup throughput and make the backup take longer than the backup’s total size would indicate. One way to determine whether or not this is the case is to watch the backup software monitor window before you expect the backup to finish, and note whether only one tape drive runs for a significant length of time until the backup completes. Copyright © EMC Corporation 2001.
