Redirect client to backup to different networker server

Thank you for your answer. That´s possible, but the problem is, that the different networker server does not know about the client and will perform a full backup, which should not happen, because it takes two days to complete, which I can only do on the weekend.

I would like to keep the client and savegroup configuration and indexes on the original server and just use the tape storage on another server. Is that possible, too?

Yes you can.

Well, pretty simple actually.

- On the client check the servers file and ensure that the name of the "different networker server" is listed in it. if not add it in the list and restart the nsrexecd services for this to take affect.

- Created a client instance for the machine on the "different networker server" and configure th egroup and schedule accordingly. Test backups and you are good to go.

All said, note that the backup that are done on the "different networker server" can be recovered only on that server.

Oh, that´s too bad. The server with the working library is a full networker server and backs up different clients than  the other server. All I want to do is to use the tape storage of the other server, but this seems to be impossible.

Now I hope I am lucky and I don´t need to recover anything until the library is repaired.

Thanks for you help,

Andreas

Just remember that you can add the older backups to another data zone (NW server) through scanning. But this will take its time, too.

Yep, incase you are not using the other networker servers as a production server. Because if you are using it as a storage node on the current server then you cannot use it as a NetWorker server. As long as this is OK, the only change you have to do is to modify the Storage Nodes field in the client properties to list the new Storage node. Of cource you have to add the new other server as a storage node on the current NetWorker server and configure the library on it.