jim_dalton If the node you restore to have disk issues, it can be the log apply on the database the is taking long time. As far as I remember you can see the log apply/restore in the event log on the target exchange server.
Active passive nodes versus dbs: point taken. But for the most part the copies are passive so i call em passive nodes.
The restore is to a restore db not the original which we create and select as part of restore process.
The target client is a little down-rev compared to the others (7504) but it has been functional for as long as I can remember. Rerun and logging seems like our only option.
Thanks,Jim
Jim - hate to give you the bad news, but... in this particular instance mixed revs of NetBackup Client, is... AFAIK... officially unsupported. I get the impression that Veritas try to support as many mixed application-to-aplication versions as they can, but as we know, Veritas' own hands are tied quite often by other vendors. Sometimes, and we never really know which... it is because either... 1) other vendors own prohibitions... or 2) because they simply don't have the resources to test an almost unlimited number of mixed scenarios.
Plus we haven't checked whether the MS Exchange version of the backup is supported by the down rev NetBackup Client version, have we?
IMO, I think your best bet is to update the down rev target restore client to the same NetBackup Client version that was originally used in the backup... and try again? Fingers crossed for you.
I don't think it's that bleak. I often do Exchange backups and restores with the client NetBackup version behind my master/media server. Also, I often upgrade my client between backup and restore. (Now, if your target restore client is below the version that made the backup, then we wouldn't support it. It could work, but that's not something we would test. I have my doubts whether that's your problem here. I expect the issue is on the master server.)
I'd like to know how the restore is being invoked - Windows GUI, Java console, command line. How long does the job persist in the Activity Monitor? Does tar32 on the client complete, and the job then stays in the Activity Monitor?
Can you get a level 5 log of bprd? Look for BPRESTORE in the log. Capture everything from the beginning of the parent pid to the end of it. I'm interested in how the parent pid communicates with the child pid.
(Per request previously posted in this forum, don't post a file named xxxx.log.)
jim_dalton If the node you restore to have disk issues, it can be the log apply on the database the is taking long time. As far as I remember you can see the log apply/restore in the event log on the target exchange server.
Kudos to Michael...although all the other input indeed also good to know but the log was showing us what was happening and it was just doing what it needed to do. Restore successful , db mounted and running.
