Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Restore failed

Created: 29 Jun 2013 • Updated: 12 Mar 2014 | 4 comments

Hi every one.

Today i had restore a data present on tape.

It failed with below error .Kindly help me on how to resolved the issue.

6/29/2013 12:59:30 PM - begin Restore
6/29/2013 12:59:33 PM - media LM2089 required
6/29/2013 12:59:33 PM - restoring image POVSCITMSATLAPP_1369854844
6/29/2013 12:59:33 PM - Info bprd(pid=5696) Restoring from copy 1 of image created 05/30/13 00:44:04    
6/29/2013 12:59:40 PM - Info bptm(pid=4996) start            
6/29/2013 12:59:41 PM - started process bptm (4996)
6/29/2013 12:59:41 PM - Info bpdm(pid=4996) reading backup image          
6/29/2013 12:59:41 PM - Info bptm(pid=4996) using 30 data buffers         
6/29/2013 12:59:41 PM - Info bptm(pid=4996) spawning a child process         
6/29/2013 12:59:41 PM - Info bptm(pid=4996) child pid: 4640          
6/29/2013 12:59:42 PM - Info bptm(pid=4640) start            
6/29/2013 12:59:42 PM - started process bptm (4640)
6/29/2013 12:59:42 PM - requesting resource LM2089
6/29/2013 12:59:43 PM - Info bptm(pid=4996) Waiting for mount of media id LM2089 (copy 1) on server CHCITMSBKP02. 
6/29/2013 12:59:43 PM - started process bptm (4996)
6/29/2013 12:59:43 PM - mounting LM2089
6/29/2013 12:59:43 PM - granted resource LM2089
6/29/2013 12:59:43 PM - granted resource Drive019
6/29/2013 12:59:44 PM - Info bptm(pid=4996) INF - Waiting for mount of media id LM2089 on server CHCITMSBKP02 for reading.
6/29/2013 1:00:54 PM - mounted; mount time: 00:01:11
6/29/2013 1:00:54 PM - Info bptm(pid=4996) LM2089            
6/29/2013 1:00:57 PM - Info bptm(pid=4996) INF - Waiting for positioning of media id LM2089 on server CHCITMSBKP02 for reading.
6/29/2013 1:00:57 PM - positioning LM2089 to file 150
6/29/2013 1:02:07 PM - positioned LM2089; position time: 00:01:10
6/29/2013 1:02:08 PM - begin reading
6/29/2013 1:02:38 PM - Info bptm(pid=4996) waited for empty buffer 1239 times, delayed 1642 times    
6/29/2013 1:02:39 PM - end reading; read time: 00:00:31
6/29/2013 1:02:39 PM - positioning LM2089 to file 152
6/29/2013 1:02:39 PM - positioned LM2089; position time: 00:00:00
6/29/2013 1:02:39 PM - begin reading
6/29/2013 1:03:10 PM - Info bptm(pid=4996) waited for empty buffer 1433 times, delayed 1834 times    
6/29/2013 1:03:11 PM - end reading; read time: 00:00:32
6/29/2013 1:03:11 PM - Info bptm(pid=4996) completed reading backup image         
6/29/2013 1:03:11 PM - Info bptm(pid=4996) EXITING with status 0 <----------        
6/29/2013 1:03:15 PM - Info bpbrm(pid=2096) SCIFDRST92 is the host to restore to      
6/29/2013 1:03:16 PM - Info bpbrm(pid=2096) reading file list from client        
6/29/2013 1:03:17 PM - Error bpbrm(pid=2096) Couldn't open /usr/openv/netbackup/.rename.2096 on client SCIFDRST92, status: 28     
6/29/2013 1:03:17 PM - Error bpbrm(pid=2096) cannot put rename file on SCIFDRST92       
6/29/2013 1:03:17 PM - Info tar32(pid=0) done. status: 12: file open failed       
6/29/2013 1:03:17 PM - Error bpbrm(pid=2096) client restore EXIT STATUS 12: file open failed     
6/29/2013 2:05:15 PM - restored image POVSCITMSATLAPP_1369854844 - (cannot connect on socket(25)); restore time 01:05:42
6/29/2013 2:05:20 PM - end Restore; elapsed time: 01:05:50
VMware policy restore error(2820)

 

Operating Systems:

Comments 4 CommentsJump to latest comment

Amit Suthar's picture

 

The ALTPATH directory in \Veritas\NetBackup\logs should exist following a typical install of the NetBackup client. In this case the directory had somehow been removed after the installation. To resolve the issue, create the ALTPATH directory manually, and re-run the restore.

Try below article for more.

Article URL http://www.symantec.com/docs/TECH174179

 

Kushaal's picture

altpath directory was there under \Veritas\NetBackup\logs.

 

Any ways i have renamed the existing folder as altpath_old and create a new AltPath directory under 

\Veritas\NetBackup\logs.let see whether restore goes successfull or not.. thanks for ur ideas

 

By the way what is this AltPath directory consists of ?..thanks for ur time again

 

 

 

 

Kushaal's picture

yes amith after performing above steps restore went succesffull

Vickie's picture

Kushal,

The <install_path>\VERITAS\NetBackup\logs\AltPath exists by default on all Windows servers and it should never be deleted from client.

NBU needs this folder to create the .rename file.