cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

Windows 2003 and Exchange 2003 failed to restore

Iwan_Tamimi
Level 6

‎08-20-2013 11:40 PM

Hi All, 

 

We have Windows 2003 and Exchange 2003, the netbackup server is version 7.5.0.4 and also the client version. We tried serveral times to restore, looks like run but it like hang, after we wait for more than 18 hours it didn't move. Bellow is the the error:

What went wrong? What log should I check?

 

Thank you. 

 

Iwan 

 

 

08/20/2013 16:44:31 - begin Restore
08/20/2013 16:50:42 - number of images required: 1
08/20/2013 16:50:42 - media needed: 401166
08/20/2013 16:51:13 - restoring from image mocexb03_1374318025
08/20/2013 16:51:15 - Info bpbrm (pid=5796) mocexb03-bck is the host to restore to
08/20/2013 16:51:15 - Info bpbrm (pid=5796) telling media manager to start restore on client
08/20/2013 16:51:18 - Info bpbrm (pid=6296) mocexb03-bck is the host to restore to
08/20/2013 16:51:18 - connecting
08/20/2013 16:51:18 - requesting resource 401166
08/20/2013 16:51:18 - awaiting resource 401166. Waiting for resources. 
          Reason: Drives are in use, Media server: ebs5-bck, 
          Robot Type(Number): TLD(1), Media ID: N/A, Drive Name: N/A, 
          Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A, 
          Disk Pool: N/A, Disk Volume: N/A 
08/20/2013 16:51:19 - Info bpbrm (pid=6296) start tar32 on client
08/20/2013 16:51:25 - Info tar32 (pid=6852) Restore started.
08/20/2013 16:51:25 - connected; connect time: 0:00:00
08/20/2013 17:34:07 - Info bptm (pid=220) Waiting for mount of media id 401166 (copy 1) on server ebs5-bck.
08/20/2013 17:34:07 - started process bptm (pid=220)
08/20/2013 17:34:07 - mounting 401166
08/20/2013 17:34:07 - granted resource  401166
08/20/2013 17:34:07 - granted resource  ESL02_Drive7
08/20/2013 17:34:09 - Info bptm (pid=220) INF - Waiting for mount of media id 401166 on server ebs5-bck for reading.
08/20/2013 17:34:55 - mounted 401166; mount time: 0:00:48
08/20/2013 17:34:55 - Info bptm (pid=220) 401166
08/20/2013 17:34:57 - Info bptm (pid=220) INF - Waiting for positioning of media id 401166 on server ebs5-bck for reading.
08/20/2013 17:34:57 - positioning 401166 to file 30
08/20/2013 17:37:15 - positioned 401166; position time: 0:02:18
08/20/2013 17:37:15 - begin reading
08/20/2013 17:37:22 - Info bptm (pid=220) INF - Waiting for positioning of media id 401166 on server ebs5-bck for reading.
08/20/2013 17:37:22 - positioning 401166 to file 73
08/20/2013 17:39:04 - positioned 401166; position time: 0:01:42
08/20/2013 17:40:06 - Info bptm (pid=220) INF - Waiting for positioning of media id 401166 on server ebs5-bck for reading.
08/20/2013 17:40:06 - positioning 401166 to file 79
08/20/2013 17:41:20 - positioned 401166; position time: 0:01:14
4 REPLIES 4

Marianne
Level 6
Partner    VIP    Accredited Certified

‎08-21-2013 12:22 AM

We see this message a couple of times:

Waiting for positioning of media id 401166 on server ebs5-bck for reading.
positioning...
positioned...

Each time it is positioned to a different file number. So, it seems that data is read from tape and sent to the client.

Is this a full database restore (DR recovery)? Same or different Exchange server?
Or a single Information Store to a Recovery Storage Group? 

Please share exact steps that you have followed on the Exchange server 

Also post the following logs as File attachments (copy to txt files to reflect process name, e.g. bptm.txt):

On media server: bpbrm and bptm
On Exchange client: bpcd and tar


Handy NetBackup Links
0 Kudos

Thiago_Pereira
Level 4

‎08-21-2013 05:06 AM

You do multiplex backup? What is the capacity to be restored? And the transfer rate?

Because the restore is positioning reading the same media in several different sectors.

Post the logs and steps like Marianne posted.

0 Kudos

Iwan_Tamimi
Level 6

‎08-22-2013 12:21 AM

Hi All, 

 

Thank you for all the replies. 

Here are the the answer of the query:

 

Is this a full database restore (DR recovery)? Same or different Exchange server?
Or a single Information Store to a Recovery Storage Group? 

A single Information Store to a Recovery Storage Group

Please share exact steps that you have followed on the Exchange server 

Done as this Technical Solution from Symantec.

http://www.symantec.com/business/support/index?page=content&id=TECH45815

Also post the following logs as File attachments:

Attached

 

 

0 Kudos