Beruflich Dokumente
Kultur Dokumente
2/17/10
2 NetBackupTM for NDMP: NAS Appliance Information Symantec Corporation
NAS appliance versions 2/17/10
For NAS filers that use NDMP V4, you can specify a different subfolder or file
name. /vol/vol1/mydir/myfile can be restored, for example, to
/vol/vol2/mydir2/myfile_restored.
For any restrictions unique to a particular NAS filer, see the appropriate section
in this document for your filer.
agámi systems
This information is provided to help you use NetBackup for NDMP with an
agámi Information Server (AIS) system. It is intended as a supplement to the
NetBackup for NDMP Administrator’s Guide.
For further details on the AIS system, please contact agámi Systems.
Known restrictions
The AIS supports three-way and remote NDMP backup, but does not support
local NDMP backup. NDMP backup types are described in the NetBackup for
NDMP Administrator's Guide.
AIS logs
To obtain diagnostic logs, use the AIS management console to access the
Support Diagnostic page. Select Create New File to create a new AIS diagnostic
log.
Other
■ The following are example entries for the NetBackup policy’s Backup
Selections list (file list):
set HIST=y
set TYPE=atar
set UPDATE=y
/export/vol2
■ The AIS supports path-based history with NetBackup 4.5 or later.
Path-based history is enabled by means of the set HIST=y entry shown
above.
BlueArc titan
This information is provided to help you use NetBackup for NDMP with a
BlueArc Titan system. It is intended as a supplement to the NetBackup for NDMP
Administrator’s Guide.
For further details, refer to the following BlueArc documentation or contact
BlueArc Corporation:
■ BlueArc Titan System Administration Guide
Known restrictions
The BlueArc supports only inode-based backup (Backup type = dump).
Other
■ Directory entry/inode-based history (file history) is supported with
NetBackup 4.5 or later.
To enable file-based history, enter the following as the first entry on the
NetBackup policy’s Backup Selections tab (file list):
SET HIST=y
DinoStor TapeServer
This information is provided to help you use NetBackup for NDMP and one or
more NAS servers (NDMP hosts) with a DinoStor TapeServer. It is intended as a
supplement to the NetBackup for NDMP Administrator’s Guide.
For further details on the DinoStor TapeServer, refer to the DinoStor TapeServer
User Guide, or contact the DinoStor division of Global Automation, Inc.
DinoStor TapeServer enables NetBackup to send backups of any supported NAS
server to a tape device configured on the TapeServer. This is a form of three-way
backup; three-way backup is described in the NetBackup for NDMP
Administrator’s Guide.
Known restrictions
None.
On NetBackup
Using the Media and Device Management utility in the NetBackup
Administration Console, define robots, drives, and storage units, then create (or
Symantec TechNote http://entsupport.symantec.com/docs/267773
10 NetBackupTM for NDMP: NAS Appliance Information Symantec Corporation
DinoStor TapeServer 2/17/10
modify) a backup policy. These procedures are described in the NetBackup for
NDMP Administrator’s Guide. Note the following when configuring NetBackup
for a DinoStor TapeServer.
■ When defining a robot in the Add a New Robot dialog, specify the device
name of the DinoStor TapeServer (not of the robot) in the Robot device path
field, and specify the DinoStor TapeServer host name in the NDMP host
name field. For example, referring to the output shown below for
tpautoconf -probe, the device name of the DinoStor TapeServer to
specify in the Robot device path field would be sgh2-0c0i1l1, and the
host name to specify in the NDMP host name field would be dinostor.
■ When defining a storage unit for DinoStor TapeServer in the New Storage
Unit dialog, specify the DinoStor TapeServer host name in the NDMP Host
field.
■ In the NetBackup policy, specify the storage unit that you created for the
DinoStor TapeServer.
Other
None.
EMC celerra
This information is provided to help you use NetBackup for NDMP with an EMC
Celerra Network Server. It is intended as a supplement to the NetBackup for
NDMP Administrator’s Guide.
For more information on your Celerra Network Server, refer to the Celerra
Network Server Version 5.5 Documentation CD, which can be downloaded from
EMC's Powerlink web site.
Known restrictions
The username used with the tpconfig command must be defined as ndmp for
each data mover.
server_2 :
SCSI non-disk devices :
chain= 0, scsi-0
symm_id= 0 symm_type= 0
tid/lun= 15/15 type= disk val= -99 info= 52658653C310 diskerr=
-1
chain= 1, scsi-1
symm_id= 0 symm_type= 0
tid/lun= 15/15 type= disk val= -99 info= 52686043C320 diskerr=
-1
chain= 2, scsi-2 : no devices on chain
chain= 3, scsi-3
symm_id= 0 symm_type= 0
tid/lun= 0/0 type= jbox info= HP C5173-7000 3.04
tid/lun= 1/0 type= tape info= QUANTUM DLT7000 2560q`
tid/lun= 2/0 type= tape info= QUANTUM DLT7000 2560q`
Robot
Use the tpconfig command to set attributes for an NDMP-attached robot.
For example:
tpconfig -add -robot 8 -robtype tld -robpath c3t0l0 -nh celerra_host
-bus 3 -target 0 -lun 0
Where:
■ celerra_host is the name of the Data Mover. This is also the NDMP host
name to be specified on the Add Robot display in the NetBackup
Administration Console. For assistance, refer to “Adding a Robot Directly
Attached to an NDMP Host” in the NetBackup for NDMP Administrator’s
Guide.
■ c3t0l0 is the device name for the robotic controller. This is also the Robotic
device to be specified on the Robot Control display. Refer to “Adding a Robot
Directly Attached to an NDMP Host” in the NetBackup for NDMP
Administrator’s Guide.
■ 3 is the chain number (the bus number).
■ 0 is the target ID or tid of the robot control.
■ 0 is the LUN number.
Media devices
EMC Celerra Network Servers have only one device file per tape drive. Use this
device file when configuring the tape device files for use with NetBackup for
NDMP.
Following is an example of a device name (on UNIX, this is called the No Rewind
Device), to be entered on the Add Drive display in the NetBackup Administration
Console:
celerra:c3t2l0
Where celerra is the external Data Mover name and c3t2l0 is the tape device
file name. This example file name is for the second DLT tape drive listed in the
example output for server_devconfig command on the previous page.
set EMC_EDIR03=/fs2/NAS*
set EMC_EDIR05=/fs2/j*
set EMC_EFILE01=*tar
set EMC_EFILE03=*dat
set EMC_EFILE02=*dat
set EMC_EDIR04=/fs2/Millions
set UPDATE=y
/fs2
In the above example, the backup of /fs2 will not include the files and
directories specified by the EMC_EDIR and EMC_EFILE statements.
Other
■ If you specify an incorrect path name in the NetBackup policy’s Backup
Selections list (file list), the entire backup fails with status code 99, “NDMP
backup failure.”
■ Path-based history is supported with NetBackup 4.5 or later.
To enable path-based history, enter the following as the first entry in the
NetBackup policy’s Backup Selections list:
set type=tar
Known restrictions
■ Backup and restore times on the CBRM running with NetBackup are
noticeably longer than expected. EMC is working to resolve this issue.
■ The CBRM is currently limited to single-threaded backups and restores. EMC
is working to resolve this issue.
■ The CBRM cannot run on the same NetBackup master server where
NetBackup for NDMP is running, because both NetBackup Remote NDMP
and CBRM utilize the same port for internal communication.
■ The CBRM does not allow redirected restores to an alternate path. If you
attempt to restore to an alternate path (or to an invalid path), the CBRM
restores the data to the original path.
■ The CBRM does not allow cross platform restores. For example, if the backup
was made by means of a CBRM installed on Windows, the backup cannot be
restored using a CBRM installed on Solaris.
■ The CBRM supports full backups (Level=0) and cumulative/incremental
backups (Level=1) only.
■ Changing the CBRM .res profile file while a backup is running may cause the
backup job to hang or fail.
■ The CBRM currently does not support local NDMP.
■ The CBRM BEGIN_DATE and END_DATE in the .res profile are automatically
deleted when the current backup job is completed.
Other
■ The following are required entries in the NetBackup policy’s Backup
Selections tab (file list). No other entries should be made in the NetBackup
Backup Selections tab.
Except for the file name for the profile, these must be entered exactly as
shown below:
set profile=file_name
set type=centera
set hist=y
set fstype=ufs
/centera
where set profile=file_name specifies the name of the CBRM .res
profile.
Note: Make sure to include the IP address of the EMC Centera host in the CBRM
.res profile:
Centera_IP=xxx.xx.xx.xxx
Known restrictions
■ The Hitachi Lightning currently supports NetBackup remote NDMP backups
only. Remote NDMP backups are a form of three-way backup described in
the NetBackup for NDMP Administrator’s Guide.
■ The Hitachi Lightning allows only one NDMP connection for non-backup
operations.
For example, if a restore operation is running, you cannot perform another
restore operation on another file system on the same node of the Hitachi
Lightning at the same time.
■ The Hitachi Lightning does not allow multiple backup operations to occur
from the same file system.
For example, if you have a policy running a backup of /dir1, you cannot run
another policy that backs up /dir1/subdir1 at the same time.
Other
■ The Hitachi Lightning supports path-based history with NetBackup 4.5 or
later.
■ On the NetBackup Administration Console, in the Backup Selections tab of
the backup policy, you must use the set directive to specify the files or
directories to back up.
Note: You must use the set directive in exactly the format shown below,
otherwise the backup will fail.
Explanation
set files=directory_to_back_up
Specifies the directory or file that you want to back up. For example:
set files=dir1
Note: This entry must NOT have a space or a slash after the equal sign (=).
The following entries are not allowed:
set type=tar
This is a required entry.
/mnt/file_system
Specifies the mounted file system on the Hitachi Lightning containing the
files to back up. For example, /mnt/hitachi05.
Note: This entry must start with a slash, and must NOT have a trailing slash if
the Hitachi Lightning NAS system version is earlier than 02-02 (version 02-02
supports a trailing slash).
The following entries are not allowed:
/mnt/hitachi01/ (do not use a trailing slash if the Hitachi Lightning version
is prior to 02-02)
Hitachi TagmaStore
This information is provided to help you use NetBackup for NDMP with the
Hitachi TagmaStore AMS/WMS NAS Modular system and the TagmaStore
USP/NSC NAS Blade system. It is intended as a supplement to the NetBackup for
NDMP Administrator's Guide.
The following information applies to both the AMS/WMS and USP/NSC systems
unless otherwise noted. For further details on your Hitachi TagmaStore system,
please contact Hitachi Data Systems.
Known restrictions
■ The Hitachi TagmaStore currently supports NetBackup remote NDMP
backups only. Remote NDMP backups are a form of three-way backup
described in the NetBackup for NDMP Administrator's Guide.
■ NetBackup policy directives in the Backup Selections list cannot omit the
TYPE variable because NetBackup assumes TYPE=dump by default.
■ Only one backup job is allowed per file system when “set SNAPSHOT=Y” is
specified in the NetBackup policy’s Backup Selections list.
■ The Hitachi TagmaStore AMS 1000/500 and USP/NSC allow up to five
simultaneous jobs per NAS unit (the number of backup and restore jobs
together must not exceed five). The Hitachi TagmaStore AMS 200/WMS 100
allow up to two simultaneous jobs per NAS unit (the number of backup and
restore jobs together must not exceed two).
For NAS hosts that support DAR, NetBackup enables DAR by default.
Other
■ The Hitachi TagmaStore supports path-based history with NetBackup 4.5 or
later.
To enable path-based history, enter the following at the top of the list on the
NetBackup policy’s Backup Selections tab (file list):
set HIST=f
■ On the NetBackup Administration Console, in the NetBackup policy’s
Backup Selections tab, you must use the set directive to specify the files or
directories to back up.
Note: Use the set directive in exactly the format shown below, otherwise the
backup will fail.
Explanation
set files=directory_to_back_up
Specifies the directory or file that you want to back up. For example,
set files=dir1
Note: This entry must NOT have a space or a slash after the equal sign (=).
The following entries are not allowed:
set type=tar
This is a required entry. Note that uppercase values such as TAR are not
supported.
/mnt/file_system
Specifies the mounted file system on the Hitachi TagmaStore system
containing the files to back up. For example, /mnt/hitachi05.
Note: This entry must start with a slash. The following entry is not allowed:
Known restrictions
The username used with the tpconfig command must be defined as root for
each data mover. See “Example configuration sequence” on page 32.
Robot
To display the robot device file, sign on to the IBM Nxxxx host and enter the
following command:
sysconfig -m
The names are of the format mcN, where N is 0 or higher.
For example:
Medium changer (6a.4) HP C6280-7000
mc0 - medium changer device
Media devices
To display tape device files, enter the following command:
sysconfig -t
Always use the drive names that begin with “nr” (such as nrst0a) because these
are the non-rewinding devices.
Example sysconfig output:
Tape drive (6a.5) Quantum DLT7000
rst0l - rewind device, format is: 81633 bpi 40 GB (w/comp)
nrst0l - no rewind device, format is: 81633 bpi 40 GB (w/comp)
urst0l - unload/reload device, format is: 81633 bpi 40 GB (w/comp)
rst0m - rewind device, format is: 85937 bpi 35 GB
nrst0m - no rewind device, format is: 85937 bpi 35 GB
urst0m - unload/reload device, format is: 85937 bpi 35 GB
rst0h - rewind device, format is: 85937 bpi 50 GB (w/comp)
nrst0h - no rewind device, format is: 85937 bpi 50 GB (w/comp)
urst0h - unload/reload device, format is: 85937 bpi 50 GB (w/comp)
rst0a - rewind device, format is: 85937 bpi 70 GB (w/comp)
nrst0a - no rewind device, format is: 85937 bpi 70 GB (w/comp)
urst0a - unload/reload device, format is: 85937 bpi 70 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0l" attributes=(0x0)
DENSITY=81633 bpi 40 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0l" attributes=(0x2) UNLOAD
DENSITY=81633 bpi 40 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0m" attributes=(0x1) REWIND
DENSITY=85937 bpi 35 GB
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0m" attributes=(0x0)
DENSITY=85937 bpi 35 GB
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0m" attributes=(0x2) UNLOAD
DENSITY=85937 bpi 35 GB
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0h" attributes=(0x1) REWIND
DENSITY=85937 bpi 50 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0h" attributes=(0x0)
DENSITY=85937 bpi 50 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0h" attributes=(0x2) UNLOAD
DENSITY=85937 bpi 50 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Other
If you eject a tape from an IBM Nxxxx-attached drive and then try to open the
device, it will reload the tape. This happens when the device is still UP and the
NetBackup automatic-volume-recognition daemon (avrd) polls it.
Isilon IQ
This information is provided to help you use NetBackup for NDMP with an Isilon
IQ system. It is intended as a supplement to the NetBackup for NDMP
Administrator's Guide.
For further details on an Isilon IQ system, please contact Isilon Systems.
Known restrictions
None.
Isilon IQ logs
The NDMP logs can be found at /var/log/isi_ndmp_d on each node.
Other
Path-based history is supported with NetBackup 4.5 or later.
To enable path-based history, enter the following at the top of the list on the
NetBackup policy’s Backup Selections tab (file list):
set HIST=f
Mirapoint
This information is provided to help you use NetBackup for NDMP with a
Mirapoint server. It is intended as a supplement to the NetBackup for NDMP
Administrator’s Guide.
For more information on your Mirapoint host, refer to the following
documentation or contact Mirapoint Inc.
■ Mirapoint System Software Setup and Administration Guide
Known restrictions
■ Mirapoint 3.6 supports local, three-way, and remote-NDMP backup.
■ Mirapoint only supports one attached robot and one attached tape drive.
The tape drive can be standalone or in the robot.
■ Mirapoint does not allow concurrent backups or restores.
■ Mirapoint only allows backup or restore of the /usr/store directory, not
of subdirectories under /usr/store. Please refer to Mirapoint
documentation regarding selective backup and restore.
■ For backup, the /usr/store directory must be specified with no trailing
slash; /usr/store/ is not allowed.
■ Mirapoint supports type=image only.
■ The default Mirapoint user ID for ndmp is administrator. This ID is user
selectable.
■ Mirapoint does not allow redirection of a restore to a different path (the
restore will fail).
■ Mirapoint must be rebooted after a successful full restore to remount the file
system.
Mirapoint logs
Contact Mirapoint support for the collection of logs on the Mirapoint host.
Tape
For either a tape drive in a robot or a standalone tape, the local NDMP drive path
is: /dev/nrsa0
Robot
Since Mirapoint supports only one robot device, the device name for the robot
controller will be /dev/ch0.
To discover the controller, target, and LUN for the robot device:
1 Telnet into the Mirapoint host with the appropriate port number (refer to
your Mirapoint documentation).
telnet mirapoint port_number
Example output
Trying 244.87.21.47...
Connected to mirapoint.mirapoint.com.
Escape character is '^]'.
OK mirapoint.mirapoint.com admind 3.0 server ready
User: administrator
Password:
OK User logged in
mirapoint.mirapoint.com>
2 To obtain the controller, target and LUN of the robot controller, enter the
following.
diag get changeraddress
Example output:
Controller 3, Target 3, Lun 0
OK Compelete
Enter quit to terminate the telnet session.
3 For NetBackup 6.0 or later, use the tpconfig command to set attributes for
an NDMP-attached robot.
For example:
tpconfig -add -robot 8 -robtype tld -robpath /dev/ch0
-nh mirapoint_host -bus 3 -target 3 -lun 0
Other
■ For incremental backups, the NetBackup policy file list (or Backup Selections
tab) must contain the following as the first entry in the list:
set UPDATE=y
■ After doing a restore, the Mirapoint host must be rebooted by pressing its
reset button. Because of the reboot of the Mirapoint host, the NetBackup
automatic-volume-recognition daemon (avrd) sets the drive to the DOWN
state. You must set the drive to the UP state in order to run backups and
restores.
■ Path-based history (file history) is supported with NetBackup 4.5 or later.
To enable path-based history (needed for selective restore), enter the
following at the top of the list on the NetBackup policy’s Backup Selections
tab (file list):
set HIST=y
To turn off path-based history:
set HIST=n
For further details, refer to Mirapoint documentation.
Known restrictions
■ The NEC iStorage NV Series supports the NDMP protocol version V2 only.
■ The NEC iStorage NV Series can only back up file systems, not
sub-directories.
■ Only one backup or restore can be running per file system. For example, if a
backup job is currently backing up /export/sxfs/vol1, another attempt
to back up or restore /export/sxfs/vol1 at the same time will fail.
■ A second backup of the same file system could fail if started too soon after
the first backup of that file system. This is because a backup job needs time
to delete the snapshot after completion of the backup. Until the snapshot is
deleted, the second backup of the same file system cannot start. The same is
true for restores: a restore of a file system could fail if started too soon after
a previous restore of that file system.
■ Enable NDMP service in the NEC iStorage: enter your NEC license key for the
NDMP option and then start NDMP in the Service section.
Drives
To find the tape device names, telnet into the NEC iStorage and enter:
dmesg | grep “scsi tape”
Example output:
Attached scsi tape st0 at scsi0, channel 0, id 1, lun 0
Attached scsi tape st1 at scsi0, channel 0, id 2, lun 0
The tape device names, to be entered on the Add Drive display in the NetBackup
Administration Console, are /dev/nst0 for tape drive 1 and /dev/nst1 for
tape drive 2. Always use the drive names that begin with “n” because these are
the non-rewinding devices.
Other
The following directive must be placed at the start of the NetBackup policy’s
Backup Selections tab (file list):
set XFS=yes
This directive must be specified for all NetBackup backups of the NEC iStorage
NV Series, otherwise the backup will fail. Note that the set XFS=yes directive
must be specified for both XFS and XFSFW file systems.
NetApp
This information is provided to help you use NetBackup for NDMP with a
NetApp NAS (Network Attached Storage) filer. It is intended as a supplement to
the NetBackup for NDMP Administrator’s Guide.
For further details, refer to the following documentation or contact NetApp.
■ Data ONTAP Command Reference Guide
■ Data ONTAP System Administrator's Guide
Known restrictions
■ The username used with the tpconfig command must be defined as root
for each data mover. See “Example configuration sequence” on page 47.
■ When restoring files, if the NetApp filer does not use Direct access recovery
(DAR), the destination path that you specify for the restore must end with
the original folder and file name. If the original backup path was
/vol/vol1/mydir/myfile, the destination path for the restore must end with
/mydir/myfile. Otherwise, NetBackup appends /mydir/myfile to the end of
the destination path.
For more details on DAR, and to determine whether DAR has been disabled
in NetBackup, refer to the NetBackup for NDMP Administrator's Guide.
NetApp logs
The logs on the NetApp filer must be viewed through an NFS or CIFS mount
point. On the NetApp filer, general messages appear in /etc/messages.
■ In ONTAP 8.0, both ONTAP 7 mode and ONTAP 10 mode are combined into a
single release. You cannot run both modes on the same filer concurrently.
■ The NDMP service is controlled by means of the Data ONTAP administrative
interface or the following commands:
ndmpd on
(Starts the NDMP service)
ndmpd off
(Stops the NDMP service)
ndmpd status
(Displays the status of the NDMP service including any active NDMP
sessions)
ndmpd probe session-number
(Displays details about the specified session)
■ By default the NDMP service is not started at boot time. To start it, add the
following line to the end of the /etc/rc file on the NetApp system:
ndmpd on
■ To determine the number of objects in a volume, enter the following:
maxfiles
Robot
To display the robot device file, sign on to the NetApp host and enter the
following command:
sysconfig -m
The names are of the format mcN, where N is 0 or higher.
For example:
Medium changer (6a.4) HP C6280-7000
mc0 - medium changer device
Media devices
To display tape device files, enter the following command:
sysconfig -t
Always use the drive names that begin with “nr” (such as nrst0a) because these
are the non-rewinding devices.
Example sysconfig output:
Tape drive (6a.5) Quantum DLT7000
rst0l - rewind device, format is: 81633 bpi 40 GB (w/comp)
nrst0l - no rewind device, format is: 81633 bpi 40 GB (w/comp)
DENSITY=85937 bpi 35 GB
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0m" attributes=(0x2) UNLOAD
DENSITY=85937 bpi 35 GB
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0h" attributes=(0x1) REWIND
DENSITY=85937 bpi 50 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0h" attributes=(0x0)
DENSITY=85937 bpi 50 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0h" attributes=(0x2) UNLOAD
DENSITY=85937 bpi 50 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0a" attributes=(0x1) REWIND
DENSITY=85937 bpi 70 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0a" attributes=(0x0)
DENSITY=85937 bpi 70 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0a" attributes=(0x2) UNLOAD
DENSITY=85937 bpi 70 GB (w/comp)
ELECTRICAL_NAME=6a.5
SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Following is an example of a device name (on UNIX, it is called the No Rewind
Device), to be entered on the Add Drive display in the NetBackup Administration
Console:
netapp:nrst0a
where netapp is the name of the NetApp filer, and nrst0a is the
non-rewinding device.
Other
Tape ejection
If you eject a tape from a NetApp-attached drive and then try to open the device,
it will reload the tape. This happens when the device is still UP and the
NetBackup automatic-volume-recognition daemon (avrd) polls it.
Note: Only the entire volume can be restored; files within the volume cannot be
restored individually.
Image Backup is supported with the following NetBackup versions and later
maintenance packs (MP) of the same release:
■ NetBackup 4.5 MP8/FP8
■ NetBackup 5.0 MP4
■ NetBackup 5.1 MP2
■ NetBackup 6.x
■ NetBackup 7.x
NetApp filers running Data ONTAP 7.0.1 or higher support SnapMirror to Tape,
which provided the same functionality as Image Backup but required approval
through a NetApp Product Variance Request (PVR) form. For that reason, this
functionality has not been included in previous NetBackup documentation.
Use this variable if you want the snapshot to be deleted after the backup
completes. A snapshot is taken of the volume before the backup is written to
tape. Deleting the snapshot saves storage space.
■ /volume_to_back_up
Specifies the volume you want backed up. For example: /vol/vol1
Known Restrictions
■ Use of the tpautoconf -probe command for device discovery is not
supported in local NDMP configurations with the NetApp Data ONTAP GX.
■ Directory DAR is not supported with the NetApp Data ONTAP GX.
■ When restoring files, if the NetApp filer does not use Direct access recovery
(DAR), the destination path that you specify for the restore must end with
the original folder and file name. If the original backup path was
/vol/vol1/mydir/myfile, the destination path for the restore must end with
/mydir/myfile. Otherwise, NetBackup appends /mydir/myfile to the end of
the destination path.
For more details on DAR, and to determine whether DAR has been disabled
in NetBackup, refer to the NetBackup for NDMP Administrator's Guide.
NetApp Logs
The logs on the NetApp Data ONTAP GX filer must be viewed through a SSH
session. NDMP logs are located in /mroot/log/ndmpd.log.
■ In ONTAP 8.0, both ONTAP 7 mode and ONTAP 10 mode are combined into a
single release. You cannot run both modes on the same filer concurrently.
■ All volumes on the NetApp Data ONTAP GX filer are created within Virtual
Servers.
■ The path specified in the NetBackup policy’s Backup Selections list must
contain the Virtual Server. For example:
/vs1/vol1
Robot
To display the robot device file, sign on to the NetApp host and go to SYSTEM >
hardware > tape > library.
The names are of the format:
/robot/switchname~switch_port_number.target
For example:
/robot/brocade18~23.126
Media Devices
The names are of the format:
/tape/nr.switchname~switch_port_number.targetLlun.a
where Llun indicates the LUN.
For example:
/tape/nr.brocade18~23.126L2.a
Other
To back up a volume as a single file, see “Image Backup (smtape)” on page 48.
Known restrictions
None.
Other
■ The ONStor NAS Gateway supports path-based history with NetBackup 4.5
or later.
■ The ONStor NAS Gateway also supports the following environmental
parameters in the NetBackup policy’s Backup Selections tab (file list).
For more detail on these parameters, refer to your ONStor documentation.
■ RECURSIVE=(y, n) (default is y)
■ TYPE= (default is tar)
■ LEVEL= (default is 0)
■ UPDATE=(y, n) (default is y)
■ ONSTOR_OVERWRITE=(y, n) (default is y)
■ ONSTOR_EXTRACT_8.3=(y, n) (default is y)
Known restrictions
The GEOn system is designed for NDMP three-way backups only.
GEOn logs
To generate trace logs for the GEOn pertaining to a particular issue, do the
following.
1 Log into the GEOn by means of the Overland console, or from a remote host
through telnet.
2 At the Ready prompt, enter:
set tracelog enabled
3 Enter:
saveconfiguration
4 Reproduce the issue that you want to log.
5 To create a trace log and display it to the screen, enter:
dumptracelog
You can highlight portions of the output and copy them to a file. Or you can
enter the script file_name command prior to running dumptracelog,
and the dumptracelog output is written to the file specified on the
script command.
6 Continued logging can impact performance. To disable logging, enter:
set tracelog disabled
7 To save this configuration (with logging disabled), enter:
saveconfiguration
host id "20000058493004?0"
Login was successful
Host supports 3-way backup/restore
2 Using the Media and Device Management utility in the NetBackup
Administration Console, define robots, drives, and storage units, then create
a backup policy. These procedures are described in the NetBackup for NDMP
Administrator’s Guide.
Other
None.
Known restrictions
None.
Pillar logs
Do the following to access the logs.
1 Log on to the Axiom Storage Manager GUI.
2 Click the Support button and then select Collect System Information under
the Tools menu on the left.
3 From the Actions pull-down menu in the bottom-middle of the window,
select Collect System Information.
4 Select the desired items from the Collection Scope list.
Collecting system information can take several minutes depending on the
items selected.
5 After collection of system information completes, select Download
Information to Client from the Actions pull-down menu and select the
location to save the System Information (it will be a tar file).
Other
None.
Quantum
This information is provided to help you use NetBackup for NDMP with a
Quantum Network-Attached Storage (NAS) backup solution controlled by a
Prism Management Card (PMC). It is intended as a supplement to the NetBackup
for NDMP Administrator’s Guide.
For further details, contact Quantum Corporation.
Known restrictions
The Quantum PMC-controlled robotic library only supports three-way backups.
ATL logs
To display any logs for Quantum PMC-controlled robotic library, contact
Quantum Corporation for assistance.
Robot
The robot name is spt0. The robot has its own IP address.
Use the tpconfig command to set attributes for the robot.
For example:
tpconfig -add -robot 8 -robtype tld -robpath spt0 -nh 101.111.222.33
-bus 0 -target 0 -lun 0
Where:
■ 101.111.222.33 is the IP address for the PMC.
■ spt0 is the device name for the robotic control.
■ 0 is the SCSI controller number.
■ 0 is the target ID.
■ 0 is the LUN number.
Media device
Although each tape drive has the same device name (/dev/nst0), each drive
has a unique IP address. As a result, you must authorize access to each drive.
The following example is for two tape drives in the same robot.
tpconfig -add -nh 101.111.222.34 -user_id root
tpconfig -add -nh 101.111.222.35 -user_id root
(enter password at prompt)
Following is an example of a device name (on UNIX, this is called the No Rewind
Device), to be entered on the Add Drive display in the NetBackup Administration
Console:
101.111.222.34:/dev/nst0
Where 101.111.222.34 is the IP address for the tape drive and /dev/nst0
is the tape device name.
os version “2.2.5-22”
host id “0”
host supports TEXT Authorization
Logging in using TEXT method...
Login was successful
Opening SCSI device “spt0”
Setting SSI target controller 0 id 0 lun 0...
Inquiry result is ATL P3000 63100501.42
2 Enter the following to authorize NetBackup 6.0 or later to access a tape drive
in the Quantum PMC-controlled robotic library. (See “Authorizing
NetBackup access to the NDMP host” for assistance with earlier NetBackup
releases.) This command must be repeated for each tape drive in the robot.
tpconfig -add -nh 101.111.222.34 -user_id root -password
password
tpautoconf -verify 101.111.222.34
Example output from the -verify option:
Verify Host name: 101.111.222.34
Connecting to host “101.111.222.34” as user “root”..
Waiting for connect notification message...
Opening session with NDMP protocol version 2...
Host info is:
host name “101.111.222.34”
os type “Linux”
os version “2.2.5-22”
host id “0”
host supports TEXT Authorization
Logging in using TEXT method...
Login was successful
3 Using the Media and Device Management utility in the NetBackup
Administration Console, define robots, drives, and storage units, then create
a backup policy. These procedures are described in the NetBackup for NDMP
Administrator’s Guide.
Other
None.
Spectra logic
This information is provided to help you use NetBackup for NDMP with a
Spectra Logic NDMP enabled by TAOS robotic library. It is intended as a
supplement to the NetBackup for NDMP Administrator’s Guide.
For further details, refer to the following Spectra Logic documentation or
contact Spectra Logic Corporation.
■ Spectra 2000 TAOS enabled Manual
Known restrictions
The Spectra Logic NDMP enabled by TAOS robotic library only supports
three-way backups.
devicetargetnumber_LUN
Robot
For example:
Library0_0
where Library is the device, the target number is 0, and the LUN is 0.
Media device
For example:
Tape1_0
where Tape is the device, the target number is 1, and the LUN is 0.
Following is an example of a device name (on UNIX, it is called the No Rewind
Device), to be entered on the Add Drive display in the NetBackup Administration
Console:
treefrog:Tape1_0
where treefrog is the name of the Spectra Logic NDMP enabled by TAOS robotic
library.
Other
None.
Stratus V Series
This information is provided to help you use NetBackup for NDMP with a
Stratus V Series system. It is intended as a supplement to the NetBackup for
NDMP Administrator’s Guide.
The Stratus V Series is supported by NetBackup 6.0 and later.
For further details on the Stratus V Series system, please contact Stratus
Technologies.
Known restrictions
■ The Stratus V Series system supports NetBackup remote NDMP backups
only. Remote NDMP backups are a form of three-way backup described in
the NetBackup for NDMP Administrator's Guide.
■ The Stratus V Series does not support directory names greater than 32
characters. The limitation for files names is 255 characters.
■ The Stratus V Series does not support CIFS or NFS for file system access. To
access the Stratus file system, you must use SAMBA.
To learn more about file system access to the Stratus V Series, please refer
to your Stratus documentation.
■ The Stratus V Series uses its own operating system called VOS. To access the
VOS operating system directly, you must use a terminal emulator such as
TTWIN 3.
■ The Stratus V Series supports the NDMP version 3 protocol only.
Other
The following directives must be placed at the start of the NetBackup policy's
Backup Selections tab (file list):
SET TYPE=save
SET SAVE_OPTIONS='-backup'
To learn more about the additional directives available for the Stratus V Series,
see the Stratus V Series documentation.
Known restrictions
■ Sun StorEdge NAS systems running OS version 4.02.45 or earlier support
remote NDMP backup and restore only. Sun StorEdge 52xx and 53xx NAS
systems running OS version 4.20 or later support local and three-way
backup and restore (including remote NDMP).
■ Set TYPE=tar is not supported for the Sun StorEdge 5xxx NAS OS version
4.02.45 or earlier. Since the path name does not start with the path
separator (/), the restores will fail. This restriction does not apply to NAS OS
version 4.20 or later.
■ Files containing hard links may not be restored with the correct number of
hard links.
Other
The Sun StorEdge 5xxx NAS supports path-based history with NetBackup 4.5 or
later.
To enable path-based history, enter the following at the top of the list on the
NetBackup policy’s Backup Selections tab (file list):
set HIST=y
Known restrictions
Remote NDMP only supports three-way backups.
Remote logs
For troubleshooting, look at the following log on the server where you installed
remote NDMP: /usr/openv/netbackup/logs/ndmpmoveragent
ps -e | grep ndmpmove
Example output:
1346 ? 0:00 ndmpmove
For details on these commands, refer to the commands appendix of the
NetBackup 4.5 for NDMP System Administrator’s Guide.
Media device
Unlike the robot, the tape device must be configured as an NDMP device.
Following is an example of a device name (on UNIX, this is called the No Rewind
Device), to be entered on the Add Drive display in the NetBackup Administration
Console:
Solaris example:
patch:/dev/rmt/0cbn
where patch is the name of the Solaris NetBackup media server, 0 specifies unit
0, c means compressed, and bn is the Berkeley no-rewind device. You must use
the Berkeley no-rewind device.
Windows NT/2000 example:
patch:Tape0
where patch is the name of the Windows NT/2000 NetBackup media server and
Tape0 is the device name.
host id "80cc45cd"
Login was successful
Host supports 3-way backup/restore
2 Using the Media and Device Management utility in the NetBackup
Administration Console, define robots, drives, and storage units, then create
a backup policy. These procedures are described for remote NDMP in the
NetBackup 5.x for NDMP System Administrator’s Guide.
Other
None.