Video Screencast Help

Quesiton regarding restoring from a cluster

Created: 03 Oct 2013 • Updated: 29 Nov 2013 | 9 comments
This issue has been solved. See solution.

Hi,

Just looking for advice. I have backed up a windows 2003 cluster, which has 2 nodes. One of the nodes failed yesterday (lets called it Node1). Node1 held all the disk's that were being backed up, some of which were a disk pool for NBU backup images to sit on.

Node2 now has the disks. When I come to restore a file that was backed up when the disk was on Node1 I can't (Status 10) as it appears to be looking for the node1 path. If I fail the disk back to the newly rebulilt Node1 it restores fine.

So we are in a situation where some backup images 'belong' to node1 and some node2. I may have to fail the disks back over if I need to restore from node2 crops up.

Is this just how it works, or is my configuration wrong?

 

NBU 7.1.0.1

Windows 2008 R2

 

Operating Systems:

Comments 9 CommentsJump to latest comment

Marianne's picture

Which hostname was used to backup the cluster data?

If virtual name was used, you should be able to browse backups for VirtName and also restore to VirtName. This will ensure that data goes to the active node where data disks are currently mounted.

If backup was done using Node1 as Client name, you should be able perform the restore from the master server with Node1 as source client and Node2 as destination client.

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

Nagalla's picture

hi,

 i understand your situation.. 

in your case.. all the cluster drives are backup with the Node name.. that is the reason you  are in this situation..

so to make a easy and succesfull restore..you need to use alternate client restore option

lets say.. backup was happend when disk are in Node 1 and now the disk are in node 2 and would like to do the restore..

so in the restore

select source client as node1

destination client as node2

and start the restore..

on other words.. what ever the source client would be alwasy select the node which is having the disks as a destination client to have the successfull restore.

 

------

if you could have configured the cluster backup using the Cluster VIP , that would be very smooth and like the regulare restore for you.

see the below tech note for backups of cluster node configured 

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

Vince_Noir's picture

I don't think that would solve the issue as the disk's (in a disk pool) netbackup are backing up to are part of the cluster too. So I think that the initial problem is finding the disks to restore from in the first place.

Marianne's picture

Your Storage Unit should also be configured with Virtual Name, not physical node name. You need to configure 'Application Cluster' in NBU.

See 'About protecting against SAN media server failures' and 'About installing media servers in clusters' as well as 'About virtual storage units in a NetBackup cluster' in NetBackup in Highly Available Environments Administrator's Guide http://www.symantec.com/docs/DOC5183 for information and detailed steps.

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

SOLUTION
Nagalla's picture

I don't think that would solve the issue as the disk's (in a disk pool) netbackup are backing up to are part of the cluster too. So I think that the initial problem is finding the disks to restore from in the first place

 

could you expline it more detail... somehow i dont understand it..

Vince_Noir's picture

The 2 cluster nodes are also media servers, four of the disks are used to create a disk pool that netbackup uses as a storage unit. When a backup was performed the disk pool was on node 1, now they are node 2. I think what the problem is when a restore is requested it's looking for the path for node1, it's looking for it's windows computer name it appears.

Marianne's picture

As per my previous post - you need to create App_Cluster in NBU so that you can use the Virtual Name in Storage Unit config.

The policy then also needs to backup Virtual name and not node name(s).

Please read through the sections of the manual that I have mentioned above.

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

Jaime_Vazquez's picture

Another thing you may try:

1. Set up "automatic failover to an alternate server" on the Master.

2. Set up "Media Host overide" in the Master Server.

See the NBU Admin Guide for specifics on setting it up.