Hello all thanks in advance for your valuable tips! We are planning to introduce the archive feature within TSM on our new install base., and I have a few issues and concerns on how to protect in-accidental or deliberate use of this service.
Currently 90% of our client backups run via a central schedular with a only a few clients who run it via CRON (client initiated) We use * backupsets* feature as part of our service for long term audit and legal requirements only, Now we are planning to use the archive service for archiving source code or users (who have left the company) private info etc for medium term rentention. via the archive group feature, The question is, Is there any way we can control this from the server The reason being, once we open this feature. The moment we assign scratch tapes to the archive copy group on the domains we want to open this feature. There is no way one can stop a sys-admin who has super user rights to run a *dsm arc* command on a file-system at his discretion. my uderstanding, there is no way I can stop a client which was doing an incremental backup send its data to the *archive* copy group or I have it wrong many thanks Chetan
