Julie, I have many nodes like this. To clean them up I created a domain with all the same management class names; then I updated the copygroups to have the '1,0,0,0' set of parameters that keeps only the active set during expiration processing. I also set the destination to a dummy storagepool that has no space assigned. Remenber to activate the policyset.
When I want to cleanup a node I simply update the node to be in this domain. After expiration has run, I export what is left and the delete everything. If anyone needs something from these old nodes I just import the node. Hope this helps, -- -------------------------- Bill Colwell C. S. Draper Lab Cambridge, Ma. [EMAIL PROTECTED] -------------------------- In <[EMAIL PROTECTED]>, on 11/01/01 at 10:07 AM, Julie Phinney <[EMAIL PROTECTED]> said: >I have an old, no-longer-backing-up client, whose backups we need to keep >in case of a disaster. We don't need to keep all the inactive versions of >files, though. Since it doesn't connect to the ADSM server any more, I >don't know how to expire those inactive versions. >Does anyone know how I could do that? If I connected as that node, with >another machine? I wouldn't want to affect the current active files >though. >Thanks, >Julie
