Hi,

If you want to manage data with different retention times for one
back-up client, I would define 2 nodes on the ITSM server, one for each
dsm.sys entry. By doing so, the data backupped under one dsm.sys entry
will not get expired by the exclude of the other entry.

Regards,

Karel

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Carlson
Sent: woensdag 28 maart 2007 17:15
To: ADSM-L@VM.MARIST.EDU
Subject: Expiring Files that Have Been Exluded

We have a situation where we have two entries in our dsm.sys.  One of
the entries contains an inclexcl that excludes certain database
filesystems, though the exlclude is using exclude not exclude.fs.  The
other has no inclexcl, so that when the DB person runs their backup
script, the files are backed up.  He is using selelctive backup
statements.  We thought this all was working, until we noticed, because
we needed a restore, that we did not have as many backup versions as we
thought we should.  What we discovered, is that the backup using the
inclexcl list is expiring backups in those directory.filesystems even
though they are excluded.  Is this the way it works?  Would it work the
same way if we used exclude.fs instead?  the manual says that exclude.fs
and exclude.dir are dropped outright, but for exclude, and etc, it only
says the file is not backed up - it does not specify that the file will
be expired.

Thanks for any input you can provide.

P.S.  TSM 5.3.2.3 on AIX 5.2.8 with Sun Solaris client version 5.3.0.

--
Andy Carlson
------------------------------------------------------------------------
---
Gamecube:$150,PSO:$50,Broadband Adapter: $35, Hunters License:
$8.95/month, The feeling of seeing the red box with the item you want in
it:Priceless.

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request.

 

Atos Origin Nederland B.V. / Utrecht

KvK Utrecht 30132762

Reply via email to