Re: exclude.systemobject sysfiles question

That's pretty much the approach we are taking here for WAN based backups. (IE 
the OS is replaceable, the user data is not.) We also make sure we have 
Includes / Excludes setup to accommodate more of a user data backup in addition 
to setting compression to yes on the client.

Here's basically what our WAN Based backup client dsm.opt looks like as far as 
the Include/Exclude piece.

Hope this helps!

DOMAIN  ALL-LOCAL
SUBDIR  YES

INCLUDE.SYSTEMOBJECT ALL SYSTEM_OBJECTS

EXCLUDE "*:\WINNT\CSC\...\*"
EXCLUDE "*:\WINNT\REGISTRATION\*.CLB\...\*.CRMLOG"
EXCLUDE "*:\DOCUMENTS\...\INDEX.DAT"
EXCLUDE "*:\PAGEFILE.SYS"
EXCLUDE "*:\WINNT\SYSTEM32\DTCLOG\MSDTC.LOG"
EXCLUDE "*:\WINNT\NETLOGON.CHG"
EXCLUDE "*:\HIBERFIL.SYS"
EXCLUDE "*:\WINNT\SCHEDLGU.TXT"
EXCLUDE "*:\WINNT\DEBUG\*.*"
EXCLUDE "*:\...\EA DATA. SF"

* THE FOLLOWING EXCLUDE PARAMETER WILL PREVENT A REGISTRY BACKUP UNLESS
* THE INCLUDE *:\ADSM.SYS\...\* IS ALSO PRESENT
EXCLUDE "*:\...\SYSTEM32\CONFIG\...\*"

* THIS INCLUDE STATEMENT NEEDS TO REMAIN FOR BACKING UP THE SYSTEM STATE
INCLUDE *:\ADSM.SYS\...\*

EXCLUDE.DIR "*:\...\NTFRS\JET"
EXCLUDE.DIR "*:\...\NTDS"
EXCLUDE.DIR "*:\SYSTEM VOLUME INFORMATION"
EXCLUDE.DIR "*:\...\TEMPORARY INTERNET FILES"
EXCLUDE.DIR "*:\RECYCLED"
EXCLUDE.DIR "*:\RECYCLER"

*Excluded to minimize data transfer
EXCLUDE.DIR "C:\SOURCE"
EXCLUDE.DIR "C:\I386"
EXCLUDE.DIR "D:\APPS"
EXCLUDE.DIR "D:\IMGS"
EXCLUDE.DIR "D:\MIGRATE"
EXCLUDE.DIR "D:\MITSUPPORT"
EXCLUDE.DIR "D:\SMS"
EXCLUDE.DIR "D:\SMSPKG"
EXCLUDE.DIR "D:\SRVRIMGS"






-----Original Message-----
From: Alan Davenport [mailto:Alan.Davenport AT SELECTIVE DOT COM]
Sent: Friday, May 02, 2003 12:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: exclude.systemobject sysfiles question


Great information Charles, my reason for asking is that I have a server
being backed up over a WAN and the amount of data is making the backup
difficult if not impossible in the time allowed. Can I NOT back up the
SYSFILES portion of the system object? My thought is that in the event of a
total loss of a server, the OS and all service packs could be restored than
applications installed the application data restored. Is this sound
thinking?

-----Original Message-----
From: Hart, Charles [mailto:charles.hart AT MEDTRONIC DOT COM]
Sent: Friday, May 02, 2003 1:16 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: exclude.systemobject sysfiles question


SysObjects are the Win2K Reg DB's and System state.  Here's some info that a
IBM/Tivoli Rep passed along


The reason I asked about system objects is that this information is used to
size and set policy for Win2k servers.  System Objects are very large and
are backed up full every day and unless specified by TSM policy are kept
for as long as the rest of the data if you do not exclude them from the
backups.  To give you an idea of why this is important, on a new Win2k
server with no applications on it the system objects are 250 MB in size and
consist of 2,000 to 3,000 files and on larger systems they can be up to 1
GB in size and have several thousand files in them.  Most customers do not
restore system files that are more than a few days old, so best practice is
to keep 10 days or so and we can do this with TSM by excluding them from
the daily backups and including them to their own management class with a
10 day retention.  This saves a lot of space in tape and helps reduce the
TSM database size.  If you have a reason to keep them for 30 or 60 days you
can, but in my experience for most customers this is just a waste of space.
This is just one of the ways TSM's extensive policy based administration
can save money, time and administrative over head.  Once the policy change
is made, TSM manages them for you.




-----Original Message-----
From: Alan Davenport [mailto:Alan.Davenport AT SELECTIVE DOT COM]
Sent: Friday, May 02, 2003 11:46 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: exclude.systemobject sysfiles question


Hello all,


        I have a quick question on the behavior of EXCLUDE.SYSTEMOBJECT with
the SYSFILES sub-parameter. It is my understanding that if included in a
DSM.OPT file, just the operating system files like FORMAT.COM, XCOPY.EXE,
etc. will not be backed up on a daily basis. Is this correct? Additionally,
will these files EVER be backed up? i.e., will they never back up at all or
will they still back up if changed, as in a normal incremental backup? What
effect will this have on restores?

        Environment, TSM server 5.1.6.2 on OS390 with client level 5.1.5.15.

    Take care,
         Al

Alan Davenport
Senior Storage Administrator
Selective Insurance Co. of America
alan.davenport AT selective DOT com
(973) 948-1306