|
Size: 2634
Comment:
|
Size: 3307
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| === EMC VNX5300 NDMP setting === | == EMC VNX5300 NDMP setting == Note: NS series require an MIA for device connection to the AUX-0 port. two SCSI connections connect the NDMP-Host Data Movers to the TLU. One SCSI connection is daisy chained to two tape drives, and the other is daisy chained to two tape drives and a robot. All Data Movers in Figure 7 on page 35 have two direct SCSI connections to VNX. * In VNX for block environment, before you run the server_devconfig -create command, verify that all paths to the Data Mover are active and no LUNs are trespassed. |
| Line 52: | Line 62: |
| * server_param server_2 –facility NDMP –info concurrentDataStreams | |
| Line 53: | Line 64: |
=== To restart server_2 === * type $ server_cpu server_2 -reboot -monitor now |
NDMP
EMC VNX requirement
- EMC supports NDMP drive sharing only through a storage area network (SAN).
- VNX uses port 10000 for NDMP operations. NDMP three-way backups and restores
use dynamic port allocation from the Data Mover.
- VNX supports a maximum of eight concurrent NDMP sessions per NDMP-Host Data Mover. The backup client (DMA) should be compatible and configured to support up to eight concurrent NDMP sessions.
- The Data Mover must have a minimum of 8 GB memory to run greater than four and up to eight NDMP sessions.
- Auto extend should be set to “No"
- Auto extend should be set to “No"
- Tape cloning is supported; use your backup software to clone a tape, which moves it from disk to tape.
EMC VNX5300 NDMP setting
Note: NS series require an MIA for device connection to the AUX-0 port.
two SCSI connections connect the NDMP-Host Data Movers to the TLU. One SCSI connection is daisy chained to two tape drives, and the other is daisy chained to two tape drives and a robot. All Data Movers in Figure 7 on page 35 have two direct SCSI connections to VNX.
- In VNX for block environment, before you run the server_devconfig -create command,
verify that all paths to the Data Mover are active and no LUNs are trespassed.
SSH login with EMC as nasadmin/nasadmin
- server_devconfig server_2 -c -s -a
Discovering storage on vnxsim1dm (may take several minutes) server_2 : done
- [nasadmin@vnxsim1dm ~]$ server_devconfig server_2 -l -s -n
- /nas/sbin/server_user server_2 -list
server_2: BB000C29B6901B0000_BB000C29B6901B0000:CFLjouSgIn5J6:65534:65534:ZDFpSJre8sulaBJZcolny2cfKW::ndmp_md5 BB000C299F807E0000_BB000C299F807E0000:Y2Tyf7gt8KF2Q:65534:65534:4l6VSJrre7tsulWacgol4E34hv::ndmp_md5
- [nasadmin@vnxsim1dm ~]$ /nas/sbin/server_user server_2 -add -md5 -passwd ndmp
Creating new user ndmp User ID: 105 Group ID: 105 Home directory: Changing password for user ndmp New passwd: Sorry, password must be 6 characters or more New passwd: Retype new passwd:
Click "Settings"->"Data Mover Parameters"->"NDMP"
NOTE: this action will need reboot Data Mover!
- Checking "concurrentDataStreams", consider change default value from 4 to 8.
- server_param server_2 –facility NDMP –info concurrentDataStreams
To restart server_2
- type
$ server_cpu server_2 -reboot -monitor now
NDMP restrictions
- NDMP backups and restores of iSCSI LUNs are not supported.
- NDMP does not support the Archive Bit method; only the Date/Time stamp method is supported.
HowTo setup Celerra NDMP Backup using Symantec BackupExec
https://768kb.wordpress.com/2011/08/08/howto-setup-celerra-ndmp-backup-using-symantec-backupexec/
Just to be sure - the user name must be ndmp, not NDMP. Hopefully this is what you have done?
To add credentials from cmd on media server, you can use this command:
tpconfig -add -nh <celerra_host> -user_id ndmp -password <password>
To test/verify comms, use this command:
tpautoconf -verify <celerra_host>
Celerra config hints and tips can be found in this doc:
NDMP Appliance Information: http://www.symantec.com/docs/TECH31885
