7 Backing Up File System Data

Overview of Scheduled Backups

Scheduled backups are the basis of your backup strategy. Your first task after setting up the administrative domain choosing and configuring a backup schedule that makes sense for your environment.

This section contains the following topics:

• Choosing a Backup Strategy

• Choosing a Backup Schedule

• Configuring a Backup Schedule

Overview of On-Demand Backups

Although scheduled backups are the basis of your backup strategy, you may also need to make one-time-only backups. On-demand backups are useful for supplementing your scheduled backups as well as testing whether the administrative domain is correctly configured.

The basic steps for creating on-demand backups are as follows:

1. Create datasets (if they are not already created).

   "Creating Dataset Files" explains how to create dataset files. Note that to create dataset files you must have the modify administrative domain's configuration right.

2. Log in to the administrative domain as an Oracle Secure Backup user with the rights to perform the backup and the UNIX/Linux or Windows account needed to access the data to be backed up.

   You need the perform backups as self right to perform unprivileged backups and perform backups as privileged user to perform privileged backups.

3. Create one or more backup requests.

   As explained in "Jobs and Requests", Oracle Secure Backup saves each backup request locally in your Web tool or obtool session until you send it to the scheduler. In this state, the backup is not eligible to run.

   "Creating an On-Demand Backup Request" explains how to create backup requests.

4. Optionally, review, delete, or add to the list of backup requests.

   "Displaying the Backup Now Page" shows the page in which you can display backup requests. "Removing a Backup Request" explains how to delete backup requests.

5. Send all queued backup requests to the Oracle Secure Backup scheduler.

   "Sending Backup Requests to the Scheduler" explains how to send backup requests to the scheduler. After requests are sent to the scheduler, they are jobs and are eligible to run.

About Dataset Files

When configuring your dataset files, it may be helpful to study the dataset files in the samples subdirectory of the Oracle Secure Backup home directory. The sample dataset files use the *.ds extension.

include host brhost2 {
    exclude name core
    exclude name *.bak
    exclude name *~ 

    include path /
    include path /usr
    include path /home
}

include host brhost3 {
    exclude name core
    exclude name *.bak
    exclude name *~

    include path /
    include path /usr
}

include host winhost1
include path "C:\Documents and Settings" {
  exclude name *.log
}

ob> mksched --dataset brhost2.ds --day saturday --time 08:00 brhost2.sch
ob> mksched --dataset brhost3.ds --day saturday --time 09:00 brhost3.sch
ob> mksched --dataset winhost1.ds --day saturday --time 10:00 winhost1.sch

ob> mksched --dataset brhost --day saturday --time 08:00 brhost.sch

include host brhost2
include host brhost3
include host brhost4
                                                                                       
include path /
include path /home

ob> mksched --dataset brhosts.ds --day saturday --time 08:00 brhosts.sch

Displaying the Datasets Page

In the Backup page, click Datasets to display the page shown in Figure 7-1. This page lists all dataset files and dataset directories. Dataset directories appear in the Path box with a forward slash as the last character in the name. You can perform all dataset configuration tasks in this page or in pages to which it provides links.

Figure 7-1 Datasets Page

Description of "Figure 7-1 Datasets Page"

Creating a Dataset File

To create a dataset file:

1. In the Datasets page, click the Add button to create a new dataset file.

   Note:

   When you create a new dataset file, the initial contents of the dataset are defined by a dataset template.

2. In the Dataset type list, select File or Directory.

   Like Windows and UNIX file systems, Oracle Secure Backup dataset files are organized in a naming tree. You can optionally create dataset directories to help you organize your data files.

   When you want Oracle Secure Backup to back up data, you identify the name of the dataset file that defines the data. If you give the name of a dataset directory, it is equivalent to naming all of the dataset files contained within the dataset directory tree.

   Note:

   Dataset directories can be nested up to 10 levels deep.

3. In the Name field, enter a name for the dataset file.

4. Update the dataset statements displayed in the template file to define your backup data. Refer to Oracle Secure Backup Reference for dataset syntax and examples of datasets.

5. Choose one of the following:

   • Click the Save button to accept your entries and return to the Datasets page.

   • Click Cancel to void the operation and move back one page.

   Oracle Secure Backup displays a message in the Status box if your dataset file has errors. See "Checking a Dataset File" for details on errors.

