HP BB118BV - StorageWorks Data Protector Express Package User's Manual & Technical Reference page 181

Using Run
You can "force" scheduled jobs to run prior to their scheduled time by selecting the job and clicking the
Run command from the Commands task pane. Alternatively, you can select the job from the job view,
right-click and select Run from the shortcut menu. You can also run the job from the Job Status view. Data
Protector Express will execute the job immediately.
NOTE:
Forcing a job that is scheduled for the same day marks the job as complete for that day. Data Protector
Express resets the job on the next day so it will run as scheduled. As a result, if you force a job to run on
the same day that it is scheduled to run, it only runs once on that day.
How forcing jobs to run affects job settings When you force a scheduled job to run before its scheduled
time, Data Protector Express does not automatically update certain settings on the Options and
Device/Media property pages of the job. Recall that when a scheduled job with an automatic rotation is
run, Data Protector Express updates the Backup mode, Write mode, New media location, New media
name and Media settings on the Options and Device/Media property pages of the job to reflect that job's
place in the rotation schedule. However, when a job is forced to run before its scheduled time, Data
Protector Express does not update these settings.
For example, suppose that a backup job is scheduled to run as an incremental job in the evening. If it is
forced to run before its scheduled time, Data Protector Express will not update the Backup Mode setting.
In this case, if the last time the job was run, it was as a full backup job, the Backup Mode setting on the
job's Option page will still be set to Full. As a result, when you force the job to run, it will be run as a full
backup job, even though it is next scheduled to run as an incremental job.
Forcing a job to run can be useful when a job failed to run for some reason. For example, suppose a full
backup job is scheduled for a Saturday, but a network equipment malfunction prevented the job from
being run as scheduled. It is important that another full backup job be run before the next incremental
job. This is the only way to ensure that the full data recovery period is not compromised. On Monday,
you can force the failed backup job to run again after the network connections are restored. Before you
run the job, open the job's property page and make sure the proper job type and media are selected.
Before forcing a scheduled job to run, you should always check the Options page of the job to see that
the option settings are set correctly. If you are forcing the job to run because an earlier job failed to run
properly, you can look at the log of the failed job to see which settings the job would have used.
How forcing jobs to run affects permissions When a job is run, Data Protector Express will check for the
appropriate permissions to the device, files, media, and so on. Data Protector Express calculates these
permissions by using the permissions of the user who scheduled the job. The Scheduled by field lists
the user who scheduled the job. The Run by field lists the user who forced the job to be run. After a
job is run, the job owner is reset to the last user who changed the job properties; forcing a job to
run does not permanently change the job owner.
When the Data Protector Express administrator creates and schedules a job, the owner of the job is the
administrator. Data Protector Express will use the Data Protector Express administrator's permissions when
running the job. Similarly, if another user creates and schedules a job, that user will be the job's owner
and Data Protector Express will calculate the job's permissions using that user's permissions.
However, if a scheduled job is forced to run, the person who forces the job to run becomes the job's new
owner. So, for example, if the Data Protector Express administrator forces a job to run that another user
has created, the Data Protector Express administrator becomes the job's new temporary owner and Data
Protector Express calculates the permissions using the Data Protector Express administrator's permissions.
Changing the job's owner can be useful for managing security. A user can create and schedule a job,
even though that user lacks the proper permissions to run that job. Another user, such as the Data
Protector Express administrator, can then force that job to run with their own permissions.
181
User's Guide and Technical Reference