NetBackup client acting as another?

[Fraser73]

In TSM there is a function to allow one "node" (client) to "act as nodename", that is you can effectively get ClientA to make a backup as ClientB, with all the files appearing as if ClientB has backed them up in ClientB's backup lists. Is anything like this possible in NetBackup?

[J_H_Is_gone]

but please tell us your final goal - if we knew what you were trying to achieve - we may know how to do it in NB.

[RiaanBadenhorst]

The only reason I can see you wanting to do that is to restore files from server 1 to server 2. You can do that with altnames. See this post.

https://www-secure.symantec.com/connect/forums/backup-and-restore-different-server

[Marianne]

Or maybe to backup virtual name in a cluster?

We really need more info...

(nice to have you back Riaan!!)

[Nicolai]

If you use Netbackup Snapshot client, some soloutions offer off-host option where data is read by a alternate server, but the backup is registred under the source name.

http://www.symantec.com/docs/TECH126901

[Fraser73]

Sorry for the lack of info, here is the background...

We use mount servers to backup some of our larger systems, so a disk snapshot of ServerA is mounted up for offline backup on a SAN attached media server AKA mount server, ServerB. Currently our guys who do restores need to know that there is a mount server being used and which one, in order that redirected restores can be carried out to the original client. This means that it is difficult for them to find backups if we've installed more mount servers and moved around the location that the backups are taken, there is a reliance on documentation, and inevitably this doesn't get updated, or takes time to find etc.

It would be nice if I can backup a filesystem on the mount server, ServerB, but when the Backup Archive and Restore client is opened on ServerA it shows this backup in the list of data from ServerA, even though it was actually backed up on ServerB.