Checking a Dataset File

This section explains how to check a dataset file for errors. You can check a dataset file at any time during editing.

When you check a dataset file, you perform a syntactic check to ask the dataset parser if your use of the dataset language is correct.

To check a dataset file for errors:

1. In the Datasets page, select a dataset file name from the Path box.

   Note:

   You can only check a dataset file, not a dataset directory.

2. Click the Check Dataset button.

   If the dataset syntax has no errors, the Web tool displays a message verification.

   If the dataset syntax has an error, the Web tool displays a message indicating the error.

3. Fix any errors that appear and recheck the dataset syntax.

Editing a Dataset File

To edit parameters for an existing dataset file:

1. In the Datasets page, select the name of the dataset file from the Path box.

2. Click the Open button.

   The Web tool displays a page with details of the dataset file.

3. Make needed changes and select one of the following:

   • Press Save to accept your changes and return to the Datasets page. Oracle Secure Backup automatically checks the dataset file for errors.

   • Click Cancel to void the operation and move back one page.

Removing a Dataset File

To remove a dataset file or directory:

1. In the Datasets page, select the name of the dataset file or directory from the Path box.

2. Click the Remove button.

   The Web tool prompts you to confirm the removal of the dataset file or directory.

3. Click Yes to remove the dataset file or directory.

   The dataset file or directory is removed and you are returned to the Datasets page.

Renaming a Dataset

To rename a dataset file or directory:

1. In the Datasets page, select the name of the dataset file or directory from the Path box.

2. Click the Rename button.

   The Web tool prompts you for the new name.

3. In the Rename box, enter the new name for the dataset file or directory.

4. Click Yes to accept the new name.

   The dataset file or directory is renamed and you are returned to the Datasets page.

Displaying the Backup Windows Page

In the Backup page, click Backup Windows to display the page shown in Figure 7-2. In the central box, the Web tool displays any existing backup windows.

You can perform all backup window creation and configuration tasks in this page or in pages to which it provides links.

Figure 7-2 Backup Windows Page

Description of "Figure 7-2 Backup Windows Page"

Creating a Backup Window

To create a backup window:

1. From the Backup window, click Backup Windows.

2. Click the Add button to add a new backup window.

3. In the Type list, select a backup window type. Your choices are:

   • Day range

     If you select this option, proceed to the instructions in "Specifying a Day Range".

   • Date

     If you select this option, proceed to the instructions in "Specifying a Single Date".

Removing a Backup Window

To remove an existing backup window:

1. In the Backup Windows page, select the name of the backup window that you want to remove.

2. Click the Remove button.

   The Web tool prompts you to confirm the removal of the backup window.

3. Click Yes to remove the backup window.

About Backup Schedules

A backup schedule tells Oracle Secure Backup what data to back up and when. In the backup schedule you specify:

• Days of the week, month, quarter, or year on which you want to perform a backup job

• Time (on each day) that a backup is to begin

• Time (on each day) that a backup is to begin

• Name of a media family to use. Oracle Secure Backup uses the characteristics of volume sets eligible to use for the backup from the media family name

Displaying the Schedules Page

In the Backup page, click Schedules to display the page shown in Figure 7-3. In the central box, the Web tool displays any existing backup schedules. You can perform all backup schedule creation and configuration tasks in this page or in pages to which it provides links.

Figure 7-3 Backup Schedules Page

Description of "Figure 7-3 Backup Schedules Page"

Creating a Backup Schedule

To create a backup schedule:

1. In the Schedules page, click the Add button to open the New Schedules page.

2. In the Schedule box, enter a name for the schedule.

   The name you enter must start with an alphanumeric character. It can contain letters, numerals, dashes, underscores, or periods. The maximum character length of 127 characters. You cannot uses spaces in the name you enter.

3. In the Priority box, enter a priority number for the backup job. The default priority is 100.

   The priority for a job is a positive numeric value. The lower the value, the greater the importance assigned to the job by the scheduler. The scheduler gives preference to dispatching more important jobs over those having lesser importance.

4. In the Datasets box, select one or more dataset files or directories that you want to include in the backup job.

