8.11 Salvaging a Deleted Job

You can salvage a deleted job to restore the job and to allow users to access its archived file versions. You can salvage only one job at a time. You cannot salvage a deleted job if the source volume it archived is currently the source volume for an existing job on the archive versioning server.

In iManager, expand Archive Versioning, then click Archive Jobs.
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 Deleted Jobs tab.
In the Deleted Jobs Report, select the Job check box next to the job you want to salvage, then click Salvage.

If multiple deleted jobs have the same job name, they are distinguishable by their deleted dates, source volumes, and source servers.
Specify a name for the salvaged job that is unique among the non-deleted jobs on the archive server.

Click OK.

Salvaging a deleted job restores the job. The following table describes the state of the job after it is salvaged, given the job’s state when it was deleted.

State of the Job When Deleted	Delete Action	State of the Job After Salvage
Running	The job stops gracefully, enters the Stopped state, then it is deleted. A partial data set exists for the job. The job’s Delete policy is suspended.	Scheduled The job’s next run time is calculated forward from the time the job is salvaged. The job’s Delete policy runs immediately.
Stopped	The job is deleted. The job’s Delete policy is suspended.	Stopped The job remains in the Stopped state until you start or schedule it. The job’s Delete policy runs immediately.
Scheduled	The job is deleted. The job’s Delete policy is suspended.	Scheduled The job’s next run time is calculated forward from the time the job is salvaged. The job’s Delete policy runs immediately.
Not Configured	The job is deleted. The job’s Delete policy, which does not run in the Not Configured state, continues to be suspended.	Not Configured The job cannot be started or scheduled until you provide valid settings. The job’s Delete policy does not run until you start or schedule the job.
Clean Up Users	The Clean Up Users job stops gracefully, enters the Stopped state, then it is deleted. The user list might be only partially cleaned up. The job’s Delete policy, which does not run in the Clean Up Users state, is now suspended.	Stopped The job remains in the Stopped state until you start or schedule it. The job’s Delete policy runs immediately.

State of the Job When Deleted

Delete Action

State of the Job After Salvage

Running

The job stops gracefully, enters the Stopped state, then it is deleted. A partial data set exists for the job.

The job’s Delete policy is suspended.

Scheduled

The job’s next run time is calculated forward from the time the job is salvaged.

The job’s Delete policy runs immediately.

Stopped

The job is deleted.

The job’s Delete policy is suspended.

Stopped

The job remains in the Stopped state until you start or schedule it.

The job’s Delete policy runs immediately.

Scheduled

The job is deleted.

The job’s Delete policy is suspended.

Scheduled

The job’s next run time is calculated forward from the time the job is salvaged.

The job’s Delete policy runs immediately.

Not Configured

The job is deleted.

The job’s Delete policy, which does not run in the Not Configured state, continues to be suspended.

Not Configured

The job cannot be started or scheduled until you provide valid settings.

The job’s Delete policy does not run until you start or schedule the job.

Clean Up Users

The Clean Up Users job stops gracefully, enters the Stopped state, then it is deleted. The user list might be only partially cleaned up.

The job’s Delete policy, which does not run in the Clean Up Users state, is now suspended.

Stopped

The job remains in the Stopped state until you start or schedule it.

The job’s Delete policy runs immediately.