For each job, ArkManager maintains information about its users centrally instead of storing duplicate information among the file versions. The user list grows cumulatively; it is not automatically synchronized to remove users from the list who no longer have associations with current file versions in the archive. To clear out obsolete user information, run the Clean Up Users task about once a month, depending on the job’s schedule, the job’s Delete policy, and the turnover of users in your workplace.
During the cleanup, jobs are in the Clean Up Users state. While Clean Up Users is running, the job itself does not run and the job’s Delete policy does not run. Afterwards, the jobs are automatically placed in the Stopped state and the jobs’ Delete policies are resumed.
If a cleanup job is interrupted, the job stops gracefully and enters the Stopped state. The user list might be only partially cleaned up. For example, the job is interrupted if you delete, edit, start, or schedule the job, or if you shut down or restart ArkManager. If you are editing a cleanup job, when you save your edits, the job continues in the Stopped state if you enabled the setting, or it enters the Scheduled state if you disabled the setting.
To clean up the user list:
In iManager, expand , then click .
Select the archive server you want to manage, then wait for the page to refresh.
For information, see Section 7.2, Configuring Archive Volume.
Select the tab.
In the Jobs report, select one or more jobs where you want to clean up the user list, then select .
Wait for the jobs to stop gracefully and report a Stopped status.
Select one or more jobs, then select .
When the cleanup for a job is complete, the job enters the Stopped state.
When cleanup is done, restart the stopped jobs.
For information, see Section 8.3, Starting or Scheduling a Job.