Forum Discussion
- MarianneLevel 6
Hi lnbu
I came across this article from 2010. https://vox.veritas.com/t5/Articles/How-to-Create-an-Exchange-2010-Backup-Policy-in-NetBackup-7-x/ta-p/806088
Unfortunately with the move from Symantec Connect to Veritas VOX the pictures got lost.
Hopefully the detailed explanation is good enough.
Although Judy had a different master at the remote site which you don't have? Maybe there is still something useful...You will notice that a PM immediately answered with 'not supported'.
If the issue is simply with port connectivity for GRT-enabled policy, then please see this extract from NBU Ports reference guide:
The following ports must be open to use the GRT feature of NetBackup.
■ TCP port 111 (portmapper) needs to be open from the client to the media server.
■ TCP port 7394 (nbfsd) needs to be open from the client to the media server.I'm sure Veritas expert Lowell_Palecek will be along soon with more solid advice :smileywink:
- Lowell_PalecekLevel 6
The old Vox post seems all right. I think it's not necessary with later Exchange versions. I presume that the underlying issue with Exchange 2010 was that the DAG name resolved to one specific Exchange server IP. Before NetBackup 7.7.3, NetBackup needed to execute something called bpresolver on the DNS-resolved DAG. One instance of bpresolver is the "grandparent" job in the old post.
IP-less DAGs forced NetBackup to resolve the DAG name to an Exchange mailbox without the DNS. This is available for Exchange 2013 and later, and NetBackup 7.7.3 and later. NetBackup doesn't need a particular Exchange server for bpresolver, we only need some Exchange server. So if you have separate NetBackup master servers in each domain, skip the complicated part about giving each master access to clients in the other domain, and follow the advice about setting up policies.
BTW, Larry Cadloff was a great technical PM. He helped a lot of customers and support engineers figure out practical solutions to Exchange questions. He's not with Veritas anymore.
- lnbuLevel 3
Thanks for your feedback.
The client tried to backup a server with Exchange in one domain from the appliance ( master server ) that was in another domain. they only have one master server and the Exchange servers/ DB's are in diffrent domains.
The Engineers tried eas they may, they could not get the backup to work. They tried creating local accounts on the server as well as a domain account that had admin permissions on both domains and they still couldn’t get it to work.
I will share the above post and see if they have tried this.
Any feedback will be appricated.
- Lowell_PalecekLevel 6
Here I am. I'm 7 or 8 timezones behind Marianne in US Central DST (UTC-5).
I need to understand the question.
If you mean databases are in multiple domains within a forest, sure, you can do that with NetBackup, so long as get-MailboxDatabase can see the database.
You can use GRT as long as get-Mailbox in a Powershell session with ViewEntireForest enabled can see the mailboxes you need. We had a regression regarding ViewEntireForest in the 8.x releases, for which Veritas support can supply you an EEB (replacement DLL).
If all your databases have copies in your local data center, then you should make sure NetBackup chooses local copies to back up. For database-level restore, Exchange requires that NetBackup restores to the active copy of the database. You could get around that by restoring to a local RDB. For GRT restore, NetBackup only needs EWS connectivity.
Related Content
- 2 years ago
- 2 years ago
- 2 years ago
- 4 years ago