Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Windows Fileserver Cluster backup issue

Created: 11 Dec 2012 | 2 comments

Hello all,

I've a windows server 2003 fileserver cluster which seems to give problems with regular backups when failover happens. 

The backup begins as scheduled but does not seem to move anywhere. There is no error on job activity, it just says backup started and is in the state for 2 days. Though I ensured that after the failover the active node is set to the one where backups were successful, it still does not move anywhere.

Job activity from one of the policies on the server is as follows:

 

12/11/2012 5:45:55 PM - Info nbjm(pid=2660) starting backup job (jobid=69378) for client <ClientName>, policy <PolicyName>, schedule Daily  
12/11/2012 5:45:55 PM - Info nbjm(pid=2660) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=69378, request id:{FC21A6BB-75A8-4B2F-9A61-D119AE210C3F})  
12/11/2012 5:45:55 PM - requesting resource <StorageUnit>
12/11/2012 5:45:55 PM - requesting resource <MasterServer>.NBU_CLIENT.MAXJOBS.<ClientName>
12/11/2012 5:45:55 PM - requesting resource <MasterServer>.NBU_POLICY.MAXJOBS.<PolicyName>
12/11/2012 5:45:55 PM - granted resource <MasterServer>.NBU_CLIENT.MAXJOBS.<PolicyName>
12/11/2012 5:45:55 PM - granted resource <MasterServer>.NBU_POLICY.MAXJOBS.<PolicyName>
12/11/2012 5:45:55 PM - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=Deduplication_Pool;Path=PureDiskVolume;StorageServer=<MasterServer>;MediaServer=<MasterServerIsMediaServer>
12/11/2012 5:45:55 PM - granted resource Dedulication_Storage_unit
12/11/2012 5:45:55 PM - estimated 694192476 Kbytes needed
12/11/2012 5:45:55 PM - begin Parent Job
12/11/2012 5:45:55 PM - begin Snapshot, Start Notify Script
12/11/2012 5:45:55 PM - Info RUNCMD(pid=10212) started            
12/11/2012 5:45:55 PM - Info RUNCMD(pid=10212) exiting with status: 0         
Status 0
12/11/2012 5:45:55 PM - end Snapshot, Start Notify Script; elapsed time: 00:00:00
12/11/2012 5:45:55 PM - begin Snapshot, Step By Condition
Status 0
12/11/2012 5:45:55 PM - end Snapshot, Step By Condition; elapsed time: 00:00:00
12/11/2012 5:45:55 PM - begin Snapshot, Stream Discovery
Status 0
12/11/2012 5:45:55 PM - end Snapshot, Stream Discovery; elapsed time: 00:00:00
12/11/2012 5:45:55 PM - begin Snapshot, Read File List
Status 0
12/11/2012 5:45:55 PM - end Snapshot, Read File List; elapsed time: 00:00:00
12/11/2012 5:45:55 PM - begin Snapshot, Create Snapshot
12/11/2012 5:45:55 PM - started process bpbrm (9944)
12/11/2012 5:46:13 PM - Info bpbrm(pid=9944) <ClientName> is the host to backup data from     
12/11/2012 5:46:13 PM - Info bpbrm(pid=9944) reading file list from client        
12/11/2012 5:46:13 PM - Info bpbrm(pid=9944) start bpfis on client         
12/11/2012 5:46:13 PM - Info bpbrm(pid=9944) Starting create snapshot processing         
12/11/2012 5:47:46 PM - Info bpfis(pid=5836) Backup started           
 
*************************  After the last line, the backup activity is just stuck for hours  ***************************

Any help would be appreciated.

Regards,

Adnan

 

Comments 2 CommentsJump to latest comment

Marianne's picture

Is Client name in Policy set to the Virtual hostname or physical nodenames?

What exactly do you have in the Backup Selection?

See this TN for Cluster policy recommendations: http://www.symantec.com/docs/TECH35842
TN is old, a bit messy, but still valid.

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

Adnan F's picture

Thanks Marianne for the response.

Just reinstalled the agent and it seemed to do the trick. Some other symptoms of my problem were (for others who may face same issue):

1. Netbackup Client Legacy Service - just wont stop, it would literally say stopping and never come up.

2. bpdown command just did not stop the Netbackup services on either cluster node

3. There also seemed to be too many bpfis processess running

4. There were VSS errors on event viewer of the active cluster node

Had the whole thing checked up by Symantec Support, who recommended to reinstall the agent and after which issue was resolved.