5. In the Restrictions box, optionally select a restriction. You can restrict scheduled backups to specific devices. If you do not select a restriction (default), then the backups defined by the schedule can use any available device on any media server, at the discretion of the Oracle Secure Backup scheduling system.

6. In the Comments box, optionally enter any information that want to store with the backup schedule.

7. Click Apply, OK, or Cancel.

Editing a Backup Schedule

To edit properties for an existing backup schedule:

1. In the Schedules page, click the Edit button.

   The Web tool displays a page with details of the backup schedule.

2. Make changes to the schedule properties.

3. Choose one of the following:

   • Click Apply, OK, or Cancel.

   • Click Triggers to define triggers for a backup schedule.

     A trigger is a calendar-based time at which a scheduled backup becomes eligible to run. Without at least one trigger, a backup you have scheduled will never run. See "Configuring Triggers" for more information.

Removing a Backup Schedule

To remove an existing backup schedule:

1. From the Backup menu, click Schedules in the submenu under Settings.

2. Select the name of the backup schedule that you want to remove from the Schedule name box.

3. Click the Remove button.

   A message appears prompting you to confirm the removal of the schedule.

4. Click Yes to remove the backup schedule.

   You are returned to Schedules page and the message "Success: name removed" appears in the Status box.

Renaming a Backup Schedule

To rename a backup schedule:

1. From the Backup menu, click Schedules in the submenu under Settings.

2. Select the name of the backup schedule that you want to rename from the Schedule name box.

3. Click the Rename button.

   A message appears prompting you to enter the new name.

4. Enter a new name for the backup schedule.

5. Click Yes to accept the new name.

   You are returned to Schedules page and a message appears in Status box telling you that the schedule was successfully renamed.

Viewing Schedule Properties

To view schedule properties:

1. From the Backup menu, click Schedules in the submenu under Settings.

2. Select the name of the schedule from which you want to view properties from the Schedule name box.

3. Click the Edit button.

   The Web tool displays a page with the properties for the schedule name you selected.

4. Click Triggers.

   The Triggers page appears.

5. Select the trigger that you want to view and click Preview.

About Triggers

A trigger is a calendar-based time at which a scheduled backup becomes eligible to run. For example, you can specify that a backup is eligible to run on the first and third Sunday of the month. You can add multiple triggers to a backup schedule. Without at least one trigger, a backup you have scheduled will never run.

Creating a Trigger

To create a trigger:

1. In the Schedules page, select the schedule for which you want to create a trigger and click the Edit button.

2. Click the Triggers button.

   The Web tool displays the Triggers page.

3. In the Trigger type box, select a time representation you want to use to define when to perform the backup job. Your choices are the following:

   • One time

     Select this option to perform a backup only once. If you select this option, see "Creating a One-Time Backup Trigger" to continue.

   • Day (default)

     Select this option to perform a backup one or more days during the week. If you select this option, proceed to the instructions in "Creating a Daily Backup Trigger".

   • Month

     Select this option to perform a backup one day every month. If you select this option, proceed to the instructions in "Creating a Monthly Backup Trigger".

   • Quarter

     Select this option to perform a backup one day every quarter. If you select this option, proceed to the instructions in "Creating a Quarterly Backup Trigger".

   • Year

     Select this option to perform a backup one day during the year. If you select this option, proceed to the instructions in "Creating a Yearly Backup Trigger".

Editing a Trigger

To edit a trigger:

1. In the Schedules page, select the schedule for which you want to edit a trigger and click the Edit button.

2. Click the Triggers button.

   The Web tool displays the Triggers page.

3. Click the Edit button.

4. Make needed changes.

5. Click Apply or Cancel.

Removing a Trigger

To remove a trigger:

1. In the Schedules page, select the schedule for which you want to edit a trigger and click the Edit button.

2. Click the Triggers button.

   The Web tool displays the Triggers page.

3. In the central box, select the trigger to be removed.

4. Click Remove.

Displaying a Trigger Schedule

To display a trigger schedule:

1. In the Schedules page, select the schedule for which you want to edit a trigger and click the Edit button.

2. Click the Triggers button.

   The Web tool displays the Triggers page.

3. In the central box, select the trigger to be displayed.

4. Click the Preview button.

About On-Demand File System Backups

