Select the Oracle database

As per the instance chosen in the Oracle connection settings, Database name will be listed in the left side of the Add Oracle Database page. Select the database that need to be backed up as part of this schedule.

Step 3: Set Basic Configuration

Backup Type

Vembu OnlineBackup provides 2 types of Backup options.

1. Seed Backup – With this option you can seed backup to local drive which you can migrate to the Vembu Cloud using USB/External Hard drives to avoid more network bandwidth. It can be done only with the initial Full backup and incremental backup will not be continued.

2. Vembu Cloud – With this option you can directly backup the data into the Vembu Cloud over the Internet.

Test connectivity - Before you proceed with the backup, you can check the connectivity to Backup Server (Vembu Cloud). It will check the Connectivity and DNS Lookup with the Vembu Cloud.

Step 4: Full Backup Scheduling (Timings)

This step allows you to configure the frequency at which a full backup of the Microsoft Outlook has to be done. A full backup is a complete backup of the Microsoft Outlook folders. Since full backups take more time to complete than an incremental backup, a full backup is typically configured to run weekly or monthly or much less frequently than the incremental backup. Configuring a full backup schedule is mandatory, i.e. this step cannot be skipped. Vembu OnlineBackup will do a full backup dump of the Microsoft Outlook whenever the full backup is scheduled and back it up.

Vembu OnlineBackup | Admin User Guide | Oracle backup and Restore 162 This step has the following options from which any one can be chosen.

Run Every Few Minutes

Choose the hours/minutes interval between each time Vembu OnlineBackup must run. If Vembu OnlineBackup is restarted in the interim, the backup will run once the Vembu OnlineBackup starts. Thereafter, Vembu OnlineBackup automatically reschedules the next backup after the period you’ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, Vembu OnlineBackup will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, Vembu OnlineBackup is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am. Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days.

Run Daily

Choose the time at which the backup should run daily. This will execute the backup everyday at a time you have provided. Vembu OnlineBackup will run at the stipulated time only.

Run Weekly

Choose the time and the day of the week the backup should run. Vembu OnlineBackup will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Vembu OnlineBackup will run at the stipulated time/day only.

Step 5: Differential Backup Scheduling (Optional)

Configuring this step is optional. Vembu OnlineBackup will do a differential backup dump of the database with respect to the previous full backup whenever this differential backup is

scheduled.

This step has the following options from which any one can be chosen.

Run Weekly - Choose the time and the day of the week the backup should run. Vembu

Vembu OnlineBackup | Admin User Guide | Oracle backup and Restore 163 that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you’ve selected the “Run this Backup each time Vembu OnlineBackup

restarts” option in Advanced Options, Vembu OnlineBackup will run at the stipulated time/day only.

Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. Unless you’ve selected the “Run this Backup each time Vembu OnlineBackup restarts” option in Advanced Options, Vembu OnlineBackup will run at the stipulated time only.

Advanced Settings (Optional)

If you want to configure some additional advanced options - like, CPU utilization, etc. click on the Advanced Options button.

Advanced Backup Schedule Settings

1. Maximum Number Of Full Backups : You can specify the maximum number of full

backups that need to be stored in the server. For example if you configured a monthly full backup, then Vembu OnlineBackup will take a full backup every month. After 6 months you will have 6 separate full backups in the backup server along with differential and transaction logs under each of the 6 full backups. If your policy is to retain only backup data for 6 months, then you can configure "Store maximum of 6 full backups" here. On the 7th month, Vembu OnlineBackup, after finishing the 7th full backup, will delete the first full backup along with its differential and transaction log backups thus retaining always the last 6 month backups.

2. Read and verify the integrity of the backup on completion : If you enable this option, then SQL Server will perform a verification of the backup once it completes.

3. Run this backup immediately after saving this configuration (thereafter, Backups will be scheduled as per the schedule stipulated) : If you enable this option, then this backup schedule will be executed once immediately after you save this backup schedule – even if its not yet ‘time’ as per the schedule. For example if you configure a daily backup at 10.00 AM but you configured the backup at 8.00 AM, then the backup schedule will be run once immediately (8.00 AM) and then as per schedule (eg. daily at 10.00 AM).

4. Attempt to run this backup every 5 minutes in case of non completion because of a problem (Network error etc.) : If enabled, the user can choose to reschedule this

