Hi Greg,

By default installation there should be Servers file under the locations i had mentioned before. Please double check them again and check if this file is configured as mentioned in the Admin guide for directed recovery.

Thanks,

Ahmed Bahaa

Hello Ahmed

As I read in the Administration Guide:

If the server file is empty, then any NetWorker host can have tasking rights.

So, schould I really had this file in this machine?

Thanks for your help

Greg

Hi David,

Well until now, there is no server file on this machine. Schould be one there?

Is this a requierment?

Thanks for your help.

Greg

Hello,

I 've haded a server file with the host name of my administering client and restart the service.

# If you want other clients to be able to perform directed recovers to this

# client, you will need to add their names to the res\servers

# file. Enter one client name per line.

#

# NOTE: NO machine names in this file will open access to ALL machines

# (servers and clients) for save as well as for recover.

#

# After you save your changes, you must restart the NetWorker Remote Exec

# Service for your changes to take effect.

[Networker server host]

[Administering client host]

Then I try the recover, but I get alwas the same permission denied.

I've read in the  administration guide:

Enabling directed recoveries

Directed recovery is a restricted NetWorker function available only to users who have

all privileges except for the Change security settings privilege, which is not required

for directed recovery.

Note: Be selective in granting users the ability to perform directed recoveries. Directed

recovery privileges enable users to browse all clients and recover data to any client.

Schould that say that directed recovery is only possible with user who have remote access to all client?

Thanks in advance for your help.

Greg

If you have a blank or missing servers file then all clients are able to access that client for directed recoveries.  For a Windows client doing a directed recovery from Unix to Unix (Admin Guide does not list Linux so I am assuming these will be the same) you need the following:

• The user must have the Remote Access All Clients privilege or the user@destination_client must be listed in the source client’s Remote Access list.

• The user@destination_client must have the Recover Local Data privilege.

• The recovery must be launched by a system administrator on the administering client

I believe we have verified the first two, have you verified the TST-Networker ID you are using has sysadmin rights on the client running the recovery?

Hi David,

He probably didn't have. So now I have two question:

- If I put tst-networker as Networker Administrator, the restore work. Why? If its a right problem.

- Who can I checked the sysadmin right on the Unix server?

Thanks for your help.

Greg

All:

• The user must have the Remote Access All Clients privilege or the user@destination_client must be listed in the source client’s Remote Access list.

• The user@destination_client must have the Recover Local Data privilege.

For a Windows initiating Windows to Windows :

• The user@administering_client must be added to the Windows Administrator Group on the administering client

For a UNIX initiating UNIX to UNIX:

Nothing extra

For a UNIX initiating Windows to Windows:

• The recovery must be launched by root on the administering client.

Hello,

Here is my situation:

-    My problem happen not only with restoring a Unix on a Unix client. It's appears that's happen by restoring a Windows      to Windows client (always thru a directed recovery)

-    I got a Networker group who get the recover local data privilege.

     In this group, *@hostB (administering client) have recover local data privilège.

     I log on windows on hostB with tst-networker, so this User schould receive correct permission.

-    My User is in a Windows Group who is local  administrator of HostB (administering client).

-    This kind of redirected recovery works fine with NDMP (source and destination are in this case different).

-    I always launch the Networker user GUI as administrator.

Thanks for your help.

Greg

Greg

Easiest way to take these forward is to do the recovery from the command line and post the output, run the command, so recovering host a's data to host a on host b, at the command prompt on host b:

recover -iN -R hostA -d destinationfolder -c hostA -t date -path

We can then get a better idea as to where it is failing or if not we can run again with some verbose logging enabled

regards

David