Purpose	A restore data operation restores files from an external filer to a managed volume; the cancel restore data command stops a restore operation.
Modes	priv-exec
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or backup-operator
Syntax	cancel restore data namespace volume volume path path   namespace (1-30 characters) is the namespace to which files are being restored. Use the show restore data command for a list of namespaces where restores are running. volume (1-1024 characters) specifies the namespace volume where the restore is occurring. path (1-1024 characters) specifies the volume directory. This path is relative to the volume root, above. Use forward slashes (/) for NFS or CIFS paths.
Default(s)	None
Guidelines	The CLI prompts for confirmation before canceling the restore operation; enter yes to continue. Use the restore data command to start restoring files and directories to a volume. Restore operations happen in the background while you continue to use the CLI; you can use the wait-for restore data command to block the CLI until the restore is complete. To show all restore operations, use show restore data.
Sample	bstnA# cancel restore data wwmed volume /acct path / Cancel specified restore operations? [yes/no] yes bstnA# cancels the restore operation in progress for the root directory in the wwmed~/acct volume.
Related Commands	restore data wait-for restore data show restore data

Purpose	The ARX holds its restore-operation records indefinitely, so that you can see the results of every restore operation through show restore data. Use the clear restore data command to remove restore operations from this running history.
Mode	priv-exec
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or backup-operator
Syntax	clear restore data clear restore data namespace clear restore data namespace volume vol-path clear restore data namespace volume vol-path path path   The namespace, vol-path, and path arguments mimic the ones used in the restore data command. These identify one or more restore operations; if you omit all of them, the command clears all restore-operation records from the switch. namespace (1-30 characters) specifies a namespace where one or more restores have occurred. vol-path (optional, 1-1024 characters) specifies a volume. Use forward slashes (/) for all volumes, including CIFS. path (optional, 1-1024 characters) identifies a particular path that has been restored. As with volumes, use forward slashes in all paths.
Default(s)	None
Guidelines	The CLI prompts for confirmation before deleting any restore records. Enter yes to continue. Use show restore data to show all recorded restore operations. This command clears them; after you run it, the show restore data command no longer displays the cleared operation(s). The restore data command starts a restore operation (which runs in the background while you continue to use the CLI), cancel restore data cancels a running restore, and wait-for restore data blocks the CLI until a running restore completes.
Samples	bstnA# clear restore data wwmed Clear restore data records? [yes/no] yes bstnA# clears all restore-operation records for the wwmed namespace.   bstnA# clear restore data Clear restore data records? [yes/no] yes bstnA# clears all restore records from the switch. The show restore data command displays nothing after you do this.
Related Commands	restore data show restore data cancel restore data wait-for restore data

Purpose	To restore files and/or directories to a namespace volume, use the restore data command.
Modes	priv-exec
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or backup-operator
Syntax	restore data namespace volume volume path dest-path filer ext-filer {nfs nfs-export | cifs cifs-share}+ source-path src-path [recurse] [remove-source]   namespace, volume volume, and path dest-path specify the destination for the restored files: namespace (1-30 characters) specifies the destination namespace for the restore operation. Use the show namespace command for a list of configured namespaces. volume (1-1024 characters) is the volume to be restored. All of the namespaces volumes appear in the show namespace output. dest-path (1-1024 characters) is the file or directory to be restored (for example, var/log). This path is relative to the volume root, above. If this is a directory, the restored files are placed into a new subdirectory under this path named restore. Use forward slashes (/) for NFS or CIFS paths.
	filer ext-filer, {nfs ... | cifs ...}+, and source-path src-path define the source share for the restore operation: ext-filer (1-64 characters) is the external filer where the backed-up files reside. This must be defined on the ARX as an external filer. Use the show external-filer command for a list of configured external filers. {nfs nfs-export | cifs cifs-share}+ is a required choice. For multi-protocol (NFS and CIFS) filers, you must specify both. nfs-export (1-1024 characters) is an NFS-export path. cifs-share (also 1-1024 characters) is a CIFS-share name. src-path (1-1024 characters) chooses the file or directory on the source share (for example, /backups/vol3). This path is relative to the nfs-export and/or cifs-share root, above. Use forward slashes (/) for NFS or CIFS paths. You can enter the final two options in any order, or you can omit them: recurse causes the restore operation to descend into subdirectories. remove-source removes all of the selected files and directories from the source share after a successful restore. If there is any failure, the restore operation leaves the source share intact.
