01-22-2016 08:50 AM
What is the necessary requirements to allow a client to be accessed by both (old & new) NB servers?
Solved! Go to Solution.
01-22-2016 09:57 PM
01-22-2016 09:37 AM
What do you mean by old and new? Different domains (different masters)?
If so, a client can only be in one domain at a time, so you can move it between domains temporarily (to maybe restore something), but you'd not want to do that on a regular basis.
01-22-2016 10:55 AM
You wouldn't want to be doing any kind of incremental (differential or cummulative) backups to two different NetBackup domains.
Personally, I think the most significant problem with having plain file-system basd "full" backups to two different NetBackup domains would be scheduling overlap... the very real possibility of two full backups occuring at the same time... which might make the OS throw a wobbly... and I would have thought that a Windows based backup client would feel more pain than a Unix/Linux client. Knowing what I know about Windows, I can't see it reacting very well to two overlapping backups. And if you use any kind of file system "change journal tracking" then... who knows, it's anyone's gues as to what might happen with files being skipped because they've already been marked as being captured. Hmmm. I wouldn't do it. I've never done this. And I've never seen a site that does.
01-22-2016 12:12 PM
To answer your question, the requirement is nothign more than "server" name entries for both masters and/or any medias (from eitehr environment) in the "server" list of the client. The first server entry will always be the true master of the client.
i.e. if multiple master server names appear in the server list of the client, then both masters can manage the client. If you have seperate media servers in each NetBackup domain, then the names of any media server which will also be doing the actual backup will also need to be in the of "server" names on the actual client.
01-22-2016 09:57 PM