Problem? with file expiration
1999-02-05 07:27:10
Hi ADSM-ers,
once again I can't see the obvious (or is it a bug with ADSM)?
There are inactive files on my server which don't seem to expire.
Here is an example:
Name Size Modified Created Backed Up Mgmt Class
archiv.pst 56,04MB 04.02.1999 10.12.1998 04.02.1999 Default
I archiv.pst 2,92MB 10.12.1998 10.12.1998 10.12.1998 Default
I archiv.pst 45,89MB 07.01.1999 10.12.1998 07.01.1999 Default
Line 1 is the active version, lines 2 and three are the inactive
versions.
My copygroup looks like:
Policy Domain Name: STANDARD
Policy Set Name: STANDARD
Mgmt Class Name: STANDARD
Copy Group Name: STANDARD
Copy Group Type: Backup
Versions Data Exists: No Limit
Versions Data Deleted: 1
Retain Extra Versions: 30
Retain Only Version: 60
Copy Mode: Modified
Copy Serialization: Shared Static
Copy Frequency: 0
Copy Destination: BACKUPPOOL
Last Update by (administrator): SYSA
Last Update Date/Time: 28.07.1998 13:17:07
I have run an expire inventory before. Today is the 5th of February so I
thought all inactive files
backed up more than 30 days ago should have been gone. So I wonder why
the inactive version
of the ARCHIV.PST backed up on 10.12.1998 (DD/MM/YYYY) is still
available.
I'm running ADSM/VM 2.1.0.19 and ADSM 3.1.0.6 for Windows NT.
Am I to tired or could this be a bug?
Kind regards
Thomas Rupp
Vorarlberger Illwerke AG
MAIL: thomas.rupp AT illwerke.co DOT at
TEL: ++43/5574/4991-251
FAX: ++43/5574/4991-820-8251
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- Problem? with file expiration,
Rupp Thomas (Illwerke) <=
|
|
|