Purge deleted editions and linked content by Back4 or custom task
Contents
There are two ways to purge deleted editions and linked content, each with pros and cons:
The Back4 cleanup process, runs at fixed intervals, specified in the Interval box. See Cleanup Process for details of how it works. Pros •It's available by default. •It follows the expiration rules. Cons •You cannot specify the absolute time of purge - and probably you don't want to do the purge during production hours. •Cleanup process needs to run pretty frequently - to get rid of the expired logins. Such frequency is potentially unsuitable for purge, but it's not possible to specify separate intervals for different types of purge. Notes As it is not possible to make the Cleanup process run the purge only out of production hours, you may prefer to use a custom scheduled task to purge content. If it is so, have in mind that Cleanup process must remain enabled, as it needs to clean expired logins. You need to set the Purge days value in the Configure Back4 scheduled purging and deleting to be higher of all parameters of the custom scheduled task, to avoid purging also by Cleanup process. |
1.On a GN4 server, create a batch command file with a following command; (change highlighted values): srv4 cleanup -purge 2.06:00 2.In Windows, create a scheduled task that runs every day at a time at your choice and executes the above batch file. The above purges all content that is deleted longer than 2 days and 6 hours. Pros You can specify Notes about Cleanup process •The Cleanup process must remain enabled, as it needs to clean expired logins. You need to set the Purge days value in the Configure Back4 scheduled purging and deleting to be higher of all parameters of the custom scheduled task, to avoid purging also by Cleanup process. •Assign an expiration rule only to partitions that group wire folders and to no other folder. That's because the Cleanup process would purge as well all folders with expiration rule, and you don't want this to happen, as all content purge would be driven by the custom scheduled task. See also |