Novell Doc: OES 1 - Managing Move or Split Volume Jobs

20.15 Managing Move or Split Volume Jobs

Use the Distributed File Services>Volume Job Control page to monitor and manage the jobs. This page allows you to monitor the status of all the active jobs and recently completed jobs that were initiated for a selected server. You can pause, resume, reschedule, finish, or delete a job, depending on the state it is in.

NOTE:Configure and initiate Move Volume jobs and Split Volumes jobs from the Storage>Volumes page in iManager.

20.15.1 Monitoring the Status of Move or Split Volume Jobs

The Volume Job Control Status Report shows the following information:

Type: Distinguishes the job as a Move job or Split job .
Name: If it is a Move, this is the name of the original volume, such as DATA1:. If it is a Split, this is the path to directory on the original volume where you split it, such as DATA2:project\dev.
State: States are defined in logical tasks so that the move or split job can start and stop at several points in the process and go back to repeat any subprocesses, as needed.

Possible states include the following:
- Scheduled
- Running
- Files Skipped (administrator action required)
- Failed
- Deleted
- Completed
Percent Complete: The estimated percentage of data to be copied from the original volume that has been copied to the new volume as of the instant the status report was created.

To update the status, click Move/Split Job Control in Roles and Tasks.
Comment: A comment you typed when you issued a Pause command.

To access a report of move and split jobs:

In iManager, click Storage>Move/Split Job Control.

For instructions, see Section 3.1.6, Accessing Roles and Tasks in iManager.
Select a server to manage.

For instructions, see Section 3.1.7, Selecting a Server to Manage.

A list of move and split jobs appears.
(Optional) Click the Sort arrow next to the column heading that you want to sort jobs by.
When you are done, click OK.

20.15.2 Pausing a Move or Split Job

Pause suspends one or more move or split jobs until you manually resume or delete them. Only four combined move or split jobs can be running on a given server at a time. The Volume Manager performs the jobs in the order they are scheduled. If four operations are in progress and you want to activate others that you decide are a higher priority, you can pause one or more of the active jobs, thus allowing the new job to run immediately.

You might want to pause a move or split job when users need access to the content in the original volume at times when the move and split jobs are normally running.

In iManager, open the Volume Job Control page to view a job status report.

For instructions, see Section 20.15.1, Monitoring the Status of Move or Split Volume Jobs.
Select the Job check box next to one or more active jobs that you want to pause.
Click Pause.
Type a comment to be displayed in the status report, such as the reason you are pausing the job.
Click OK.

After the page refreshes, the jobs report their status as Pausing or Paused. If you inadvertently selected some jobs that are not eligible to be rescheduled, iManager ignores the Pause command for those jobs. It applies only to those jobs that the command is valid for.

20.15.3 Resuming a Move or Split Job

Resume continues one or more paused move or split jobs so that they can continue from wherever they were in the move or split process when you paused them.

In iManager, open the Volume Job Control page to view a job status report.

For instructions, see Section 20.15.1, Monitoring the Status of Move or Split Volume Jobs.
Select the Job check box next to one or more paused jobs that you want to resume.
Click Resume.
Click OK.

After the page refreshes, the jobs report their status as Scheduled or Running, depending on when the job was originally scheduled to run. If you inadvertently selected some jobs that are not eligible to be rescheduled, iManager ignores the Resume command for those jobs. It applies only to those jobs that the command is valid for.

You cannot resume a completed, failed, or deleted job.

20.15.4 Rescheduling a Move or Split Job

Reschedule changes the date and time that the selected jobs should run. It applies the same date and time to all of the selected jobs.

IMPORTANT:You cannot reschedule a completed, failed, or deleted job.

In iManager, open the Volume Job Control page to view a job status report.

For instructions, see Section 20.15.1, Monitoring the Status of Move or Split Volume Jobs.
Select the Job check box next to one or more uncompleted jobs that you want to reschedule.
Click Reschedule.

This opens a Reschedule Jobs dialog box.
To set the new schedule:
- To start the job immediately, select Start Now.
- To start the job at a future date or time, specify the start date and time when you want the move or split job to begin.
Click OK.

After the page refreshes, the jobs report their status with the new schedule. If you inadvertently selected some jobs that are not eligible to be rescheduled, iManager ignores the Reschedule command for those jobs. It applies only to those jobs for which the command is valid.

20.15.5 Viewing Files Skipped by a Move or Split Job

If a move or split volume job reports a Files Skipped status, some files could not be moved because they were open at the time that DFS attempted to copy them.

To view a list of files:

To retrieve the Operation ID number of the move or split job, enter the following command at the server command prompt:
```
volmn status
```
NSS displays a list of the Move and Split jobs that are in progress or were initiated or run in the past seven days.
Find the move or split job of interest and make a note of its Operation ID (OpID) number.

For example, Move(Vol1) might have an Operation ID number of 104211375.
To display a list of the files skipped, enter the following at the server command prompt:
```
volmn list OpID
```
For example, enter
```
volmn list 104211375
```

20.15.6 Deleting a Move or Split Job

Delete cancels a selected job before it begins or up to a certain point in the move or split process. If the process is beyond a certain state, it returns an error message to prevent you from deleting the process.

If the deletion continues, it stops the job at the next convenient step in the process, but performs no cleanup. The destination volume exists and contains all files copied to it before you deleted the job. Deleted jobs appear in the status report for a week by default.

IMPORTANT:If deletion continues, the original data is still intact. There is no loss of service or need to copy data from the destination volume back to the original volume.

In iManager, open the Volume Job Control page to view a job status report.

For instructions, see Section 20.15.1, Monitoring the Status of Move or Split Volume Jobs.
Select the Job check box next to one or more scheduled or paused jobs that you want to cancel.
Click Delete.

After the page refreshes, the selected jobs report their status as Deleted. Some jobs might not allow themselves to be deleted, depending on how far into the move or split process they are when you click Delete.

If you inadvertently selected some jobs that are not eligible to be deleted, iManager ignores the Delete command for those jobs. It applies only to those jobs that the command is valid for. You cannot delete a completed, failed, or previously deleted job.

20.15.7 Finishing a Move or Split Job

Finish continues a move or split job that has reached a state that requires manual intervention to finish even though some files might remain behind.

In iManager, open the Job Control page to view a job status report.

For instructions, see Section 20.15.1, Monitoring the Status of Move or Split Volume Jobs.
Select the Job check box next to one or more jobs waiting for administrator intervention that you want to complete, acknowledging and understanding the exceptions noted.
Click Finish.

After the page refreshes, the selected jobs report their status as Scheduled, Running, or Complete, depending on how much work was left to do in the job.

If you inadvertently selected some jobs that are not eligible to be finished, iManager ignores the Finish command for those jobs. It applies only to those jobs for which the command is valid.