RMAN Backup

Before running database backups, ensure that archive logging is enabled on the Oracle database. If archive logging is not enabled, perform the following steps on the database server:

1. Open a Command Prompt window.

2. Run the command SET ORACLlE_SID = <DB SID>.

3. Run the command sqlplus /nolog.

4. Run the command CONNECT SYS/<SYSPWD> AS SYSDBA.

5. Run the sql select log_mode from v$database;

   If the query returns ARCHIVELOG, archive logging is already enabled. You can perform the RMAN backup steps. If the query returns NOARCHIVELOG, then to enable archive logging, perform the following:

   1. Run the command Shutdown immediate.

   2. Run the command Startup mount.

   3. Run the command ALTER SYSTEM ARCHIVELOG;

   4. Run the command ALTER DATABASE OPEN;

   5. Run the sql select log_mode from v$database;

      ARCHIVELOG appears and confirms that the archive logging is enabled and the database is ready for backups.

After you configure RMAN, run the backup PowerShell scripts to perform the initial database backups.

6. Open the Powershell window.

7. Navigate to the <OracleBase>\db-backup.

8. Run the script RmanBackup.ps1, passing the following parameters

   OracleHome - The home of the Oracle database. For example, C:\app\oracledb\product\19.0.0\dbhome_1.

   OracleSid - The SID of the database that is backed up. For example AVEVA Enterprise Resource Management.

   SysPwd - The SYS password for database.

   SystemPwd - The SYSTEM password for database.

   SmtpServer - The SMTP server to send backup confirmation email.

   SmtpFrom - The user that the email is sent from.

   SmtpTo - The user that receives the emails. The list is email a comma delimited set of email addresses of the users.

   .\RmanBackup.ps1 -OracleHome C:\app\oracledb\product\19.0.0\dbhome_1
   -OracleSid ERM -SysPwd ERM -SystemPwd ERM -SmtpServer smtp.aveva.com
   -SmtpFrom ERMoracle@aveva.com -SmtpTo mark.booth@aveva.com

After completion, an email with verification that the backup is complete, is received, and the status of all the datafiles is reported. Ensure that the backup is completed successfully, and the attached logfile shows no errors.

Ensure that the backup path defined earlier now contains the following sub-folders:

• ARCHIVELOG

• AUTOBACKUP

• BACKUPSET

The folder contains system-generated files that form the RMAN backup set.

Note: Ensure that the entire backup directory is included in your regular IT backup policies. In a disaster recovery scenario, successful database restoration requires all files and directories within the backup path, along with the DBID recorded earlier. Without the information, database recovery is not possible.The responsibility for ensuring that the backup scripts run nightly and that restore operations are tested regularly lies with the customer. Regular recovery testing confirms that all required components are available to restore the database in a complete disaster recovery situation.

Once the backup process is completed, you can configure a scheduled job or use an existing internal backup mechanism to run the PowerShell script on a nightly basis.

Note: While multiple database backup approaches exist, taking full file‑level copies of Oracle database files while the database is open results in a corrupted backup set and cannot be used for recovery purposes.