Experience with Quest Recovery Manager
Has anyone here had any experience using Quest Recovery Manager to restore an Exchange public folder to an alternate location? I have a customer that is trying to do this. We both understand that process is not officially supported by Veritas or Microsoft. I'm hoping a forum member has been able to make this work. They have the server setup, I've done some basic OS type backups and restores to make sure that NBU can talk to the client for both operations. I'm seeing these errors in the restore log. I'm still waiting to get the client side logs from the customer. I do not have access to that server to login and look myself. I redacted the server names.
07:28:20 (95392.001) INF - Beginning restore from server XXXXXX01-adc-01-001-nbma to client XXXXXX01.
07:28:20 (95392.001) TAR - Microsoft Information Store:\
07:28:20 (95392.001) TAR - Microsoft Information Store:\XXXXXX01\
07:28:20 (95392.001) (95392.001) ERR - Aborting restore: Error writing Exchange object: Microsoft Information Store:\XXXXXX01\ Error: BEDS 0x0:
07:28:20 (95392.001) (95392.001) INF - TAR EXITING WITH STATUS = 5
07:28:20 (95392.001) (95392.001) INF - TAR RESTORED 1 OF 2 FILES SUCCESSFULLY
07:28:20 (95392.001) (95392.001) INF - TAR KEPT 0 EXISTING FILES
07:28:20 (95392.001) (95392.001) INF - TAR PARTIALLY RESTORED 0 FILES
07:28:20 (95392.001) The following files/folders were not restored:
07:28:20 (95392.001) UTF - /Microsoft Information Store/XXXXXX01/Database
07:28:20 (95392.001) UTF - /Microsoft Information Store/XXXXXX01/Logs_1433645688
07:28:20 (95392.001) Status of restore from copy 1 of image created Sat 06 Jun 2015 07:55:51 PM PDT = socket write failed
NetBackup Master 7.5.0.7 (RHEL 6.5)
Client 7.5.0.6 (Win 2012)