01-28-2021 03:38 PM
Solved! Go to Solution.
02-01-2021 06:18 AM
For the browse to work, you need to set the destination client to a Windows client that exists. It doesn't even have to have Exchange on it. NetBackup captures the Microsoft eseutil DLL in the backup. (That's legal because it's a redistributable binary.) NetBackup uses eseutil from the backup to access the backed up image. That way, the Exchange version exactly matches.
The actual restore may work. Try it. NetBackup harvests messages with their attributes and attachments from the backup image. It constructs new messages and attachments, and tells the Microsoft EWS service to save them in the target database. This will work so long as the message from your 2010 database doesn't have an attribute that is not supported (or has changed type) in your 2016 database.
If the restore does not work because of a database incompatibility, then you will need to stand up an Exchange 2010 server as the target of your restore. Then use Exchange tools to move the messages to your 2016 server. If it comes to that and server A is still available to power up, you could use Exchange tools to move the messages directly from A to B without the NetBackup restore step.
01-28-2021 03:52 PM
To restore an Exchange mailbox you need to have a server with the same version as the backup (among other requirements). It does not need to be the same server. This can be found in the NetBackup Exchange Server Admin Guide (although not necessarily easily) see here: https://www.veritas.com/content/support/en_US/doc/19475139-127283815-0/v14706174-127283815
So you will either need to power Exchange server "A" back on, or stand up a temporary server running Exchange 2010 to enable the restore.
Annoying I know, but I think the issue is with Exchange services rather than NetBackup. This question has been asked before by the way https://vox.veritas.com/t5/NetBackup/Exchange-restores-to-different-versions/
Cheers
David
02-01-2021 06:18 AM
For the browse to work, you need to set the destination client to a Windows client that exists. It doesn't even have to have Exchange on it. NetBackup captures the Microsoft eseutil DLL in the backup. (That's legal because it's a redistributable binary.) NetBackup uses eseutil from the backup to access the backed up image. That way, the Exchange version exactly matches.
The actual restore may work. Try it. NetBackup harvests messages with their attributes and attachments from the backup image. It constructs new messages and attachments, and tells the Microsoft EWS service to save them in the target database. This will work so long as the message from your 2010 database doesn't have an attribute that is not supported (or has changed type) in your 2016 database.
If the restore does not work because of a database incompatibility, then you will need to stand up an Exchange 2010 server as the target of your restore. Then use Exchange tools to move the messages to your 2016 server. If it comes to that and server A is still available to power up, you could use Exchange tools to move the messages directly from A to B without the NetBackup restore step.
03-21-2021 04:25 PM
Hello Lowell
Finally we recreate a Exchange 2010 in order to do the restore.
thanks to all and best regards