Your exclude list should be in the NetBackup installation directory (typically /usr/openv/netbackup on UNIX/Linux) and named for the policy you’re using.
exclude_list.<POLICYNAME> e.g. if your policy were called something like SOLARISOS you’d name the exclude exclude_list.SOLARISOS.
It is a simple text file.
To exclude the files you got errors on you could do:
/etc/sysevent/sysevent_door
/etc/sysevent/devfsadm_event_channel/1
/etc/sysevent/devfsadm_event_channel/reg_door
/etc/sysevent/syseventconfd_event_channel/reg_door
/home/*
/net
/platform/sun4v/lib/libc_psr.so.1
/platform/sun4v/lib/sparcv9/libc_psr.so.1
/proc
/system/contract
/system/object
/tmp/.X11-unix/X0
Notes on above:
If everything in /etc/sysevent was a Door file you could just exclude /etc/sysevent rather than the 4 individual files.
Excluding /home/* says to exclude everything under the directory but to backup the directory name itself. That way on a restore it would make the mount point for you.
/net, /proc are sufficient (as opposed to /net/* and /proc/*) because these filesystems are pseudo filesystems created at boot so don’t need to be restored like /home to be mountpoints.
I’m not sure what the 3 filesystem types (lofs, objfs and ctfs) are. It appears NetBackup doesn’t understand those filesystem types but you might want to research them to be sure you know what they are and
whether they have anything that would be lost in a system crash. Excluding them makes sense as NetBackup apparently won’t back them up but you need to understand their use and importance for possible future system recovery.
From: Harpreet Singh Chana [mailto:HarpreetSingh.Chana AT sg.flextronics DOT com]
Sent: Friday, May 25, 2012 11:20 AM
To: Mark Glazerman; Lightner, Jeff; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Backup Selection on Windows 2008 MasterServerfor Unix Servers.
Dear All,
Appreciated for your prompt reply
If possible, as a example may I request to share your exclude list.
With Warm Regards
___________________________________
Harpreet Singh Chana
Sr. Administrator
2, Changi South Lane
Singapore 486123
Singapore
Number (D) +65-6876-9313
Number (M) +65-9186-0581
Number (F) +65-6876-9711
VoIP 6666-900-313
HarpreetSingh.Chana AT sg.flextronics DOT com
www.flextronics.com
___________________________________
We use the ALL_LOCAL_DRIVES as our backup selection on Solaris OS backups and then have exclude lists on each host to make sure we don’t back up any application
specific files (like oracle dbf, rdo and arc files) which will get backed up using other policies. As mentioned below, selecting the “cross mount points” check box can lead to HUGE backups being taken because it will attempt to backup data residing on NFS
shares etc… For example, we have our Data Domain appliances mounted as NFS shares on some of our Solaris servers. If we used the “Cross Mount Points” option each OS backup would attempt to backup 100+TB of compressed data residing on the Data Domain appliances.
This is obviously not required.
Mark Glazerman
Desk: 314-889-8282
Cell: 618-520-3401
P
please don't print this e-mail unless you really need to
Door files on Solaris, socket files on any flavor of UNIX/Linux, /proc and others are special files that can’t be backed up and don’t need to be as they are
created on the fly on the system on which they exist. To prevent your backup with exiting with a status 1 (which means generally successful) you could add the files complained about to your exclude list.
The autofs stuff is for NFS mounts. In addition to cross mount points you’d have to enable crossing NFS boundaries. Note that this generally is NOT necessary
or desirable because the files are typically backed up on the system that exported the NFS share. On the Solaris host if you do “df /home” it should show you which system the share was exported from and you should be able to verify whether that system is
being backed up separately.
You do NOT want to backup /net as it is shortcut to all visible shares whether they are used on the system or not so you might end up backing up data from multiple
other systems that a) is being backed up on those systems already and b) is not actually necessary for the running of the system you’re currently backing up. Here again I’d suggest adding /net at least to your exclude and /home if it is in fact being backed
up from the system that exports it to this one.
Dear All,
We have setting up a Master/Media server running on Windows 2008 (64 bit) server. Where I am trying to do a backup of Sun Solaris clients.
In the Standard Backup Policy. In the Policy attributes I am using “cross mount points” and in backup selection “/” i.e. I want to backup the whole root file system
But during the backup, I am not able to cover the whole root file system and it is keep skipping some of the files.
<<
5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/sysevent_door] is a door file. Skipping
5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/devfsadm_event_channel/1] is a door file. Skipping
5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/devfsadm_event_channel/reg_door] is a door file. Skipping
5/26/2012 4:16:44 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/etc/sysevent/syseventconfd_event_channel/reg_door] is a door file. Skipping
5/26/2012 4:17:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/home] is on file system type autofs. Skipping
5/26/2012 4:18:06 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/net] is on file system type autofs. Skipping
5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/platform/sun4v/lib/libc_psr.so.1] is on file system type lofs. Skipping
5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/platform/sun4v/lib/sparcv9/libc_psr.so.1] is on file system type lofs. Skipping
5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/proc] is on file system type PROC. Skipping
5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/system/contract] is on file system type ctfs. Skipping
5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/system/object] is on file system type objfs. Skipping
5/26/2012 4:18:54 PM - Info bpbrm(pid=6340) from client tsraux02-zh-bk: TRV - [/tmp/.X11-unix/X0] is a socket special file. Skipping
.
.
etc
>>
Please advise how I can do a clean backup for Unix Servers.
With Regards.
Harpreet Singh
Legal Disclaimer: The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not
the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message
Athena®,
Created for the Cause™
Making a Difference in the Fight Against Breast Cancer
How and Why I Should Support Bottled Water!
Do not relinquish your right to choose bottled water as a healthy alternative to beverages that contain sugar, calories, etc. Your support of bottled water will make a difference! Your
signatures count! Go to
http://www.bottledwatermatters.org/luv-bottledwater-iframe/dswaters and sign a petition to support your right to always choose bottled water. Help fight federal and state issues, such as bottle deposits (or taxes) and organizations that want to ban the
sale of bottled water. Support community curbside recycling programs. Support bottled water as a healthy way to maintain proper hydration. Our goal is 50,000 signatures. Share this petition with your friends and family today!
---------------------------------
CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information
is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.
----------------------------------
Legal Disclaimer: The information contained in this message may be privileged and confidential. It is intended to be read only by the individual or entity to whom it is addressed or by their designee. If the reader of this message is not
the intended recipient, you are on notice that any distribution of this message, in any form, is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete or destroy any copy of this message