Carefull implementation and coordination with TSM retention policy changes could overcome this issue. You could set VDE/VDD to 3 and REV/ROV to no limit (or some acceptable value) for the stub files.
If the access time to the files can be minutes or hours, you might be better served by a database referencing archives. This could reduce dependency on OS/filesystem upgrades messing up the HSM and provides a small level of futureproofing your system. Cheers, Neil -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Allen S. Rout Sent: Friday, July 13, 2007 3:43 PM To: [email protected] Subject: Re: [ADSM-L] HSM for Windows >> On Fri, 13 Jul 2007 08:02:48 -0400, "Schaub, Steve" <[EMAIL PROTECTED]> said: > We're considering implementing HSM for Windows on some large (5TB+ > each) fileservers. Has anyone undertaken something similar, and care > to share any results? Any gotchas? Take a look back in the archives: the TSM product for windows which is called 'HSM' has many, very important characteristics in which it differs from what you may be thinking if you've ever dealt with a HSM product in the past. For very prominent example: When you've migrated your data, the stub will get backed up, which will push the full version of the file to inactive status, so it'll disappear from your backups. My opinion is "Avoid, avoid, avoid." - Allen S. Rout IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