backup every 5/10/15/20/25/30 minutes, whenever an attempted backup is incomplete because of a network error, server crash etc. The number of times the backup will be rescheduled (due to an error) can be configured to be in between 1-5 or unlimited, with the default setting as 5. This is to ensure that an incomplete backup is completed as soon as possible without waiting for the next actual schedule time. Note that this option is enabled by default.

5. Data Integrity Check : Vembu OnlineBackup supports data integrity check where the data sent from the client machine is verified for integrity at the backup server. When a

Vembu OnlineBackup | Admin User Guide | Oracle backup and Restore 164 file's integrity check fails, Vembu OnlineBackup flags that file as skipped and the file is then again backed up during the next backup schedule.

Saving the configured backup

Once the Oracle database to be backed up are chosen and the configuration options are set, you simply need to click on the "Configure/Save Backup” button to activate the backup as per the schedule- on to the configured backup servers.

Temporary Dump Path Details

Temporary dump files will be stored in the name

<Temporary_Dump_Location>\<Backup_Name>\<Machine_Name>\<Database_Name>\<File_ Name>.BS

Vembu OnlineBackup | Admin User Guide | Oracle backup and Restore 165

Troubleshooting Tips

Error: Oracle RMAN Hot Backup could not be done on Oracle in NON-ARCHIVE Log mode. Please change DB Log Mode to ARCHIVE Log mode And then Schedule Additional Full Backup to fix this issue..

Cause: This error occurs when Vembu OnlineBackup performs backup on Oracle database which is running under "NON-ARCHIVE" log mode.

Solution: To resolve this issue, Oracle database should be brought to "ARCHIVE" log mode. Run the following script to bring Oracle database to "ARCHIVE" log mode.

SET ORACLE_SID = <SID> RMAN TARGET /

RMAN> SHUTDOWN IMMEDIATE; RMAN>STARTUP MOUNT;

RMAN> SQL "alter database archivelog"; RMAN> ALTER DATABASE OPEN;

Limitations

 Mapped drive cannot be given as temporary dump location for Oracle backup.

 If the local dump location is configured as a FAT32 disk partition, then the local dump file size should not exceed 4 GB as the FAT32 file system cannot hold file size more than 4 GB. In this case, Vembu OnlineBackup cannot dump the data files and the backup schedule will fail.

Vembu OnlineBackup | Admin User Guide | Oracle backup and Restore 166

Restore Oracle Database

You can restore the backed up Oracle databases using your most recent backup version or using an earlier backed up version. This section gives information on how to restore Oracle database using Vembu OnlineBackup.Follow the instructions detailed below.

1. Follow the steps for a regular restore operation and restore the required Oracle database backup files [ in which Oracle dump was made while Oracle backup was in progress ]. 2. Follow the Oracle restore steps below to restore the files contents to Oracle database. Before restoring the Oracle database, Database ID of Oracle database should be known. Database ID can be identified in restored control files.

1. Open the command prompt and set Oracle SID(system identifier) of the database that

you are going to restore.

For Windows: set ORACLE_SID = SID_NAME (Replace this SID_NAME with your Oracle

SID name)

For Linux: export ORACLE_SID = SIDNAME

2. Open Recovery Manager(RMAN) and Connect target database by running the

following command: RMAN TARGET /

3. Shutdown the Oracle database.

RMAN> SHUTDOWN IMMEDIATE;

4. Start the database instance without mounting Oracle database and restore the control file

RMAN>STARTUP NOMOUNT

RMAN>RESTORE CONTROLFILE FROM 'CONTROL_FILE_PATH';

5. Mount the database instance

RMAN>SQL "alter database mount";

6. Now restore the database by running the following command:

RMAN>RESTORE DATABASE;

7. After restoring the backed up datafiles from backup piece, Oracle should be recovered from the restored datafiles. Issue the following command to recover the database. RMAN>RECOVER DATABASE;

8. If RECOVER DATABASE fails with the error that archive log or redo logs are missing, then perform incomplete recovery upto the available archive or redo log sequence. RMAN>RECOVER DATABASE UNTIL LOGSEQ=FromLOGSEQ; [FromLOGSEQ should be log sequence number from where archive or redo logs are not available for restore.]

Limitations

 The backed up data has to be restored from the backup server to the Oracle dump location in the client machine from where it was backed up. Since RMAN can only recognize the files available in the dump location (which is the location to which RMAN dumped the files in the client), it is very critical that data is restored back into the same dump location while restoring the Oracle Databases.

Vembu OnlineBackup | Admin User Guide | PostgreSQL Database Backup and Restore 167