This has been one of my gripes for a while. The main problem with this is the vocabulary that the client uses. A TSM client just "deactivates" a file, it doesn't expire anything despite what the client log says. The Server expiration process will then analyze the inactive files and decide what to do with it (i.e. delete or keep it) according to the management class. Depending on your management class settings, it is possible that the Server expiration will decide to keep the inactive file around for a long time. The server expiration process ignores any active files.
Regards, Shawn ________________________________________________ Shawn Drew Internet [email protected] Sent by: [email protected] 10/20/2011 09:00 AM Please respond to [email protected] To ADSM-L cc Subject [ADSM-L] expiration As a client performs a backup it expires files and this is evident in the logs. Later the expiration inventory process runs on the server. Are the files just marked for expiration by the client and the expiration process actually updates the database. If I have a client that I need to not run a backup on for specific DR reasons since it is missing some files. I don't want the backup to mark those as expired and thus actually expired as part of the inventory process Thus if I run the full expire inventory process on the server and not the client backup the missing files on the server wont expire and will remain active. Hope I explained the situation right. Thanks, Tim Brown Systems Specialist - Project Leader Central Hudson Gas & Electric 284 South Ave Poughkeepsie, NY 12601 Email: [email protected] <<mailto:[email protected]>> Phone: 845-486-5643 Fax: 845-486-5921 Cell: 845-235-4255 This message contains confidential information and is only for the intended recipient. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, please notify the sender immediately by replying to this note and deleting all copies and attachments. This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. Please note that certain functions and services for BNP Paribas may be performed by BNP Paribas RCC, Inc.
