Table of ContentsLibraryView in Frames

Example: Using NDMP or dump command to archive SnapManager backups

You can run a script to archive your SnapManager backups to tape either by using the Run Command After Operation feature or by hardcoding the Snapshot copy names into the script.

Assume you want to run a script in the following environment:

To run a script using the SnapManager Run Command After Operation feature, use the following command:

C:\SnapManager Scripts\scriptname.txt $ExchSnapshot $InfoSnapshot

The command-line parameters %1 and %2 might provide values similar to the following, respectively:

exchsnap__SRVR3_01-20-2006_12.05.58__Daily

eloginfo__SRVR3_01-20-2006_12.05.58__Daily

If you do not use the Run Command After Operation feature and you do not use the unique naming convention for your backups, you can hard code the Snapshot copy names into the script.

For example, the dump command for the database might look like this, for an Exchange server named SRVR3:

rsh storagesystem1 dump 0f nrst0a

/vol/Exch/.snapshot/exchsnap__SRVR3__recent__Daily/exch1db.lun

The following script uses the storage system dump command to dump the database, transaction logs, and SnapInfo LUNs to the tape. This script relies on rsh functioning on the Exchange server using the SnapManager user account.

REM Back up the LUN containing the Exchange database.
REM For this example, a level 0 backup is performed
REM to the tape device named nrst0a.
rsh storagesystem1 dump 0f nrst0a
/vol/ExchVol/.snapshot/%1/exch1db.lun
REM Before appending the next backup to the tape,
REM reposition to the end of the tape so the next
REM write will not overwrite the existing data.
rsh storagesystem1 mt -f nrst0a eom
REM Back up the LUN containing the Exchange
REM transaction log files and the SnapManager SnapInfo
REM directory.
rsh storagesystem1 dump 0f nrst0a
/vol/ExchVol/.snapshot/%2/exch1logs.lun
Related concepts
Automatic backup archiving using the Run Command After Operation feature