Video Screencast Help

Filesystem backup RC156 for cluster, where are no drive letters

Created: 25 Jan 2013 • Updated: 04 Sep 2014 | 3 comments
nounejmak's picture
This issue has been solved. See solution.

we have cluster windows 2008 with netbackup 7.1.0.4

master server and media server are linux with 7.1.0.3

 

Windows cluster has drives, which are reserved for customer, they will be maybe used in future

we are not allowed to set drive letters (drives are switchable, so they are on active node now, this is inactive node)

so we cannot use w2koption -backup -ignore_unresolved_volumes

 

is there any other solution for backup selection all_local_drives?

 

25.1.2013 10:07:08 - connected; connect time: 0:00:00
25.1.2013 10:07:10 - Info bpbkar (pid=3524) Backup started
25.1.2013 10:07:10 - Info bpbrm (pid=5959) bptm pid: 5961
25.1.2013 10:07:11 - Info bptm (pid=5961) start
25.1.2013 10:07:11 - Info bptm (pid=5961) using 1048576 data buffer size
25.1.2013 10:07:11 - Info bptm (pid=5961) setting receive network buffer to 262144 bytes
25.1.2013 10:07:11 - Info bptm (pid=5961) using 64 data buffers
25.1.2013 10:07:11 - Info bptm (pid=5961) start backup
25.1.2013 10:07:12 - Info bptm (pid=5961) backup child process is pid 5979
25.1.2013 10:07:12 - begin writing
25.1.2013 10:08:33 - Error bpbrm (pid=5959) from client srpdbs301239bk: ERR - Volume resolution error for (System State:\System Files\System Files)
25.1.2013 10:08:39 - Error bptm (pid=5961) media manager terminated by parent process
25.1.2013 10:08:39 - Error bptm (pid=5979) system call failed - Connection reset by peer (at child.c.1296)
25.1.2013 10:08:39 - Error bptm (pid=5979) unable to perform read from client socket, connection may have been broken
25.1.2013 10:08:41 - Error bpbrm (pid=5959) could not send server status message
25.1.2013 10:08:42 - Info bpbkar (pid=3524) done. status: 156: snapshot error encountered
25.1.2013 10:08:42 - end writing; write time: 0:01:30
snapshot error encountered  (156)

Comments 3 CommentsJump to latest comment

Nagalla's picture

could you expline why you cannot use w2koption -backup -ignore_unresolved_volumes.

ignore_unresolved_volumesis the one of the better solutions , if you want to to use ALL local Drives.

 

if not, you need to sepecifically 2 policeys, one for local Drives and another policy for  Cluster Drives as Client Name as Cluster name.

 

below tech note might give more info

http://www.symantec.com/business/support/index?pag...

SOLUTION
nounejmak's picture

the drives are not for using now

so normally you don't see these drive in windows (hired drives witout drive letters)

i cannot use w2koption, becuase these drives doesn't have letters

Marianne's picture

PLEASE read through TECH35842 -   link in Nagalla's post.

I always recommend having a minimum of two policies for clusters:

One policy for actual node names that backs up internal drives (e.g. C:\ and Shadow Copy Components).

Another policy for the virtual hostname to backup the clustered data. 

Please read through these sections of the TN: 

a) To backup the cluster nodes

b) To backup the Virtual Servers

 Ignore references to Virtual NetBackup Media Server. if clustered clients are not Media servers as well.

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