cancel
Showing results for 
Search instead for 
Did you mean: 

Backup error with NetBackup 7.0.1 on a DMZ server (status 83, media open error)

Carl-Marius
Level 4

Hi,

 

We use NetBackup 7.0.1 to backup on our DMZ servers, and on all of the servers, we get the status error 83 media open error, when the backup has run on these servers.

 

The server configuration is made on the following way (one of the servers is a test-server called cmssand01.silk.dk):

- The following information has been added to the hosts file (C:\WINDOWS\system32\drivers\etc\hosts) on the cmssand01.silk.dk:

10.15.2.X cmssand01.silk.dk

10.10.2.Y nbbackup.silk.local

10.10.3.Z nbpde.silk.local

 

This way it is possible to ping both backup-servers, and on the nbbackup.silk.local I have added the "10.15.2.X cmssand01.silk.dk" address to the hosts file.

The right ports have been opened to the DMZ-servers, so the problem should not be the firewall and it is possible to ping the server both way (from the DMZ server and to the nbbackup server and the other way).

The information I can get from the job is the following:

3/20/2011 9:59:55 PM - requesting resource PDDE_DEDUP_01
3/20/2011 9:59:55 PM - requesting resource nbbackup.silk.local.NBU_CLIENT.MAXJOBS.cmssand01.silk.dk
3/20/2011 9:59:55 PM - requesting resource nbbackup.silk.local.NBU_POLICY.MAXJOBS.Default_Puredisk_Filservere
3/20/2011 9:59:55 PM - granted resource nbbackup.silk.local.NBU_CLIENT.MAXJOBS.cmssand01.silk.dk
3/20/2011 9:59:55 PM - granted resource nbbackup.silk.local.NBU_POLICY.MAXJOBS.Default_Puredisk_Filservere
3/20/2011 9:59:55 PM - granted resource MediaID=@aaaaw;DiskVolume=PureDiskVolume;DiskPool=pdde_1;Path=PureDiskVolume;StorageServer=nbpde.sil...
3/20/2011 9:59:55 PM - granted resource PDDE_DEDUP_01
3/20/2011 9:59:55 PM - estimated 0 Kbytes needed
3/20/2011 9:59:56 PM - started process bpbrm (7020)
3/20/2011 10:00:23 PM - connecting
3/20/2011 10:00:26 PM - connected; connect time: 00:00:03
3/20/2011 10:00:30 PM - Info nbpde.silk.local(pid=2676) Using OpenStorage client direct to backup from client cmssand01.silk.dk to nbpde.silk.local 
3/20/2011 10:01:14 PM - Critical bptm(pid=2676) sts_open_target_server failed: error 2060014 operation aborted      
3/20/2011 10:01:14 PM - Critical bptm(pid=2676) failure to open proxy target server nbpde.silk.local: plug-in reports error 2060014 operation aborted
3/20/2011 10:01:16 PM - Error bpbrm(pid=7020) cannot send mail to miso@silk.dk       
3/20/2011 10:01:18 PM - end writing
media open error(83)

 

Is there a tool that can verify the connection from the client servers and to the backup-server?

 

Can you help me locate why I get this error on all our DMZ servers?

Kind regards,

Carl-Marius

1 ACCEPTED SOLUTION

Accepted Solutions

Carl-Marius
Level 4

Hi,

I opened an official supportcase at symantec for this error and thanks to Andreas Almroth (Senior System Consultant at Proact Systems A/S) we found the solution:

 

The solution was to add the "nbpde" server name to the hosts file on the DMZ zone server, when I did that it worked, as it should.

I am not sure whether it is nessacery the open the to ports above (TCP 10102 and TCP 10082) but this I will check and report back on this one.

 

Kind regards,

Carl-Marius

 

View solution in original post

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Please confirm which ports you have opened... Seems more than just vnetd and pbx is needed.

See http://www.symantec.com/docs/HOWTO36321

Carl-Marius
Level 4

Hi,

I forgot to mention what the OS is on the above servers:

cmssand01.silk.dk => MS Windows 2003 standard edition service pack 2.

nbpde.silk.local => MS Windows 2008 R2 standard edition.

nbbackup.silk.local => MS Windows 2008 R2 standard edition.

Kind regards,

Carl-Marius
 

Carl-Marius
Level 4

Hi Marianne,

The ports that I have opened from the nbbackup server to the DMZ-zone are the following:

TCP: 1025 - 5000

TCP: 13720

TCP: 13724

TCP: 13782

TCP: 13783

TCP: 1556

TCP: 2821

TCP: 4032

TCP: 53

UDP: 53 

 

Kind regards,

Carl-Marius

Carl-Marius
Level 4

Hi,

According to http://www.symantec.com/connect/articles/symantec-netbackup-7-and-firewalls I needed to open 2 addtional ports in the firewall:

 

TCP 10102 (PDDE_CTRL   10102            PureDisk Controller)
TCP 10082 (PDDE_CR        10082            PureDisk Content Router)


 

I have open these to ports, but I still get the error message:

3/23/2011 8:34:58 AM - requesting resource PDDE_DEDUP_01
3/23/2011 8:34:58 AM - requesting resource nbbackup.silk.local.NBU_CLIENT.MAXJOBS.cmsweb01.silk.dk
3/23/2011 8:34:58 AM - requesting resource nbbackup.silk.local.NBU_POLICY.MAXJOBS.Default_Puredisk_Filservere
3/23/2011 8:34:58 AM - granted resource nbbackup.silk.local.NBU_CLIENT.MAXJOBS.cmsweb01.silk.dk
3/23/2011 8:34:58 AM - granted resource nbbackup.silk.local.NBU_POLICY.MAXJOBS.Default_Puredisk_Filservere
3/23/2011 8:34:58 AM - granted resource MediaID=@aaaaw;DiskVolume=PureDiskVolume;DiskPool=pdde_1;Path=PureDiskVolume;StorageServer=nbpde.sil...
3/23/2011 8:34:58 AM - granted resource PDDE_DEDUP_01
3/23/2011 8:34:58 AM - estimated 0 Kbytes needed
3/23/2011 8:34:59 AM - started process bpbrm (7116)
3/23/2011 8:35:09 AM - connecting
3/23/2011 8:35:12 AM - connected; connect time: 00:00:03
3/23/2011 8:35:16 AM - Info nbpde.silk.local(pid=1332) Using OpenStorage client direct to backup from client cmsweb01.silk.dk to nbpde.silk.local 
3/23/2011 8:35:39 AM - Critical bptm(pid=1332) sts_open_target_server failed: error 2060022 software error      
3/23/2011 8:35:39 AM - Critical bptm(pid=1332) failure to open proxy target server nbpde.silk.local: plug-in reports error 2060022 software error
3/23/2011 8:35:42 AM - Error bpbrm(pid=7116) cannot send mail to miso@silk.dk       
3/23/2011 8:35:44 AM - end writing
media open error(83)

Kind regards,

Carl-Marius

Carl-Marius
Level 4

Hi,

I opened an official supportcase at symantec for this error and thanks to Andreas Almroth (Senior System Consultant at Proact Systems A/S) we found the solution:

 

The solution was to add the "nbpde" server name to the hosts file on the DMZ zone server, when I did that it worked, as it should.

I am not sure whether it is nessacery the open the to ports above (TCP 10102 and TCP 10082) but this I will check and report back on this one.

 

Kind regards,

Carl-Marius