cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup Restores failing after upgrade to 7.1.0.1

David_V_NL
Level 3

Hello

This is my first post on the forum

I have a problem restoring files after an upgrade from netbackup 6.5.5. to 7.1.0.1 and upgrading the ost plugin from 1.1.4.2 to 2.2.3.0
After i upgraded the master and media servers i cant restore files anymore form backup taken before the upgrade.
The funny thing is that i can restore files from backups taken after the upgrade.
Can anybody help me?

See joboutput below (is from ndmp restore but all types of restore fail)

9/9/2011 8:38:51 AM - begin Restore
9/9/2011 8:38:51 AM - restoring image server1.company.com_1313834400
9/9/2011 8:38:52 AM - requesting resource @aaaai
9/9/2011 8:38:52 AM - granted resource MediaID=@aaaai;DiskVolume=DataDomain-stu;DiskPool=DataDomain_diskpool;Path=DataDomain-stu;StorageSer...
9/9/2011 8:38:54 AM - Info bpbrm(pid=6488) server1.company.com is the host to restore data    
9/9/2011 8:38:54 AM - Info bpbrm(pid=6488) reading file list from client      
9/9/2011 8:38:56 AM - connecting
9/9/2011 8:38:56 AM - Info bpbrm(pid=6488) starting bptm         
9/9/2011 8:38:56 AM - Info ndmpagent(pid=4868) Restore started         
9/9/2011 8:38:56 AM - connected; connect time: 00:00:00
9/9/2011 8:38:56 AM - Info bptm(pid=6216) start          
9/9/2011 8:38:56 AM - started process bptm (6216)
9/9/2011 8:38:57 AM - Info bpdm(pid=6216) reading backup image        
9/9/2011 8:38:59 AM - Critical bptm(pid=6216) image open failed: error 2060013: no more entries   
9/9/2011 8:39:00 AM - Error ndmpagent(pid=4868) terminated by parent process       
9/9/2011 8:39:02 AM - Info ndmpagent(pid=4868) done          
9/9/2011 8:39:02 AM - restored image server1.company.com_1313834400 - (media open error(83)); restore time 00:00:11
9/9/2011 8:39:02 AM - end Restore; elapsed time: 00:00:11
media open error(83)
9/9/2011 8:39:02 AM - Error ndmpagent(pid=4868) NDMP restore failed from path UNKNOWN

1 ACCEPTED SOLUTION

Accepted Solutions

David_V_NL
Level 3

Hello,

The problem is solved

on advise of symantec support I downgraded the ost pluging and tried the restore again. Now it was working again. So I opened a case with datadomain.

They told me the OST pluging had a know issue in it.

It had to do with the name of the imagefiles on the datadomain. if  the image file on Data Domain system ends with :4:5::  it could'nt be read

I got a new version of the OST plugin (2.3.2.0) and the restores are working fine again.

Everybody thanks for the reply's

 

David

View solution in original post

4 REPLIES 4

CRZ
Level 6
Employee Accredited Certified

Sorry to say, this really sounds like something you would need to contact support and get a case opened for.

RonCaplinger
Level 6

Our OST plugin was already at 2.2.3.0, but otherwise had a similar setup and had no problems with older backups.  I agree with Chris: call Symantec support.

David_V_NL
Level 3

 

Thanks everybody for the reply

 

I opened a case with support. If resolved ill try to post a solution

David

David_V_NL
Level 3

Hello,

The problem is solved

on advise of symantec support I downgraded the ost pluging and tried the restore again. Now it was working again. So I opened a case with datadomain.

They told me the OST pluging had a know issue in it.

It had to do with the name of the imagefiles on the datadomain. if  the image file on Data Domain system ends with :4:5::  it could'nt be read

I got a new version of the OST plugin (2.3.2.0) and the restores are working fine again.

Everybody thanks for the reply's

 

David