ADSM-L

[ADSM-L] File expiration in schedule log

2016-01-20 13:13:28
Subject: [ADSM-L] File expiration in schedule log
From: "Vandeventer, Harold [OITS]" <Harold.Vandeventer AT KS DOT GOV>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 20 Jan 2016 18:11:33 +0000
I've never had to deal much with the client schedule log.

But, do the statements below (from dsmsched.log) mean that a file was marked to 
be expired, and that a subsequent EXPIRE INVENTORY on the TSM server would have 
removed the file?

01/19/2016 19:23:14 Expiring-->            5,898,240 
\\<nodename>\d$\<path>\<filename> [Sent]
.... Several log lines
01/19/2016 19:23:14 Retry #1 Expiring-->            5,898,240 
\\<nodename>\d$\<path>\<filename> [Sent]


We have a default policy with a 30 day deleted files setting, but the fellow 
that owns the file claims he deleted it yesterday.

He's trying to restore and doesn't see the file in the list of available for 
recovery.

Thanks...

------------------------------------------------------------
Harold Vandeventer
Office of Information Technology Services
(785) 296-0631
Harold.Vandeventer AT ks DOT gov<mailto:Harold.Vandeventer AT ks DOT gov> | 
www.oits.ks.gov<http://www.oits.ks.gov>



CONFIDENTIALITY AND PRIVILEGE NOTICE
This email message including attachments, if any, is intended for the person or 
entity to which it is addressed and may contain confidential and/or privileged 
information. Any unauthorized review, use or disclosure is prohibited. If you 
are not the intended recipient, please contact the sender and destroy the 
original message, including all copies.


[Confidentiality notice:]
***********************************************************************
This e-mail message, including attachments, if any, is intended for the
person or entity to which it is addressed and may contain confidential
or privileged information.  Any unauthorized review, use, or disclosure
is prohibited.  If you are not the intended recipient, please contact
the sender and destroy the original message, including all copies,
Thank you.
***********************************************************************

<Prev in Thread] Current Thread [Next in Thread>