Managing Network Space

[phyllisr]

Have any of you created a successful policy or procedure for managing content in the automatic Revit _backup and _log folders? We are adding *.000*.rfa to the search routine that removes other old junk (like *.bak) but for obvious reasons, we cannot add the TXT, RWS and DAT files to this routine. It is also not possible to write a "custom" routine to find all the folders (*_backup) and delete *.rws older than, say, 30 days. Same thing with the _log folder content and txt files. One project folder is already 1.22 GB and though I have manually cleaned things occasionally, it's not really practical for the long run when we have more than 10-12 projects. It is only April and our new 2006 projects now number beyond 197 - this does not count late 2005 numbers or suffixes added to 2003 and 2004 projects and other longer term projects that stay with us for 1-3 years. Or more.

Do you have one person on your team responsible for this? Who decides how far back to retain the files? What's the average time frame that you keep files for a possible rollback? Is a month too much or too little? Does anyone keep everything forever (except at closeout, of course)? If you have a policy or procedure, is it successful? Did any early users (particularly those who came from ADT) notice increased demand on server space because of the backup and log files? (I understand all the misconceptions about file size in general - that's not the question. We also keep user copies on the local drive so that's not an issue either.)

Thanks in advance.

[truevis]

...We are adding *.000*.rfa to the search routine that removes other old junk (like *.bak) but for obvious reasons....
*.0???.r?? may be more effective as a wildcard search for old Revit files.

[pdavis]

We are using robocopy to find and move those files so that they can be deleted.