public:module:oracle:running_backup_jobs
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
public:module:oracle:running_backup_jobs [2021/04/20 17:10] ronnie.chan created |
public:module:oracle:running_backup_jobs [2021/04/20 17:34] (current) ronnie.chan |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| ---- | ---- | ||
| - | ===== 7.1 Start a Manual Backup ===== | + | ===== 7.1. Start a Manual Backup ===== |
| ---- | ---- | ||
| Line 15: | Line 15: | ||
| 3. There are two (2) types of backup mode in an Oracle database backup set: | 3. There are two (2) types of backup mode in an Oracle database backup set: | ||
| - | * **Database** – this type of backup includes Tablespaces, Control and Init File, and Archived Log Files. To see the steps during a database backup job, please refer to Ch. 7.1 Overview on the Database Backup Process. | + | * **Database** – this type of backup includes Tablespaces, Control and Init File, and Archived Log Files. |
| - | * **Archived Log** – this type of backup is for archived log files. To see the steps during an archived log backup job, please refer to Ch. 7.2 Overview on the Archived Log Backup Process. | + | * **Archived Log** – this type of backup is for archived log files. |
| To modify the In-File Delta type, Destinations, or Run Retention Policy Settings before running a backup, click the show advanced option link. | To modify the In-File Delta type, Destinations, or Run Retention Policy Settings before running a backup, click the show advanced option link. | ||
| - | 4. Click Backup to start the backup job. | + | | {{public:module:oracle:image102.png?700}} | |
| - | 5. Backup job is completed successfully. | ||
| - | + | 4. Click Backup to start the backup job. | |
| - | 7.3 Configure Backup Schedule for Automated Backup | + | |
| - | 1. Click the Backup Sets icon on the CloudBacko Pro main interface. | + | | {{public:module:oracle:image100.png?700}} | |
| - | 2. Select the backup set that you would like to create a backup schedule for. | + | 5. Backup job is completed successfully. |
| - | 3. Go to the Backup Schedule tab. | + | | {{public:module:oracle:image105.png?700}} | |
| - | + | ||
| - | 4. To modify an existing schedule, click the backup schedule to be modified. Or click the Add button to add a new one. | + | |
| - | + | ||
| - | 5. In the New Backup Schedule window, configure the following settings: | + | |
| - | + | ||
| - | · Name – the name of the backup schedule | + | |
| - | + | ||
| - | · Backup set type – the type of backup mode (i.e. Database and Archived Log) | + | |
| - | + | ||
| - | · Type – the type of backup schedule. There are four (4) different types of backup schedule: Daily, Weekly, Monthly and Custom | + | |
| - | + | ||
| - | * Daily – the time of the day or interval in minutes/hours when the backup job will run | + | |
| - | + | ||
| - | * Weekly – the day of the week and the time of the day or interval in minutes/hours when the backup job will run | + | |
| + | ===== 7.2. Configure Backup Schedule for Automated Backup ===== | ||
| + | ---- | ||
| - | + | 1. Click the Backup Sets icon on the CloudBacko Pro main interface. | |
| - | + | {{public:module:oracle:image045.png}} | |
| - | + | 2. Select the backup set that you would like to create a backup schedule for. | |
| - | + | | {{public:module:oracle:image098.png?700}} | | |
| - | + | 3. Go to the Backup Schedule tab. | |
| - | + | | {{public:module:oracle:image111.png?700}} | | |
| - | + | 4. To modify an existing schedule, click the backup schedule to be modified. Or click the Add button to add a new one. | |
| - | + | 5. In the New Backup Schedule window, configure the following settings: | |
| - | + | | {{public:module:oracle:image113.png?700}} | | |
| - | + | * **Name** – the name of the backup schedule | |
| - | + | * **Backup set type** – the type of backup mode (i.e. Database and Archived Log) | |
| - | + | * **Type** – the type of backup schedule. There are four (4) different types of backup schedule: Daily, Weekly, Monthly and Custom | |
| - | + | <WRAP indent> | |
| - | + | * **Daily** – the time of the day or interval in minutes/hours when the backup job will run | |
| - | + | <WRAP indent> | |
| + | | {{public:module:oracle:image115.png?500}} | | ||
| + | </WRAP> | ||
| - | + | * **Weekly** – the day of the week and the time of the day or interval in minutes/hours when the backup job will run | |
| - | + | <WRAP indent> | |
| + | | {{public:module:oracle:image117.png?500}} | | ||
| + | </WRAP> | ||
| - | * Monthly – the day of the month and the time of that day which the backup job will run | + | * **Monthly** – the day of the month and the time of that day which the backup job will run |
| - | * Custom – a specific date and the time of that date when the backup job will run | + | <WRAP indent> |
| + | | {{public:module:oracle:image119.png?500}} | | ||
| + | </WRAP> | ||
| - | + | * **Custom** – a specific date and the time of that date when the backup job will run | |
| - | + | <WRAP indent> | |
| + | | {{public:module:oracle:image121.png}} | | ||
| + | </WRAP> | ||
| - | + | </WRAP> | |
| - | + | * **Start backup** – the start time of the backup job | |
| - | + | <WRAP indent> | |
| - | + | * **at** – this option will start a backup job at a __specific time__ | |
| - | + | * **every** – this option will start a backup job __in intervals of minutes or hours__ | |
| - | + | <WRAP indent> | |
| - | + | Here is an example of a backup set that has a periodic and normal backup schedule. | |
| - | + | Figure 1.1 – Periodic backup schedule runs every 4 hours from Monday – Friday during business hours for Archived Log backup | |
| - | + | | {{public:module:oracle:image127.png}} | | |
| - | + | Figure 1.2 – Normal backup schedule runs at 21:00 or 9:00 PM every Sunday during non-business hours for Database backup | |
| - | + | | {{public:module:oracle:image129.png}} | | |
| - | + | </WRAP> | |
| - | + | </WRAP> | |
| - | · Start backup – the start time of the backup job | + | * **Stop** – the stop time of the backup job. This only applies to schedules with start backup “at” and is not supported for periodic backup schedule (start backup “every”) |
| - | + | ||
| - | * at – this option will start a backup job at a specific time | + | |
| - | + | ||
| - | * every – this option will start a backup job in intervals of minutes or hours | + | |
| - | + | ||
| - | + | ||
| - | + | ||
| - | Here is an example of a backup set that has a periodic and normal backup schedule. | + | |
| - | + | ||
| - | Figure 1.1 | + | |
| - | + | ||
| - | + | ||
| - | Figure 1.2 | + | |
| - | + | ||
| - | Figure 1.1 – Periodic backup schedule runs every 4 hours from Monday – Friday during business hours for Archived Log backup | + | |
| - | + | ||
| - | Figure 1.2 – Normal backup schedule runs at 21:00 or 9:00 PM every Sunday during non-business hours for Database backup | + | |
| - | · Stop – the stop time of the backup job. This only applies to schedules with start backup “at” and is not supported for periodic backup schedule (start backup “every”) | + | <WRAP indent> |
| - | * until full backup completed – this option will stop a backup job once it is complete. This is the configured stop time of the backup job by default. | + | * **until full backup completed** – this option will stop a backup job once it is complete. This is the configured stop time of the backup job by default. |
| - | * after (defined no. of hrs.) – this option will stop a backup job after a certain number of hours regardless of whether the backup job has completed or not. This can range from 1 to 24 hrs. | + | * **after (defined no. of hrs.)** – this option will stop a backup job after a certain number of hours regardless of whether the backup job has completed or not. This can range from 1 to 24 hrs. |
| The number of hours must be enough to complete a backup of all files in the backup set. For small files in a backup, if the number of hours is not enough to back up all files, then the outstanding files will be backed up in the next backup job. However, if the backup set contains large files, this may result in partially backed up files. | The number of hours must be enough to complete a backup of all files in the backup set. For small files in a backup, if the number of hours is not enough to back up all files, then the outstanding files will be backed up in the next backup job. However, if the backup set contains large files, this may result in partially backed up files. | ||
| Line 151: | Line 128: | ||
| As a general rule, it is recommended to review this setting regularly as the data size on the backup machine may grow over time. | As a general rule, it is recommended to review this setting regularly as the data size on the backup machine may grow over time. | ||
| - | · Run Retention Policy after backup – if enabled, the CloudBacko Pro will run a retention policy job to remove files from the backup destination(s) which have exceeded the retention policy after performing a backup job | + | </WRAP> |
| + | |||
| + | * **Run Retention Policy after backup** – if enabled, the CloudBacko Pro will run a retention policy job to remove files from the backup destination(s) which have exceeded the retention policy after performing a backup job | ||
| 6. Before closing the Backup Schedule menu, click the Save button to apply the backup schedule settings. | 6. Before closing the Backup Schedule menu, click the Save button to apply the backup schedule settings. | ||
public/module/oracle/running_backup_jobs.1618909810.txt.gz · Last modified: 2021/04/20 17:10 by ronnie.chan
Page Tools