Default(s)	recurse is off; the restore only restores from the top of the src-dir-path to the top of the dir-path without descending into any child directories. remove-source is off; the source share is unaffected by the restore operation.
Guidelines: Backups	You can perform backup operations on back-end filers using the same procedure that was employed prior to the introduction of the ARX. You can use a data-protection device, called a backup server in this manual, to coordinate NDMP backups from your filers to tape.
Guidelines: Finding the Backup File	Before you begin a restore operation, you need to find the backed-up version of the lost or corrupted file. To accomplish this, you must first find the filer that held the file at the time of the desired backup. Assuming you know the service FQDN or VIP, the front-end-share name, and the file path of the lost file, you can use the find command to find the actual namespace, volume, and filer where the file currently resides. For sites where migrations are frequent, or where backups are infrequent, you may need file tracking to find a file location on a particular backup date. The file-tracking process involves regular snapshots of the managed volumes configuration and metadata, which are stored on a file-history archive. Once this archive process is running, you can use the show virtual path-history command to query the archive for service names at the time of an earlier backup. This also shows the namespace, volumes, and filers that mapped to the service names at the time. Armed with this historical information, you can use show file-history virtual-service to query the archive for the file location at a given time. Once you find the filer location for the lost file, you can go to your backup server to recover the file.
Guidelines: Sending the File to a Staging Area	Recover the file from the backup server and place it onto a staging area on a filer (typically, the same filer where the file was originally backed up). A staging area is a directory that is not imported into any managed volume. The staging-area directory usually resides on a filer that is already defined as an external filer in the ARX configuration. If not, use the external-filer and ip address commands to add the new filer to the ARX database.
Note: The external-filer configuration is required so that the ARX can support multi-homed backup servers for its restore operations.
Guidelines: Restoring Files from an External Staging Area	The restore data command restores the files and directories from the staging-area directory to their managed volume, which in turn sends the files/directories to the filer(s) specified by your storage policies. Each restore operation has a unique job ID and generates a report of its progress. The reports follow this naming convention: restore.job-id.volume.rpt. Use show reports to list all reports, including restore reports. To follow the progress of the restore operation, you can use tail reports report-name follow. A sample of this report appears in Figure 32.1 on page 32-8. To view all restore operations (past and present), use show restore data. You can use the cancel restore data command to cancel a restore operation that is currently underway. To remove old records of restore operations, you can use the clear restore data command. Restore operations occur in the background so that you can continue to issue CLI commands; to pause the CLI until the restore operation to finishes, use wait-for restore data.
Guidelines: Invoking Restore from a Remote Host	From any remote host that runs the Secure SHell (SSH) program, you can run the restore data command and show the output of the report. Use the following syntax with ssh at the remote machine: ssh admin-user@mip restore-data... where admin-user is a valid user (use show users to list all of them), mip is a management-IP address for this ARX (use show interface mgmt and/or show interface vlan to list them), and restore-data... is the restore data command, surrounded by quotation marks ().
Samples	bstnA# restore data wwmed volume /acct path / filer das1 nfs /exports/backups source-path /acct recurse Scheduling restore operation on switch bstnA, report name: restore.5._acct.rpt bstnA# restores files to the wwmed~/acct volume from an NFS-only share on a filer named das1.   bstnA# restore data insur volume /claims path /stats filer nasE1 nfs /root_vdm_4/backups cifs BACKUPS source-path /stats recurse Scheduling restore operation on switch bstnA, report name: restore.7._claims.rpt bstnA# restores files to the insur~/claims volume from a multi-protocol filer named nasE1. This restores one directory tree in the volume, /stats. A sample report appears below in Figure 32.1.
Related Commands	show server-mapping export-mapping external-filer show restore data cancel restore data clear restore data wait-for restore data show reports

