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

issue on VNB.

Created: 04 Oct 2012 • Updated: 17 Dec 2012 | 4 comments
This issue has been solved. See solution.

Marianne - I am new to netbackup and the links you provided are very useful. I got stuck in one of the issue on VNB. Could you please help me out on this...Much appreciated for the quick response.

I've a solaris 10 backup master server(sun-zone-2) with version 7.5
I've a global zone(sun-zone-1) with local zone (sun-zone-1z).
I subscribed the global zone to backup server to my understand the local zone gets backuped up automatically and netbackup skips lofs, socket, door files.However /n1z_sw & /n1z_DBs are also getting skipped as the LUNS are coming from a filer server and we created a ZFS filesystem. Please see below output.

root@sun-zone-1 #> df -h | grep n1z
sun-zone-1z           49G    14G    35G    30%    /sun-zone-1z
n1z_DBs                345G   150G   194G    44%    /n1z_DBs
n1z_sw                  49G    29G    20G    60%    /n1z_sw

root@sun-zone-1 #> zpool list
NAME            SIZE  ALLOC   FREE    CAP  HEALTH  ALTROOT
sun-zone-1z  49.8G  14.5G  35.3G    29%  ONLINE  -
n1z_DBs         350G   150G   200G    42%  ONLINE  -
n1z_sw         49.8G  29.2G  20.6G    58%  ONLINE  -
rootpool        136G   100G  35.7G    73%  ONLINE  -
temppool        272G  15.8G   256G     5%  ONLINE  -

root@sun-zone-1 #> zpool status n1z_DBs
  pool: n1z_DBs
 state: ONLINE
 scan: none requested
config:

        NAME                      STATE     READ WRITE CKSUM
        n1z_DBs                   ONLINE       0     0     0
          c2t500A09818AC19CDEd10  ONLINE       0     0     0

errors: No known data errors

root@sun-zone-1 #> zoneadm list -cv
  ID NAME             STATUS     PATH                           BRAND    IP
   0 global           running    /                              native   shared
   1 sun-zone-1z    running    /sun-zone-1z                 native   shared
root@sun-zone-1 #>

On the global zone i've created exclude_list file and provide /proc /tmp /devices directories however it still shows that in the log status.

On the backup server i've selected "cross mount points" and / in backup selections options instead of ALL_LOCAL_DRIVES.

10/03/2012 17:23:05 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/oraprod is on file system type lofs. Skipping.
10/03/2012 17:23:05 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/etc/mnttab is on file system type mntfs. Skipping.
10/03/2012 17:23:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/etc/svc/volatile is in a different file system from /sun-zone-1z. Skipping.
10/03/2012 17:23:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/sw is on file system type lofs. Skipping.
10/03/2012 17:23:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/proc is on file system type PROC. Skipping.
10/03/2012 17:23:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/DBs is on file system type lofs. Skipping.
10/03/2012 17:23:10 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/system/object is on file system type objfs. Skipping.
10/03/2012 17:23:10 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/system/contract is on file system type ctfs. Skipping.
10/03/2012 17:23:10 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/tmp is in a different file system from /sun-zone-1z. Skipping.
10/03/2012 17:28:09 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/root/var/run is in a different file system from /sun-zone-1z. Skipping.
10/03/2012 17:28:09 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z/dev/.devfsadm_synch_door is a door file. Skipping.
10/03/2012 17:42:57 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /export/home is in a different file system from /export. Skipping.
10/03/2012 17:43:05 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /etc/mnttab is on file system type mntfs. Skipping.
10/03/2012 17:43:06 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /etc/svc/volatile is in a different file system from /. Skipping.
10/03/2012 17:43:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /etc/sysevent/sysevent_door is a door file. Skipping.
10/03/2012 17:43:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /etc/sysevent/piclevent_door is a door file. Skipping.
10/03/2012 17:43:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /etc/sysevent/syseventconfd_event_channel/reg_door is a door file. Skipping.
10/03/2012 17:43:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /etc/sysevent/devfsadm_event_channel/reg_door is a door file. Skipping.
10/03/2012 17:43:07 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /etc/sysevent/devfsadm_event_channel/1 is a door file. Skipping.
10/03/2012 17:43:09 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /temppool is in a different file system from /. Skipping.
10/03/2012 17:43:09 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /usr/openv/var/vnetd/bpcd.uds is a socket special file. Skipping.
10/03/2012 17:43:09 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /usr/openv/var/vnetd/terminate_vnetd.uds is a socket special file. Skipping.
10/03/2012 17:43:09 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /usr/openv/var/vnetd/terminate_bpcd.uds is a socket special file. Skipping.
10/03/2012 17:46:42 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /sun-zone-1z is in a different file system from /. Skipping.
10/03/2012 17:46:47 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /system/contract is on file system type ctfs. Skipping.
10/03/2012 17:46:47 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /system/object is on file system type objfs. Skipping.
10/03/2012 17:46:50 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /devices is in a different file system from /. Skipping.
10/03/2012 17:46:50 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /export is in a different file system from /. Skipping.
10/03/2012 17:46:50 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /rootpool is in a different file system from /. Skipping.
10/03/2012 17:46:52 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /proc is on file system type PROC. Skipping.
10/03/2012 17:46:52 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /tmp is in a different file system from /. Skipping.
10/03/2012 17:46:52 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /n1z_sw is in a different file system from /. Skipping.
10/03/2012 17:46:52 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /n1z_DBs is in a different file system from /. Skipping.
10/03/2012 18:05:00 - Info bpbrm (pid=2906) from client sun-zone-1: TRV - /var/run is in a different file system from /. Skipping.

