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.
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu]
On Behalf Of Harpreet Singh Chana
Sent: Friday, May 25, 2012 4:31 AM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Backup Selection on Windows 2008 Master Server for Unix Servers.
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