cancel
Showing results for 
Search instead for 
Did you mean: 

Phase 2 import Exchange Store

Bill_Liston
Level 4
We are trying to restore our Exchange 2003 Store (35gig) in our I-lab envirnonment. Production and I-Lab both run NB 6.0 MP4 on a windows platform. We start phase 1 import and that runs for about an 45 minutes finishing successfully. We then select just the exchange image and run phase 2. The issue is that phase 2 takes 10 hours to complete which to us seems like a very long time. Looking at the tape drive, LTO2, it shows activity, blinking light, for 3 or 4 seconds then pauses for 30 seconds or so and then shows activity again for 3 or 4 seconds over and over again.
Is there something we're missing or does a phase 2 import really take that long.

Thanks,
Bill
4 REPLIES 4

CY
Level 6
Certified
That sounds wrong for imporint/reading a 35 GB backup image on a LTO-2 tape (which holds 200 GB natively.)
 
Check the import job's log and see if there is some hint to tell you what's causing trouble.
 
Did you use Media Multiplexing for your Production backup?  If so, maybe your backup image span on several tapes and NetBackup is waiting for mouting differnt tapes and some of them are offsite?

Bill_Liston
Level 4
Thanks for the response CY,  when you refer to the import logs is that the review tab on the catalog window or is there another place that logs are stored? We don't use Multiplexing, so that doesn't come into the picture. The backup policy type is MS-Exchange-Server with multiplexing set to 1 in the schedule.

CY
Level 6
Certified
Hi Bill - yes the import log should show in the Catalog tool's "Results" tab.
 
You should be also able to read it from the NetBackup Master server:
 
/usr/openv/netbackup/logs/user_ops/<<user_ID>>/logs/XXXXXX.log
 
 
BTW, you may also want to check the bptm log (/usr/openv/netbackup/logs/bptm/) and see if it gives you any warning or error messages when the import job is running.

Message Edited by CY on 05-02-200703:48 PM

Bill_Liston
Level 4
Just a quick update. Turns out that the SCSI card that attaches the drive was bad. Replaced it and problem went away.
Thanks for your help.
Bill