A directed recovery enables a NetWorker administrator to recover data to a NetWorker host that differs from the source of the backup, while retaining the original file ownership and permissions.
A directed recovery is a restricted NetWorker function available only to user accounts that have the necessary privileges required to perform the operation.
A user with directed recovery privileges can:
· Browse the backup data of all NetWorker clients.
· Recover the data to any NetWorker client.
A directed recovery from a remote client provides an example of a directed recovery. A user on client Saturn performs a directed recovery of data from a remote client to the destination client Mars.
Figure 33 A directed recovery from a remote client
Review the requirements for a directed recovery:
Table Table 49 summarizes recover requirements for each host in a recover session.
|Table 49 General recover requirements (continued)|
|Destination||Is the same platform as the source host, for example, UNIX to UNIX or Windows to Windows.
Uses the same file system as the source host, for example, UXFS to UXFS or NTFS to NTFS.
The root user or the Administrator user on the destination host must be one of the following:
· A member of a NetWorker User Group with Remote Access All Clients privileges.
· Added to the Remote Access attribute of the source host.
The source client is mars. The destination client venus, is a Windows host. The Remote Access attribute for the client mars contains:
The servers file contains an entry for the administering host. Editing the servers file describes how to modify the servers file.
The Disable Directed Recover attribute is set to the default value No, in the NSRLA database. A value of No means that the client accepts directed recoveries from remote hosts. Editing a client NSRLA database describes how to edit the NSRLA database.
|Source||The same platform as the destination host, for example, UNIX to UNIX or Windows to Windows.
Uses the same file system as the destination host, for example, UXFS to UXFS or NTFS to NTFS.
The Remote Access attribute contains the user account of the administering host. For example:
The source client is mars and the administering client is venus. The Administrator account on venus starts the recover program. The value in the Remote Access attribute for the client mars is:
|Administering||A client of the NetWorker server that contains the backup information. The administering client can be a different platform from the source and destination clients.
Use the local root or Administrator account to start the recover. Ensure the user account is a member of one of the following:
· The Operators, the Application Administrators, the Database Administrators, or the Database Operators User Group.
Notice: You must have operator privileges in the Operators user group to perform a selective files restore from a Microsoft Windows deduplication backup. Microsoft provides complete documentation for working with the Windows deduplication functionality.
· A customized User Group with the following privileges on the NetWorker server:
Remote Access All Clients
Operate Devices and Jukeboxes
Backup Local Data
Recover Local Data
Recover Remote Data
Managing server access provides more information about access requirements
|Virtual cluster client||A Client resource for the virtual cluster client must exist on the NetWorker server.
The Remote Access attribute for the virtual cluster client must contain an entry for the root or Administrator user for each physical cluster node.
Review this section before you perform a directed recovery of a Windows client:
· You cannot a recover data from a backup that you performed on a NetWorker 8.1 or higher client to a pre-NetWorker 8.1 client.
· You cannot perform a directed recovery of the SYSTEM or VSS SYSTEM save sets.
· You cannot perform a directed recovery to a CIFS share.
· For Microsoft Windows XP Professional, the NetWorker server and clients must be in a Microsoft Windows Domain, regardless of the username and password.
· Enable the Windows File and Print Sharing option on a Windows destination client.
· If you use the recover command and the NetWorker server and clients are Microsoft Windows hosts, then:
· When the NetWorker server and the destination host are in the same domain, start the NetWorker Backup and Recovery service with a domain user that is a member of the local Administrators group.
· When the NetWorker server and destination host are not in a domain, or are not in the same domain, start the NetWorker Backup and Recovery service with a local user that exists on both hosts. The local user must have the same password on both hosts and be a member of the local Administrators group on the NetWorker server.
UNIX specific requirements
When relocating non-ASCII directories on UNIX hosts:
· If the remote directory is an existing non-ASCII directory, the locale of the administering client must match the locale of the destination client.
· If the remote directory does not exist, NetWorker creates the relocation directory on the destination file system, based on the locale of the administering client.