Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Restore getting fail with error code 2808

Created: 05 Feb 2013 | 6 comments

Hi,

I configured 2 master/media server, site 1 DC and site 2 DR,

storage unit as MSDP, and also configured SLP policy to replicate (AIR) backup data from site 1 to site 2, backup jobs are running fine and replication is alos completing successful, but while trying restore from site 2 master server to site 1 client, its getting fail with error code 2808, but if i restore from site 2 master server to local disk, its getting successful.

can, anyone guide me to fix this issue.

Thank you.

Error log :

02/05/2013 12:38:26 - begin Restore
02/05/2013 12:42:03 - restoring from image nbk-rsulaiman_1360073069
02/05/2013 12:42:03 - Info bprd (pid=6848) Restoring from copy 1 of image created 02/05/13 11:04:29
02/05/2013 12:42:03 - requesting resource @aaaab
02/05/2013 12:42:03 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=deduplication;Path=PureDiskVolume;StorageServer=nbuserverdr;MediaServer=nbuserverdr
02/05/2013 12:45:39 - Info bpbrm (pid=5540) connect failed STATUS (18) CONNECT_FAILED
02/05/2013 12:45:39 - Info bpbrm (pid=5540)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO nbk-rsulaiman 192.168.10.111 bpcd VIA pbx
02/05/2013 12:45:39 - Info bpbrm (pid=5540)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO nbk-rsulaiman 192.168.10.111 bpcd VIA vnetd
02/05/2013 12:45:39 - Info bpbrm (pid=5540)  status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO nbk-rsulaiman 192.168.10.111 bpcd
02/05/2013 12:45:39 - Error bpbrm (pid=5540) Cannot connect to nbk-rsulaiman
02/05/2013 12:45:39 - Info tar32 (pid=0) done. status: 58: can't connect to client
02/05/2013 12:45:39 - Error bpbrm (pid=5540) client restore EXIT STATUS 58: can't connect to client
02/05/2013 12:45:39 - restored from image nbk-rsulaiman_1360073069; restore time: 0:03:36
02/05/2013 12:45:39 - Warning bprd (pid=6848) Restore must be resumed prior to first image expiration on 2/19/2013 11:04:29 AM
02/05/2013 12:45:39 - end Restore; elapsed time 0:07:13
Windows File System policy restore error  (2808)

02/05/2013 13:31:43 - begin Restore
02/05/2013 13:31:43 - restoring from image nbk-rsulaiman_1360073069
02/05/2013 13:31:43 - requesting resource @aaaab
02/05/2013 13:31:44 - Info bprd (pid=6580) Restoring from copy 1 of image created 02/05/13 11:04:29
02/05/2013 13:31:44 - granted resource  MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=deduplication;Path=PureDiskVolume;StorageServer=nbuserverdr;MediaServer=nbuserverdr
02/05/2013 13:35:20 - restored from image nbk-rsulaiman_1360073069; restore time: 0:03:37
02/05/2013 13:35:20 - end Restore; elapsed time 0:03:37
Windows File System policy restore error  (2808)

Discussion Filed Under:

Comments 6 CommentsJump to latest comment

Marianne's picture

Your site 2 master cannot connect to site 1 client:

... Cannot connect to nbk-rsulaiman
... done. status: 58: can't connect to client

Connection was attempted to client via PBX (port 1556), vnetd (13724) and bpcd (13782), All connection attempts were refused:

CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO nbk-rsulaiman 192.168.10.111 bpcd VIA pbx

CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO nbk-rsulaiman 192.168.10.111 bpcd VIA vnetd

CONNECT_REFUSED; system: (10060) Connection timed out.; FROM 0.0.0.0 TO nbk-rsulaiman 192.168.10.111 bpcd

Check that port 1556 is open in both directions between site 2 master and client.
Check that client can resolve IP address from site 2 master to a hostname and that resolved hostname has SERVER entry on client.

Enable bpcd log on site 1 client if you need further assistance. 
If nothing is logged in client's bpcd log during restore attempt, chances are that firewall is blocking connection.
If anything is logged, please copy file to bpcd.txt and post as file attachment.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Mark_Solutions's picture

Not only do your media servers need to resolve the client, the client needs to resolve the media servers

They will also need to be in the clients server list or the client will refuse connection when you try the restore as the DR media servers are not valis servers

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.

NBU_13's picture

Hi Mark,

yes, I added both (source and target media server name in client´s server list) and also there is no firewall block, same domain,

 but ports (1556, 13782, 13724) are not connecting between 2 master servers.

Marianne's picture

Please post client's bpcd log.

Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows
Handy NBU Links

Stumpr2's picture

Add to bp.conf

FORCE_RESTORE_MEDIA_SERVER = from_host to_host

 

Did you run this after adding valid media servers?

/usr/openv/netbackup/bin/admincmd/bprdreq -rereadconfig

 

VERITAS ain't it the truth?

Mark_Solutions's picture

As Marianne says the bpcd log from the client would be the best thing here - if it does not log anything then there is no communication and you need to check all hosts files etc. again, otherwise it may show us what the problem is.

You can also try a telnet across sites - if you cannot do it then there is a firewall in the link somewhere (there usually is between sites)

Also make sure the media server resolves the client by short and FQDN and vice versa, this can be important in de-dupe environments.

Lets see the clients bpcd log first (and the media servers too) and tell us the exact time that you try the operation.

You could also make a blank policy on the DR site and add the client in - that way it will appear under client host properties (though you  would also need to make the server you run the console from a valid server too)

Authorised Symantec Consultant

Don't forget to "Mark as Solution" if someones advice has solved your issue - and please bring back the Thumbs Up!!.