AWS Thinkbox Discussion Forums

Minimizing storage impact of archived jobs

Due to artists overusing “submit scene file with job,” our repo is out of storage.

If I archive the jobs, it appears these no longer needed scene files will be zipped and retained, but if I delete the jobs it appears I will no longer have the job info for analytics.

Is there a third way that keeps the jobs’ statistics but not the aux files? Can I set something akin to dev\null as the alternate archive location?

Deadline has a housecleaning event, on which you can have custom logic to delete what you do not need.

(sorry the article is a bit older and links are broken, but hopefully can put you on the right path)

Privacy | Site terms | Cookie preferences