Purpose	Use the show restore data command to show the results of all restore operations.
Modes	(any)
Security Role(s)	operator or backup operator (any)
Syntax	show restore data show restore data namespace show restore data namespace volume vol-path show restore data namespace volume vol-path path path   namespace (optional, 1-30 characters) is the name of a namespace. Use show namespace for a list of all configured namespaces. If you omit this (and all other options), the output includes all recorded restore operations on all namespaces. vol-path (optional, 1-1024 characters) focuses on a particular volume. Use forward slashes (/) for all volumes, including CIFS. path (optional, 1-1024 characters) narrows the focus further, to a particular path within the volume. As with volumes, use forward slashes in all paths.
Default(s)	None.
Guidelines	This command shows all restore operations, past and present. They are organized by namespace, volume, and in-volume path that was restored: Namespace is a namespace where at least one restore operation occurred. Volume is one volume that was restored. Path is the specific path that was restored. This contains details about the operation: Options are recurse and/or remove-source. This does not appear unless the user selected one of these options. They are options in the restore data command. Source Filer is the name and IP address of the external filer used as a source. This is also specified in the restore data command. NFS Source identifies the NFS export used as a source share. This only appears if NFS was used in the restore operation. CIFS Source identifies the CIFS share used as a source. This only appears if CIFS was used in the restore operation. Status is Pending, Restoring, Pending Cancel, Canceling, Success, or Failed. A typical restore operation goes from Pending to Restoring to Success. Use the cancel restore data command to cancel the restore operation. For details on the restore operations progress, you can look at the restore report, identified below. Report Name is the name of a detailed report about the restore operation (and the ARX where the report is stored). You can use the show reports command to view the report. Error only appears if the restore failed. This summarizes the problem.
Guidelines (Cont.)	Items Found are the files and/or directories that were found on the Source Filer share. Items Transferred are the files and/or directories that were successfully restored to the target volume. Failures is the number of files and/or directories that were not restored. Total Bytes Restored is the number of bytes in the successfully-transferred files and directories. Completed at shows the date and time when the restore operation finished. This output grows with every run of the restore data command. Use clear restore data to clear all restore operations from this output (without deleting any of the detailed restore reports; use delete to remove those).
Samples	bstnA# show restore data displays the state of all restore operations for all namespaces. Figure 32.2 shows sample output.   bstnA# show restore data insur volume /claims displays the state of all restore operations for a multi-protocol (NFS and CIFS) volume, insur~/claims. Figure 32.3 on page 32-13 shows sample output.
Related Commands	restore data clear restore data cancel restore data

Purpose	Use the wait-for restore data command to block the CLI until one or more restore operations completes.
Mode	(any)
Security Role(s)	crypto-officer, storage-engineer, network-engineer, network-technician, or backup-operator
Syntax	wait-for restore data [timeout timeout] wait-for restore data namespace [timeout timeout] wait-for restore data namespace volume vol-path [timeout timeout] wait-for restore data namespace volume vol-path path path [timeout timeout]   The namespace, vol-path, and path arguments mimic the ones used in the restore data command. These identify one or more restore operations; if you omit all of them, the command waits for all restore operations on the switch. namespace (1-30 characters) specifies a namespace where one or more restore operations are occurring. vol-path (optional, 1-1024 characters) specifies a volume. Use forward slashes (/) for all volumes, including CIFS. path (optional, 1-1024 characters) identifies a particular path that is being restored. As with volumes, use forward slashes in all paths. timeout (optional, 1-2096) is the timeout value, specified in seconds. If this timer expires before the restore operation completes, the command exits with a warning.
Default(s)	timeout - 0 (zero, meaning wait indefinitely)
Guidelines	The wait-for restore data command waits for a specified restore operation to complete. To interrupt the wait-for restore data command, press <Ctrl-C>. Use cancel restore data to cancel the restore operation altogether.
Samples	bstnA# wait-for restore data timeout 60 waits for all restore operations on the switch to complete. If they do not complete in 60 seconds, the command returns with a warning.   bstnA> wait-for restore data insur timeout 120 waits for all restore operations in the insur namespace to complete. If they do not complete in 120 seconds, the command returns with a warning.
Related Commands	restore data show restore data cancel restore data