hey guys,
i have to archive about 400TB of data over NFS. our archive backup/restore pipeline involves handing out the NetBackup java GUI to operators, having them use a specific media server to search for archived data to be restored. because of this, i need to keep all data that these guys will search for, under one client name.
this has worked fairly well over time, it allows users to find what they need by doing one search, with one client, using the java gui. however it requires all data that we archive, to be archived via one client (which also happens to be a media server).
as time goes on, it's becoming harder and harder to route all our data to be archived through this one server though. in fact i now have to archive this 400T of data, which is going to take weeks, if not months, if i have to scoop it all up via this one client/media server.
so what i'm looking for, is a way to deploy multiple media servers, and have them archive data in parallel, but have that data land in the backup catalog under a single client name, which can be searched by the java backup and restore GUI, under that single host name.
are there any tricks inside NetBackup that would help with that? i'm not aware of any.
the one thing i was thinking i might be able to do, would be to deploy a 2nd media server with a different network hostname, but set it's CLIENT NAME entry in bp.conf to match the 1st/main media server?
if i did that, would NFS backups run on both of these media servers land sanely in the backup catalog under that single hostname, and be searchable/restorable via the single client name?
or i'm thinking that might be potentially a bad thing to do?
any ideas?
thanks as usual everyone!
