bak restoredisk(8dfs)

Restores the contents of an entire aggregate from tape

Synopsis

bak restoredisk -server machine -aggregate name [-tcid tc_number]
[-newserver machine] [-newaggregate name] [-noaction] [-help]

Alias
bak dkrestore

Options

-server machine
Names the File Server machine that houses the aggregate you want to restore. Specify the File Server machine using the machine's DCE pathname, the machine's host name, or the machine's IP address.

-aggregate name
Specifies the device name or aggregate name of the aggregate on the machine indicated with the -server option that you want to restore. These names are specified in the first and second fields of the entry for the aggregate in the dcelocal/var/dfs/dfstab file.

-tcid tc_number
Specifies the Tape Coordinator ID (TCID) of the Tape Coordinator for the tape drive in which you are placing the necessary tapes. If omitted, it defaults to 0 (zero).

-newserver machine
Names the File Server machine to which to restore the data. Specify the File Server machine using the machine's DCE pathname, the machine's host name, or the machine's IP address. Use this option only if the destination server is different from the server specified with the -server option.

-newaggregate name
Specifies the device name or aggregate name of the aggregate to which to restore the data. These names are specified in the first and second fields of the entry for the aggregate in the dfstab file. Use this option only if the name of the destination aggregate is different from the name of the aggregate specified with the -aggregate option.

-noaction
Directs the command to display the list of tapes necessary to perform the indicated restore without actually performing the operation.

-help
Prints the online help for this command. All other valid options specified with this option are ignored.

Description
The bak restoredisk command restores the contents of the aggregate specified with the -server and -aggregate options to the file system. To do this, the bak program contacts the Fileset Location Server (FL Server) for a listing from the Fileset Location Database (FLDB) of all the filesets that reside on the specified aggregate. It then consults the Backup Database to learn which tapes contain the full and incremental dumps needed to restore every fileset from the aggregate. This command is useful if a disk or machine failure destroys the data on an entire aggregate.

To restore filesets from the specified aggregate to the same site (the site specified with the -server and -aggregate options), omit the -newserver and -newaggregate options. The data in the restored filesets overwrites the filesets' current contents; there is no change in the Fileset Location Database (FLDB) entries for the filesets.

To restore the filesets to an alternate site, include the -newserver option, the -newaggregate option, or both. The filesets continue to use their existing FLDB entries and fileset ID numbers, and the filesets' FLDB entries are updated to record the new site. The current contents of each fileset are replaced with the data restored from tape. The command allows you to restore filesets to a new site as follows:

· To restore the filesets to a different aggregate on the same File Server machine, specify the new aggregate with the -newaggregate option.

· To restore the filesets to an aggregate of the same name on a different File Server machine, specify the new File Server machine with the -newserver option.

· To restore the filesets to a completely different site, specify the new File Server machine with -newserver option and the new aggregate with the -newaggregate option.

If you specify a new site and the filesets to be restored currently exist at their old site, you must use the fts zap command to delete the existing filesets before issuing the bak restoredisk command. The bak restoredisk command fails if you do not use the fts zap command to delete the existing filesets before using the bak restoredisk command to restore the filesets to the new site.

Note: Do not use the fts delete command to delete the existing filesets and their FLDB entries before issuing the bak restoredisk command. If you use the fts delete command instead of the fts zap command, you cannot use the bak restoredisk command to restore the filesets; you can restore the filesets only with the bak restoreft command.)

The -noaction option instructs the command to produce a list of the tapes the Backup System would need to perform the indicated restore without actually performing the operation. To do so, include the -noaction option with all of the other options to be used with the actual command.

Data can be dumped and restored between different types of file systems. For example, data dumped from a DCE LFS fileset can be restored to a DCE LFS fileset or to any type of non-LFS fileset; likewise, data dumped from a non-LFS fileset can be restored to a DCE LFS fileset or to a different type of non-LFS fileset. (See your vendor's documentation to verify the level of support for dump and restore operations between different types of file systems.)

Restored data is translated into the appropriate format for the file system to which it is restored. Note that incompatible information may be lost when a fileset is dumped and restored between different types of file systems. For example, ACLs on objects in a DCE LFS fileset may be lost if the fileset is restored to a file system that does not support ACLs.

Use the bak restoreft command to restore one or more filesets to a single site. Use the bak restoreftfamily command to restore a fileset family or to restore one or more filesets to the same site or to different sites.

Privilege Required
The issuer must be listed in the admin.bak files on all Backup Database machines. The issuer must also be listed in the admin.fl files on all Fileset Database machines and in the admin.ft file on the File Server machine to which filesets are to be restored.

Output
If you do not include the -noaction option, the bak restoredisk command returns the unique dump ID number associated with the restore operation. The dump ID is displayed in the command window following the command line and in the Tape Coordinator's monitoring window if the butc command is issued with debug level 1. The dump ID is not the same as the job ID number visible with the (bak) jobs command if the bak restoredisk command is issued in interactive mode.

If you include the -noaction option, a Tapes needed: header is displayed, followed by a list of the tapes necessary to complete the restore operation. No dump ID number is reported because none is assigned.

Examples
The following command restores the filesets listed in the FLDB as residing on the aggregate named /dev/lv01 on the File Server machine named fs5. The filesets are restored to the same aggregate and server machine. Tapes are placed in the drive with TCID 3.

$ bak restored /.../abc.com/hosts/fs5 /dev/lv01 3

Starting restore

bak: dump ID of restore operation: 253

bak: Finished doing restore

The following command restores the filesets listed in the FLDB as stored on the aggregate named /dev/lv02 on the File Server machine named fs1. The filesets are restored to a new site, the aggregate /dev/lv01 on the File Server machine fs3. The fts zap command is used to delete existing filesets from the current site before the bak restoredisk command is issued. Tapes are placed in the drive with TCID 0 (zero).

$ bak restored /.../abc.com/hosts/fs1 /dev/lv02 -news /.../abc.com/hosts/fs3 \
-newa /dev/lv01

Starting restore

bak: dump ID of restore operation: 256

bak: Finished doing restore

Related Information
Commands: bak dump(8dfs)

bak restoreft(8dfs)

bak restoreftfamily(8dfs)

fts delete(8dfs)

fts zap(8dfs)

Files: dfstab(4dfs)