source and destination are of the form [filer:]path
options:
[-sa username:password]
[-da username:password]
[-st { text | md5 }]
[-dt { text | md5 }]
[-l { 0 | 1 | 2 }]
[-d]
[-f]
[-h]
Ndmpcopy is supported on vfilers, as well as the physical filer named vfiler0. Use vfiler context or vfiler run to issue Ndmpcopy commands on a specific vfiler. See na_vfiler(1) for details on how to issue commands on vfilers. The use of Ndmpcopy on vfilers requires a MultiStore license.
The password used must be the NDMP password as described in the ndmpd man page.
The source and destination for the copy are specified in the following format:
[filer:]path
where filer is the hostname or IP address of the filer and path is the absolute pathname of the directory to be used in the transfer. If you do not specify the filer hostname or IP address, ndmpcopy assumes the source and destination filers to be the same as the filer running the ndmpcopy command. ndmpcopy creates the destination directory if it does not already exist. When ndmpcopy receives a destination pathname, the following rules are applied to determine what volume that path is referencing and the data is migrated accordingly:
Case 1: No /vol in the pathname. Default to the root volume.
Case 2: /vol/volume in the pathname and volume is a real volume on the filer. Target at your volume.
Case 3: /vol/volume in the pathname and volume is not a real volume on the filer. Default to the root volume.
The filer will print the full destination path when ndmpcopy operation successfully completes.
When running ndmpcopy against a vfiler, all the source and destination paths must live in volumes exclusively owned by the vfiler.
Before starting the ndmpcopy operation, the NDMP request daemon ndmpd has to be enabled on both the source and destination filers. Issue `ndmpd on' on both filers to enable the request daemon.
Example 1:
This command migrates data from a source path (source_path) to a different destination path (destination_path) on the same filer (myhost).
myhost> ndmpcopy -sa username:password -da username:password myhost:/vol/vol0/source_path myhost:/vol/vol0/destination_path
myhost> ndmpcopy /vol/vol0/source_path /vol/vol0/destination_path
Example 2:
This command migrates data from a source path (source_path) to a different destination path (destination_path) on remotehost1.
myhost> ndmpcopy -da username:password /vol/vol0/source_path remotehost1:/vol/vol0/destination_path
Example 3:
This command migrates data from a source path (source_path) on remotehost2 to a destination path (destination_path) on myhost.
myhost> ndmpcopy -sa username:password -st text remotehost2:/vol/vol0/source_path /vol/vol0/destination_path
Example 4:
This command migrates data from a source path (source_path) on remotehost1 to a destination path (destination_path) on remotehost2.
myhost> ndmpcopy -sa username:password -da username:password -l 1 remotehost1:/vol/vol0/source_path remotehost2:/vol/vol0/destination_path
Example 5:
This command describes the behaviour of ndmpcopy without the -f option. In this case, the /etc directory and its contents on the root volume of remotehost1 are protected from being overwritten with the /etc directory from myhost. This is intended to avoid the unintentional changing of the system characteristics after the root volume migration is completed.
myhost> ndmpcopy -da username:password /vol/rootvol remotehost1:/vol/rootvol
myhost> ndmpcopy -da username:password -f /vol/rootvol remotehost1:/vol/rootvol
Whether ndmpd is installed and turned on, on the source and destination filers involved in the copy.
myhost> ndmpd on
Whether the 2 filers can ping each other with first their
hostnames and if not then their IP addresses. If both do
not work, then it usually denotes an incorrect network
setup.
myhost> ping remotehost myhost> ping ip address of remotehost
Make sure that the Data ONTAP release on the filers you
are using for the copy support NDMP version 3 and/or
higher.
myhost> ndmpd version
Copyright © 1994-2008 NetApp, Inc. Legal Information