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
-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
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Carlson
Sent: Wednesday, March 28, 2007 10:15 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Expiring Files that Have Been Exluded
We have a situation where we have two entries in our dsm.sys. One
Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Carlson
Sent: Wednesday, March 28, 2007 10:15 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] 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
Along with what others have replied with, you can either use two different
node names, or have the DBA run Archives (and have an archive management
class on the server for the appropriate retention).
Two nodes is a little harder, as you have to make sure you invoke the
right node name, both on
