ADSM-L

Re: incremental blocked by inclexcl file

2003-08-19 19:46:33
Subject: Re: incremental blocked by inclexcl file
From: Steve Harris <Steve_Harris AT HEALTH.QLD.GOV DOT AU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 20 Aug 2003 09:45:57 +1000
Hi Richard,

If these files change so frequently, they will be backed up every day.
Thus the archive and backup cases converge to an expiry after a given number of 
days.

I'd suggest that you leave your directory excluded from backup, set up an 
appropriate management class for archive as necessary, and run an archive each 
day.

See also my post of yesterday about snapshots.  An AIX filesystem snapshot may 
be useful here.

HTH

Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia 


>>> rna AT FRONTIERNET DOT NET 20/08/2003 8:48:38 >>>
I am using TSM  Client Version 4, Release 2, Level 1.0 on an AIX system.
I have a directory (/s/sirsi/Unicorn) that contains 60 GB of data files,
the largest of which are frequently updated.  The application that updates
these files must be kept running with very little down time.

We have nightly incremental backups running via the scheduler.  They
usually start at about 22:00, but the actual start time varies, depending
on what other backups the server is performing.  In order to prevent
/s/sirsi/Unicorn from being backed up while the application is live, we
exclude the directory and its children in the inclexcl file.

I would like to write a script to be run from crontab that shuts down the
application, does an incremental backup, and then restarts the
application.  However, I find that because the directory is excluded in
the inclexcl file, the incremental job of course fails to backup anything.

So... Is there any way to override the inclexcl file temporarily while
manually doing an incremental command?  I can find no command line option
that would help.  And my attempts to create a custom user dsm.opt file
pointing to a different inclexcl file only resulted in an error:
ANS1036S Invalid option 'INCLEXCL' found in options file
'/s/sirsi/dsm.opt'

Any suggestions would be welcome.  Thank you.

Richard Anderson
Stanford University Libraries



***********************************************************************************
This email, including any attachments sent with it, is confidential and for the 
sole use of the intended recipients(s).  This confidentiality is not waived or 
lost, if you receive it and you are not the intended recipient(s), or if it is 
transmitted/received in error.

Any unauthorised use, alteration, disclosure, distribution or review of this 
email is prohibited.  It may be subject to a statutory duty of confidentiality 
if it relates to health service matters.

If you are not the intended recipients(s), or if you have received this e-mail 
in error, you are asked to immediately notify the sender by telephone or by 
return e-mail.  You should also delete this e-mail message and destroy any hard 
copies produced.
***********************************************************************************