Discussion Filed Under:

Comments 4 CommentsJump to latest comment

Marianne's picture

Please show us what your backup policy looks like? 

Post output of this command on the master:
/usr/openv/netbackup/bin/bppllist <policy-name> -U

When / is backed up, it is perfectly normal to see all other file systems being skipped. It will be backed up when NBU gets to that filesystem, depending what is specified in the Backup Selection.

If you have any databases running in the local zones and you do not wish to shut them down before global backup runs, install NBU client software in the zone and use the appropriate agent to backup the database.

See this TN for zone backup recommendations: http://www.symantec.com/docs/TECH65627

 

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

SOLUTION
raju3235's picture

Thanks Marianne,

I keep reading your blogs for couple of weeks and were very useful... I am in a situation where I am not able to resolve netbackups for the VMware machines....

Here is the brief summary of my setup.
 
All together we've four machines as catagorized below.
 
1) Unix machine hosting solaris 10 and serves as veritas Netbackup master server Ver 7.5
 
2) Storage Tek 48 Tape library
 
3) Netapp filer
 
4) Windows 2008 server with Netbackup client which acts as a proxy server for ESX hosts.
 
5) Two ESX hosts hosting 40 VMs each
 
All the above servers are connected through FC to brocade FC switch.
 
 
6) Few unix clients connected through LAN
 
 
 
My concern is I need to fire backups over the SAN so that the VMs get backedup on Tapes.For this to work I've configured the following....
 
 
I've created two LUNS of size 4TB each on NetApp and presented them to windows 2008 machine. These LUNS are configured as datastores on the ESX hosts for the VMs.
 
configuration at Netapp side..
 
a) Created initiator group with windows and one ESX host.
b) Created another initiator group with windows and other ESX host.
 
 
Please help me how to troubleshoot this issue I've all the necessary Licences in place..
 
Attached the screen shot of my environment..
 
 
Much appreciated for quick response...
 
 
setup-3.png
Marianne's picture

I have moved your last post to a new discussion as it is not related to this thread.

New discussion: https://www-secure.symantec.com/connect/forums/i-am-not-able-resolve-netbackups-vmware-machines

Please post one question per discussion? If your issue in this post was resolved, please close this thread by marking the post that answered your question as solution. 

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

raju3235's picture

Thanks Marianne..

I've created exclude_list and provided the filesystems which are not needed and I am able to backup the host.

Regards,

Seshi