On-demand backups are ad hoc or one-time-only backups of the data in a dataset. For example, you can instruct Oracle Secure Backup to back up the Oracle home on client host brhost2. "Scheduled and On-Demand Backups" provides a conceptual overview of on-demand backups.

Displaying the Backup Now Page

In the Backup page, click Backup Now to display the page shown in Figure 7-4. In the central box, each backup request that you have created but not yet sent to the scheduler displays. Backup requests are identified by a backup name and number.

You can perform all on-demand backup creation and configuration tasks in this page or in pages to which it provides links.

Figure 7-4 Backup Now Page

Description of "Figure 7-4 Backup Now Page"

Creating an On-Demand Backup Request

To create an on-demand backup request:

1. In the Backup Now page, click the Add button to display the Options page.

2. In the Datasets box, select one or more dataset files or directories.

3. In the Backup date and Backup time boxes, select a future date and time for the backup to run. If you leave these fields unchanged, then Oracle Secure Backup considers your backup job as eligible to run immediately.

4. Using the Expire after box and list, optionally enter a time interval. For example, enter 3 and select days to specify a duration of 3 days. By default the expiration is disabled, which means that it will never expire. Refer to the duration placeholder description in Oracle Secure Backup Reference for more information.

   This option instructs Oracle Secure Backup to automatically expire this backup job if it has not started within the specified expiration period after the date and time intervals defined earlier in the Backup date and Backup time boxes.

5. Select a backup level from the Backup level box. Your choices are:

   • full (default)

     Select this option to back up all data in a dataset, regardless of when it was last backed up. This option is the same as backup level 0.

   • 1 to 9

     Select an integer value to back up only those files that have changed since the last backup at a lower numerical backup level.

   • incr

     Select this option to back up only data modified since the last backup, regardless of its backup level. This option is the same as backup level 10.

     Caution:

     Oracle Secure Backup does not support the incr backup level in conjunction with some platforms, including NAS devices. Notably, the incr option does not apply to Network Appliance filers.

   • offsite

     Select this option to specify a full (level 0) backup and instruct Oracle Secure Backup to keep a record of this backup so that it does not affect the full/incremental backup schedule. This option is useful when you want to create a backup image for offsite storage without disturbing your schedule of incremental backups.

6. In the Media family box, select a media family to which the date of this backup should be assigned. As explained in "Media Families", a media family is a named classification of backup volumes.

7. In the Restrictions box, optionally enter the names of devices to which backups controlled by this database backup storage selector are restricted. Restrictions come in the following forms:

   • device, which specifies a particular device

   • @hostname, which specifies any drive attached to the specified host

   • device@hostname, which specified any drive-host attachment

   If this option is left blank, then Oracle Secure Backup uses device polling to find any available device for use in backup and restore operations.

8. In the Priority box, optionally change the priority of the backup job. The default value is 100. The priority of a job is a positive integer value. The lower this value, the greater the priority assigned to the job by the scheduler. It considers priority 20 jobs, for example, more important than priority 100 jobs. The scheduler always gives preference to dispatching higher priority jobs over lower priority ones.

9. Choose whether you want the backup to operate in unprivileged or privileged mode (see "Privileged and Unprivileged Backups"). Unprivileged mode is the default.

10. Click OK or Cancel.

Removing a Backup Request

This section explains how to remove a backup request you have created, but have not yet sent to the scheduler.

To remove a backup request:

1. From the Backup menu, click Backup Now in the submenu under Operations.

   The Backup Now page appears.

2. Select a backup request from the Number/Dataset box in the central panel.

3. Click the Remove button.

   A message appears in the status area advising you of the Number of the backup removed.

Sending Backup Requests to the Scheduler

To send all pending backup requests to the scheduler:

1. In the Backup Now page, click the Go button

   The Web tool sends each backup request that appears in the central box to the Oracle Secure Backup scheduler.

   The Web tool displays a message in the status area for each request acknowledged by the scheduler. For example:

   backup request 1 (dataset datadir.ds) submitted; job id is admin/6.
   
   

   Oracle Secure Backup deletes each backup request upon its acceptance by the scheduler. As a result, the central box is empty upon completion of the Go operation.

2. See "Displaying Job Transcripts" to view the output for each job.