Scheduled jobs allow you to define automatic run periods and blackout periods for the following file system jobs:
◆ Migrate
◆ Purge
◆ Delete Old Files
◆ Prune
For each managed file system, you can create one Migrate job and one Purge job. You can also create one Delete Old Files job and one Prune job for each of the file system’s back-end systems.
Table 27 on page 92compares each job before and after a scheduled job is created for it.
Table 27 Scheduled job comparison
Job type Without a scheduled job With a scheduled job Migrate Runs automatically. Checks for migration
candidates on the interval defined by the file system's Sleep Interval Until Next Migration setting.
Runs automatically during defined runtimes. Checks for migration candidates on the interval defined by the runtime element. Stops running during defined blackout times.
Purge Runs automatically. Checks for purge candidates on the interval defined by the file system’s Sleep Interval Until Next Purge setting.
Runs automatically during defined runtimes. Checks for purge candidates on the interval defined by the runtime element. Stops running during defined blackout times.
Delete Old Files
Must be run manually as described in“Periodic back-end system cleanup” on page 167.
Runs automatically during defined runtimes. Deletes orphaned files on the back-end system (as described in
“Delete Old Files job” on page 94) on the interval defined by the runtime element. Stops running during defined blackout times.
Prune Will not run. Runs automatically during defined runtimes. Only runs on the Level 1 back-end system, and only if the file system also has a Level 2 back-end system. Stops running during defined blackout times.
Files on the Level 1 back-end system are “pruned” (marked as deleted) when the number of days since their migration exceeds the number of days set in the expiration period.
Pruned files become available for removal by back-end system cleanup or Delete Old Files jobs.
File system data is not affected by pruning and files are not removed from the Level 2 back-end system.
A scheduled job consists of a standard file system job with an assigned schedule. The assigned schedule consists of the components described inTable 28 on page 93.
Effect on existing file system settings
A scheduled job can honor some file system settings and overrule others.
Which settings are honored and which are overruled depends on the type of job scheduled, as described inTable 29 on page 94.
Table 28 Components of a schedule Component Description
Name Descriptive label for the schedule. The Name value must be unique for each schedule created for a file system.
Description Information about the schedule's purpose.
Run Time Time periodaduring which the task is started regularly on the wake-up interval. More than one Run Time may be assigned to a schedule.
Note: Blackout times have priority over runtimes. Jobs do not run during time periods in which blackout time segments coincide with runtime segments.
Black Out Time Time period that the task cannot be run. More than one Black Out Time value may be assigned to a schedule.
a. Time periods are defined by the assigned time elements. Time elements are described in
“Creating a scheduled job” on page 96.
Delete Old Files job The Delete Old Files job removes files on a back-end system that have become orphaned because the files have been deleted from the file system. Those files are marked for deletion by FSM but are not automatically removed. Delete Old Files jobs have the same effect as the manual maintenance procedures described in“Periodic back-end system cleanup” on page 167.
If a file system has two back-end systems, the Delete Old Files job only runs for the back-end system that is selected. The behavior of a scheduled Delete Old Files job changes depending on the type of back-end target. The differences are described inTable 30 on page 95.
Table 29 Effect of a scheduled job on file system settings Job type Honored settings Overruled settings Effect Migrate • Delay Until Migrate
Candidacy
• Minimum File Size to Migrate
• Extended Rules
Sleep Interval Until Next Migration
Once a migrate job is scheduled, migration of eligible files is only started during the job's runtimes. No files are migrated during the job's blackout times.
During runtimes the eligibility logic specified by the file system settings is applied.
Extended rules are only applied during scheduled runtimes.
Purge • Delay Until Purge Candidacy
• Minimum File Size to Purge
• Concurrent Files Purged
• File Stub Size
• High Watermark
• Low Watermark
• Concurrent Files Migrated
• Extended Rules
• Sleep Interval Until Next Purge
• Purge After Migrate
Once a purge job is scheduled, purge of eligible files is only started during the job's runtimes. No files are purged during the job's blackout times.
A scheduled purge job can also overrule an enabled Purge After Migrate setting by preventing the immediate purging of files that are migrated during the purge job's blackout times.
During runtimes the eligibility logic specified by the file system settings is applied.
Extended rules are only applied during scheduled runtimes.
Delete Old Files Concurrent Files Destroyed None None
Prune None None None
Prune job The Prune job removes files from a Level 1 back-end system after a set number of days (expiration period). This clears the Level 1 back-end system of older files, but the availability of all files is not affected. When files that have been pruned are needed they are retrieved from the Level 2 back-end system.
Prune jobs have the following characteristics:
◆ Run only on Level 1 back-end systems
◆ Run only when the file system has both Level 1 and Level 2 back-end systems
◆ Cannot be run manually
◆ Files must be migrated before they are eligible for pruning
◆ Files do not need to be purged to be eligible for pruning
Table 30 Delete Old Files job differences Module type Description
Centera The Delete Old Files job applies to all eligible file data from all UTDM file systems that share the same virtual pool on an EMC Centera.
Note: To avoid performance issues on the EMC Centera, only schedule a Delete Old Files job on one UTDM file system in any virtual pool. Since the job runs for all UTDM file systems in the virtual pool, scheduling more than one job wastes resources on the EMC Centera.
FTP The Delete Old Files job is not available for an FTP module back-end system. This task must be performed on the back-end host.“Periodic back-end system cleanup” on page 167describes how to do this.
NFS The Delete Old Files job applies to the selected file system only.