Oracle Database Backup and Restore Guide

T-Bot
Published: 1 year ago
Share:

This guide describes the backup and recovery process and the steps necessary to restore the PowerSchool 12.x or later database server from a database datapump. For recoveries that require restoring the RMAN backups or restoring to a point-in-time.

Introduction

This guide describes the backup and recovery process and the steps necessary to restore the PowerSchool 12.x or later database server from a database datapump. For recoveries that require restoring the RMAN backups or restoring to a point-in-time, contact PowerSchool Technical Support.

This guide is intended for PowerSchool system administrators. To use this guide, you must be familiar with Windows Server 2012 R2 or Windows 2016 and the Oracle database. You must also have PowerSchool 12.x or later installed and operating correctly.

Please refer to the appropriate section for step-by-step instructions.

Important Note: If your district uses Unified Classroom, do not use the Restore and Recovery process listed in this guide. Contact PowerSchool Technical Support for specific instructions.

Terminology

The following table describes the terminology used in this document.

Oracle Database Backup and Restore Guide

TermDefinition
Flashback

The PowerSchool SIS database no longer supports Flashback, but certain Oracle functions such as datapump exports still utilize it.

Flashback is an optional feature of an Oracle database that is enabled by default with the installation. Flashback is dependent on the amount of undo data in the system. The undo data is what keeps track of the changes made to the Oracle database. It recognizes which Oracle redo logs, archive files, or backup sets hold the data for any given point in time within the flashback retention period. The datapump export uses Flashback to maintain table consistency and is set to a default retention period of 24 hours.

Full Backup

An operation that backs up all RMAN database files. Files are backed up whether they have changed since the last backup. Also known as a Level 0 RMAN backup.

Note: Archivelogs are included in the backup and are deleted each time a backupset is created.

Incremental BackupAn operation that backs up only the database files that have changed since a previous backup. Oracle supports nine different incremental backup levels for file system backups. A differential incremental backup copies data that changed since an incremental backup at the same or lower level. Incremental backups are also referred to as Level 1 RMAN backups.

 

Oracle Database Backup and Restore Guide

TermDefinition
Retention PolicyThe length of time that data in one or more backupsets (a set being a full backup and all of its subsequent incremental backups) is not eligible to be overwritten. Data can be restored to a point in time between the current time moving backward bound by the retention policy window (for example, the current date subtracts retention policy days).
Fast Recovery AreaAn Oracle-managed directory that provides a centralized storage location for backup and recovery files. Archivelogs and backupsets are maintained in this directory. These files are used when restoring during media recovery and referenced in the RMAN backup process.

 

Oracle Database Backup and Restore Guide Understanding Oracle Backup and Recovery

This section provides a simplified overview of Oracle processes. Many technical details are not included to keep the overview simplified.

Oracle 12c Migration Prerequisites

If you have not already done so, run the Configure PowerSchool Backup Jobs process via the PowerSchool Installer Start Page link. The backup script must be in place before you start the Oracle upgrade process.

If you plan to backup and export your existing Oracle data before the upgrade, you must run the Configure PowerSchool Backup Jobs process via the link on the PowerSchool Installer Start Page to have RMAN backups enabled.

Backup jobs must be installed AND enabled. Backups

When you make a change in PowerSchool, modifying or creating data, the change is written to the Oracle database. Oracle records the change to the database data file and then writes the change to the redo log. Redo logs are also known as online logs or online redo logs.

Writing changes to both the data file and the redo log ensures that every change made to the database is immediately backed up.

Redo logs make it possible to undo changes made to the database and make it possible to restore the database in case of data loss due to hardware failure or user error.

This is a simple overview of the core concept of backup and recovery in an Oracle database. Oracle records and backs up every change to the database almost immediately.

There are five redo logs configured in the installation of Oracle with PowerSchool. Oracle writes to each of them one at a time. When the current redo log reaches 512 megabytes in size, Oracle stops writing to it and starts writing to the next redo log. When Oracle changes to a new redo log, the previous redo log is backed up to an archivelog so the previous redo log can be reused. Oracle cycles through the five redo logs, continuously reusing them and backing them up over and over. Backed-up redo logs are called archivelogs.

Archivelogs are not reused; they are compressed into backup sets and deleted nightly. Each night, the scheduled Oracle jobs back up all the day's archivelogs into backupsets (a set of backup files). Once the archivelogs become part of the backupsets, the archivelogs are deleted from the file system.

By default, PowerSchool will keep 31 days of the backupsets. Oracle jobs that perform backups run nightly. Once a week, a full backup is generated, and incremental backups are made the other six days of the week. Incremental backups contain only the changes made to the database since the previous backup.

Understanding Oracle Backup and Recovery 6

Files Not Backed Up by Oracle

Files that are not stored in the Oracle database are not backed up automatically and require manual intervention to be backed up.

The PowerSchool data folder is not backed up with Oracle. This folder contains information such as:

All photos (Student/Staff/Reports)

Output of completed reports

The legacy custom web_root

PowerSchool Encryption Keys (keys folder)

In a Single Server environment, this folder is located at Program Files > PowerSchool > Data. In a Server Array environment, this is a network shared folder defined in the PowerSchool Installer Mapped Drives.

Also, the contents of the Document Server are not backed up with Oracle. This is typically a folder located at the root drive or a shared drive and has a default name of ps3.

Oracle File Structure

An Oracle installation creates several files and folders on the drive(s). On a Windows operating system, the primary folders are oracle and oradata. Since Oracle is a self-managing database, the permissions of these folders mustn't be changed. Also, some folders should not be accessed at all while the Oracle service is running, including access by antivirus or backup software. Accessing these folders while Oracle is running can lead to database corruption.

Backupsets and archivelogs should never be manually modified or deleted. Oracle manages these files within the parameters defined by the retention policy. For more information on how to modify the retention policy, refer to the Administration section of this guide.

The following table lists the directory locations in Oracle that should be backed up, which can be safely backed up while the Oracle Database is running (Online Backup), and which can only be backed up while the Oracle Database is not running (Offline Backup):

oracle\product\[Oracle Version]\dbhome_1\NETWORK\ADMIN

oracle\product\ [Oracle Version] \dbhome_1\database oradata\[SID]\DATAFILE oradata\fast_recovery_area\[SID]\backupset oradata\fast_recovery_area\[SID]\autobackup (19c) oradata\fast_recovery_area\[SID]

Yes

No No Yes Yes No

No

Yes 
Yes 
No 
No 
Yes PSPRODDB).

Oracle Database Backup and Restore Guide

Directory LocationOnline BackupOffline Backup

Note: [SID] is the SID entered during the Oracle installation (commonly and by default

Understanding Oracle Backup and Recovery

7

Disaster Recovery Concepts

Disaster recovery is the process of regaining access to the data, hardware, and software necessary to resume critical business operations after a natural or human-induced disaster. A school district's Disaster Recovery Plan (DRP) with respect to PowerSchool relies heavily on usage and configuration characteristics specific to every server and district.

This section covers backup and recovery topics and identifies directories that should be backed up per your entire district's DRP.

In addition to backing up the Oracle file systems identified in the tables in the previous section, it is also possible to export your data to a file that can be used to recover your database in the event of a disaster.

The best practice for disaster recovery is frequently exporting your data and moving the exported data to another physical location. Steps to export your data are provided in the procedure Run a Datapump Export in the Backup section of this guide. With this single export data file stored safely away, you can easily recover to a new server.

The export process can be run anytime without interrupting access to PowerSchool or the database (the best practice is to run an export during times of lessor activity when possible). The resulting datapump export file is relatively small and can be compressed, making it easy to transfer to another server or media (CD, DVD, or tape) for off-site storage. Using the database export to store your data off-site, in addition to the Oracle automated backups, provides you with the redundancy necessary to quickly recover from any disaster scenario. Previous days' datapumps can be backed up while the database is online.

The Oracle automated scheduled backups enable the quick recovery from many situations, such as data file corruption due to power outages or user errors but recovering from a hard drive failure can be complicated, difficult, or even impossible if you do not have the correct off-site backups. With an exported data file, recovery is simplified.

Additional backup and restore functions and processes, including a list of Oracle file systems that should be included in warm and cold backups that can also be used to restore your database in the event of a disaster, are provided in this guide.

Oracle Database Backup and Restore Guide

Understanding Oracle Backup and Recovery 8

Backup

Backups (both RMAN and datapump) are automatically set and configured during the 12c installation process. If email parameters were entered in your previous Oracle installation, they will be carried over to your new installation.

If you need to change the email parameters, the Configure PowerSchool Backup Jobs configuration page can be used. The email parameters entered determine who receives a notification when the full (RMAN) backup has been completed.

A full backup is performed automatically by default every Saturday at 1:15 a.m. An incremental backup runs nightly all other days of the week at 1:15 a.m. and will back up all data changed since the most recent full backup. This backup includes reports added to the Enterprise Reporting application using the Oracle Application Express (APEX) report builder but does not include reports created outside of

the Enterprise Reporting application. The backupsets and archivelogs that are compressed in the full backup are located in the fast recovery area directory. The fast recovery area location is based on the database layout configured during installation. For more information, see the Database Layout section of the installation guide.

A datapump export is also completed as part of the nightly backup process. The datapump export runs by default at 4:30 a.m. daily. The export is a complete backup of the database that includes table data, object metadata, and control information. This back up also includes application 100 and 200 reports added to the Enterprise Reporting application using the Oracle Application Express (APEX) report builder by default but does not include reports created outside of the Enterprise Reporting application. This backup provides a portable solution for restoring data and is located in the datapump directory which is further explained in the Datapumps section of this document.

The Oracle jobs scheduler executes all of the backup scripts. An email notifies the designated administrator when a full (RMAN) backup is completed and directs the administrator to check the log output. The RMAN log files are available in the oracle\scripts\[SID]\backups folder. The datapump export log files are available in the datapump directory

The default recovery span for the full backup is based on the retention policy and is set to a default of 31 days, which means that backups can be recovered up to 31 days in the past. These RMAN backup files are maintained in the fast recovery area directory. The datapump export files and logs are retained for 7 days in the datapump directory.

Note: The steps outlined in this document address recoveries that require data from the past seven days. Any recoveries older than seven days may require PowerSchool Technical Support's intervention.

There are several ways to back up PowerSchool's associated database files.

Online backups are created while PowerSchool and Oracle are running and accessible.

With PowerSchool and Oracle running there are several directories to backup to assure recovery in the event of a disaster.

Important: If other Oracle related files are backed up while PowerSchool and Oracle are online, possible data corruption can occur within Oracle tablespaces (datafiles) resulting in the need for server downtime while PowerSchool Technical Support repairs the database or recovers a backup from before the incident occurred.

Offline backups, or "cold backups", are created while PowerSchool and Oracle are not running and not accessible. All files can be backed up in offline status.

Oracle Database Backup and Restore Guide

Backup

9

With both PowerSchool and Oracle not running, there are several directories to backup. By backing up these directories, a snapshot is taken of archive (redo) logs, flash recovery logs, and the weekly and nightly backups that occur at 1:15 a.m. every morning. These directories are locked while Oracle is running, and the operating system does not allow them to be backed up.

When generating offline or online backups, it is recommended that you copy the backups from the nightly volume to a separate storage area in case of a disaster. PowerSchool recommends moving a copy of the backup to a separate physical location such as an establishment that specializes in media storage.

Manual Backup

There are two types of RMAN backups generated through the Oracle Jobs. There is a full backup that is run weekly and an incremental backup runs daily. In the backup set folder, the file names of the backups are dated and either has an L0 (Level 0) in the file name for the weekly backup, or an L1 (Level 1) for the incremental backup.

On Windows, open the Command Prompt.

Enter the following:

Weekly Full Backup

[Oracle binaries drive]\oracle\scripts\[SID]\backup\ps_weekly_backup.bat

Daily Incremental Backup

[Oracle binaries drive]\oracle\scripts\[SID]\backup\ps_daily_backup.bat

Press Enter/Return.

Check the RMAN output log for any errors:

[Oracle binaries drive]\oracle\scripts\[SID]\backup\rmanlog.log Datapumps

The datapump scripts rely on the datapump directory. The export script automatically exports files to the datapump directory, and the import script automatically looks for files to import in that same directory.

Datapumps are maintained for seven days. The datapumps are named based upon the day of the week in which the export occurred. For every 10K students, allocate 25GB of additional disk space. PowerSchool strongly recommends including these datapumps as part of your offsite backup strategies. To disable this feature, set the PS.DAILY_FULL_EXPDP job to false in PowerSchool Administrator.

The drive location is dependent on the database layout selected during installation. If one drive was selected for the database installation, the directory is located on that drive in the following directory:

• [drive]:\oradata\[SID]\data_pump_dir

Oracle Database Backup and Restore Guide

Backup 10

If two or more drives were selected for the database installation, the datapump directory is located on the second drive in the same path listed above. For more information, see the Database Layout section of the installation guide.

Run a Datapump Export

On the server that you want to export data from, open the Command Prompt.

Enter [drive]:, where [drive] is the drive on which the Oracle binaries are installed.

Press Enter/Return.

Enter cd \oracle\scripts.

Press Enter/Return.

Enter Export.bat [SID] [Filename] [FLASHBACK/NO_FLASHBACK] [NO_APEX].

[SID] is required. It is the SID entered during the Oracle installation (commonly and by default PSPRODDB).

[Filename] is required. It is the name you provide for the file that includes the export dataset. The filename can be anything you choose in any format.

[FLASHBACK/NOFLASHBACK] is optional. The default is FLASHBACK. NO_FLASHBACK should not be used without assistance from PowerSchool Support.

NO_APEX is optional. Without this parameter, Apex configuration data is exported with the PS schema. If NO_APEX is present, then the Apex data is not exported, and any existing Apex configuration will not be replaced when this datapump is imported. NO_APEX should not be used without assistance from PowerSchool Support.

Press Enter/Return.

The datapump export is now in the folder [drive]:\oradata\[SID]\data_pump_dir.

Note: Previous days' datapumps can be backed up while the database is online.

Run a Datapump Import

On the application server, navigate to Program Files > PowerSchool and double-click

PowerSchool Installer.html to open the PowerSchool Installer.

On the Configure Server page, click Stop PowerSchool/PowerTeacher Services. On the

Confirmation page, click Confirm. PowerSchool/PowerTeacher Services are stopped.

On the Configure Server Page, click Stop ReportWorks Services. On the Confirmation page, click

Confirm. ReportWorks services are stopped.

On the application server, open the Microsoft Management Console, navigate to Services, and

then right-click on PowerSchool Message Service and select Stop from the pop-up menu.

On the server that you want to import data to, copy the datapump export file to

[drive]:\oradata\[SID]\data_pump_dir.

Open the Command Prompt.

Oracle Database Backup and Restore Guide

Backup

11

Enter [drive]: where [drive] is the drive on which the Oracle binaries are installed.

Press Enter/Return.

Enter cd \oracle\scripts.

Press Enter/Return.

If this server currently has a PowerSchool database installed, enter DropSchema.bat [SID] and press Enter/Return.

Enter Import.bat [SID] [Filename] [Y/N] [ALL/DEFAULT]. If you are importing a datapump file on to a test server, then use ImportTestServer.bat [SID] [Filename] [Y/N] [ALL/DEFAULT].

[SID] is required. It is the SID entered during the Oracle installation (commonly and by default PSPRODDB).

[Filename] is required. It is the name of the datapump file that is in the [drive]:\oradata\[SID]\data_pump_dir.

[Y/N] is required. Y will delete production server connection information for PowerSchool, PowerTeacher Gradebook, ReportWorks, and Document Attachments. This is useful if the datafile originated from another server with different connection information. For datafiles originating on the same server, a value of N will retain the connection settings.

[ALL] is optional. The default value is DEFAULT. DEFAULT only imports PS and PS_MGMT. ALL imports all schema in the datapump. ALL should not be used without assistance from PowerSchool Support. 
Note: This setting will not disable email, SIF, or AutoComm/AutoSend events.

For test servers, the ImportTestServer.bat script will disable common settings and services from a live production server that should not typically be active on a test server, such as Email, AutoComm, and AutoSend. This script is not installed if you are using Oracle 12.1.0.2.

Press Enter/Return. The import process displays the progress on-screen as it works through the import. Occasionally errors may be reported, some of which can be ignored. Review DB Import Errors and Warnings to understand the errors that can occur during the import process, and what actions may need to be taken.

On the application server, open the Microsoft Management Console, navigate to Services, and then right-click on PowerSchool Message Service and select Restart from the pop-up menu.

On the PowerSchool Installer Configure Server page, click Start PowerSchool/PowerTeacher Services. On the Confirmation page, click Confirm. PowerSchool/PowerTeacher Services are started.

16. On the Configure Server Page, click Start ReportWorks Services. On the Confirmation page, click Confirm. ReportWorks services are started.

17. On the application server, navigate to Program Files > PowerSchool and double-click PowerSchool Installer.html to open the PowerSchool Installer.

18. Click Configure PowerSchool Backup Jobs and follow the on-screen instructions. Note: Configure backup jobs on the database node.

Oracle Database Backup and Restore Guide

Backup

12

Restore and Recovery

It is possible to restore the backup onto a different computer running PowerSchool 20.x.

To remedy an accidental erasure of the database, perform the first part of the Restore process to make a backup of any existing databases. Be sure you have a full backup before running any restore and recovery scenarios. For more information, see the Manual Backup section of this guide.

To import a backup to a test server, use the procedure for ImportTestServer.bat. To import a backup to a Production server, use the procedure for Import.bat which will not disable production system configurations and settings.

Note: Virtual machines running PowerSchool must not be restored from a snapshot. 
Data Replication to a Different Server using the Datapump Utility

Restoration and recovery of the database to a test server requires the use of Oracle's datapump technology. The following steps are used to replicate data on a different server:

Daily export files are available on your production server. [drive]:\oradata\[SID]\data_pump_dir

Remove any existing data on the target server (run the DropSchema script as instructed in the Run a Datapump Import procedure in the Backup section).

Import data into the target server (see Run a Datapump Import in the Backup section).

Configure Oracle Jobs through the Configure PowerSchool Backup Jobs link in the PowerSchool

Installer.

Modify the PS user password, if applicable (see Modify Oracle User Permissions in the Administration section).

Configure the Document Server, if applicable (see Configure Document Server in the Administration section).

The four scripts listed below are included in the Oracle installer to simplify the import and export process. These scripts are located on the same drive on which the Oracle binaries are installed (Drive 1). See Run a Datapump Export in the Backup section for details on export.

Note: These scripts handle the movement of Application Express (APEX) data for Enterprise Reporting between databases.

• [drive]:\oracle\scripts\Export.bat 
• [drive]:\oracle\scripts\DropSchema.bat 
• [drive]:\oracle\scripts\Import.bat 
• [drive]:\oracle\scripts\ImportTestServer.bat

The DropSchema script deletes existing schema, which is necessary when importing into an Oracle database with an existing dataset. Export.bat creates a dump file of all of the data including a transportable version of Application Express content. Import.bat and ImportTestServer.bat import the data pump, including Application Express content into a production or test database respectively.

Oracle Database Backup and Restore Guide

Restore and Recovery 13

Administration 
Unlock the Database User Accounts

If you have been locked out of the database, a generic error stating that PowerSchool cannot connect to the database appears. There are several reasons why this error occurs.

Use the following procedure to unlock the database user accounts.

On the database server, on the command prompt type sqlplus /@PSPRODDB as sysdba

Note: If you used a Database SID other than PSPRODDB, substitute it in the above command.

You are now logged into Oracle using local authentication. On the command prompt type alter

user PS account unlock;

Press Enter.

Type alter user PS_MGMT account unlock;

Press Enter.

Type alter user APEX_PUBLIC_USER account unlock;

Press Enter.

Type exit

Press Enter.

Note: All APEX user account passwords must match the PS and PS_MGMT account passwords. If the passwords are not identical, you will need to update the APEX_PUBLIC_USER account and run the Configure Database Connection process in the PowerSchool Installer.

Fast Recovery Area

PowerSchool is installed with a default setting of 100GB of backup space. Depending on the usage of the application and retention policy, this value may need to be adjusted. After migration to PowerSchool 9.2 or later is complete, it is recommended that the fast recovery area limit be adjusted while considering overhead for the operating system and other processes.

The following formula can be used to adjust the fast recovery area: 
100GB + ([Remaining free hard drive space on the fast recovery drive] X 80%)

For example, after PowerSchool is installed, there is 600GB of hard drive space left. Based on the above calculation, the fast recovery area should be set to 580GB:

100GB + (600GB X .80) = 580GB 
The fast_recovery_area folder is located in the following directory:

• Search the root of all the drives for oradata. This directory may contain a folder called fast_recovery_area. The location is dependent on how many drives were selected during the initial Oracle installation. The oradata directory may be located on multiple drives, but only one of these directories will contain the fast_recovery_area folder.

Oracle Database Backup and Restore Guide

Administration 14

Change the Fast Recovery Area Size

To change the flash recovery area size, perform the following procedure.

Note: If you do not perform this procedure, backup space on the server could reach the capacity limit, resulting in server downtime and the need for PowerSchool Technical Support intervention.

Open the Command Prompt.

Enter sqlplus / as sysdba

Press Enter/Return.

Enter ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=[new_size]; (where [new_size] is the size decided on using the formula above). For example: ALTER SYSTEM SET DB_RECOVERY_FILE_DEST_SIZE=580G;

Press Enter/Return.

Enter Exit.

Press Enter/Return.

Backup Retention Policies

By default, PowerSchool sets the retention policy for backups to 31 days for full and incremental backups and seven days for datapumps. Full and incremental RMAN backups are compressing the database archivelogs and are taken daily at 1:15 a.m. by default. Datapump backups are portable snapshots of the database that run by default at 4:30 a.m. daily.

Note: Retention should never be set below 14 days. 
Use the following procedures to alter these backup retention policies.

Alter Retention for Full and Incremental Backups

Open the Command Prompt.

To log into SQLPLUS, enter sqlplus / as sysdba

Press Enter/Return.

Enter UPDATE PS_MGMT.RMAN_PROPERTIES SET PROPERTY_VALUE = [X] WHERE PROPERTY_NAME = 'rman_retention_window'; where [X] is the number of days you would like to retain your daily backups. For example: UPDATE PS_MGMT.RMAN_PROPERTIES SET PROPERTY_VALUE = 21 WHERE PROPERTY_NAME = 'rman_retention_window';

Press Enter/Return.

Enter Exit.

Press Enter/Return.

Oracle Database Backup and Restore Guide

Administration 15

Removing Previous Server Information

The cleaning of production information from the Server_Instance, Server_Config, ConfigItem tables, and the PSM_Configuration table that could cause a user to point to a production server rather than a test server is now incorporated into the PowerSchool Installer.

Modify Oracle User Password

The PowerSchool Installer now allows the user to change the PS database user password.

On your server, navigate to Program Files > PowerSchool.

Double click the PowerSchool Installer shortcut

Click on the Reset PS Password link from the home page.

Enter the Current Oracle PS Password.

Enter the New PS Password and confirm the new password.

Click Next.

Click Confirm.

Click Done.

Click Configure Database Connection.

Enter new Oracle PS Password.

Click Next.

Click Confirm.

Note: You must run the Configure Database Connection process on each application node.

13. Click Done.

Configure Document Server

During the import process, Document Attachments settings are cleared from the database. The following procedure is required to reconnect your server to your existing document attachment data that may have been previously configured on your test server.

Reconnect the Server After Importing Production Data to a Test Server

In the PowerSchool installer, navigate to Configure PowerSchool Document Server.

Verify your Document Server mapped drive is pointing to the correct location for the server you are configuring. In the Hostname/IP field, remove the PowerSchool server that is currently assigned and replace it with the new value, if applicable.

Note: Only one PowerSchool environment can be connected to a Document Server drive at any given time. You will need a separate environment for Production and Test servers.

Click Next.

Administration 16

Oracle Database Backup and Restore Guide

On the next screen, verify your Document Server Storage Quota (In GB) value is correct.

Click Next.

On the next screen, click Confirm.

When Confirmation Required screen appears, select the appropriate value. If the previous screens were verified properly, this should be Yes.

Click Confirm.

After PowerSchool restarts, sign in to PowerSchool.

Navigate to System > Special Operations.

Select Rebuild Document Attachment Metadata from Document Storage Server from the pop- up menu.

Click Submit.

Click Rebuild.

Note: This process should only be done if the imported data is the same dataset as the last one utilized. If the dataset is different, this process will orphan records that will need to be manually reattached.

Click Confirm Rebuild.

Disable Production-Impacting Settings and Functionality

After launching PowerSchool in a test environment, before allowing access to other users, the following items should be removed to ensure that a test environment does not interfere with production data and processes:

Outgoing Email – On the test server, navigate to Start Page > System > System Settings > Email, and select No from the Enable Email Notifications (if No, Overrides Guardian Setting) pop-up menu.

AutoComm/AutoSend - If AutoComm or AutoSend are set to send or receive data via FTP or by network share, disable these processes to prevent test environment data from impacting production processes.

Start Page > System Administrator > AutoComm/AutoSend Setup

Double-check the following areas of PowerSchool to ensure that your production settings were properly removed and automatically reconfigured:

Start Page > System Administrator > ReportWorks Administration > ReportWorks Preferences Start Page > System Administrator > System Settings > Global Server Settings

Oracle Jobs Email Settings

During the Oracle Jobs installation, an option is available to enter email information to inform via email once the RMAN backup job has been completed. Three properties need to be set for the emails: the

Oracle Database Backup and Restore Guide

Administration 17

FROM address (rman_email_from), the TO address (rman_email_to), and the SMTP Server address (smtp_out_server).

View the Oracle Jobs Email Settings

Open the Command Prompt.

Enter sqlplus / as sysdba

Press Enter/Return.

Enter select * from PS_MGMT.rman_Properties;

Press Enter/Return.

Modify Oracle Jobs Email Settings

On your server, navigate to Program Files > PowerSchool.

Double click the PowerSchool Installer shortcut.

Click the Configure PowerSchool Backup Jobs link.

Enter new backup settings in the applicable fields.

Click Next.

Click Confirm.

Click Done.

Note: When a datapump is performed on an Oracle 12c server, the backup jobs DO NOT get imported. If you do not enable backup jobs, your archive logs will reach maximum capacity and the server will run out of disk space. To re-enable the backup jobs, re-run the Configure PowerSchool Backup Jobs through the installer after importing the datapump.

0 Comments

Leave us your comments

Related Information

Server Virtualization Requirements and Configuration Guide for PowerSchool

Server virtualization within IT environments has become a popular concept to reduce costs and effect...

PowerSchool 21.x System Requirements

This document contains the hardware and software requirements for implementing PowerSchool 21.x Stu...

PowerScheduler Checklist: Load Only

For schools that want an automated process to schedule students into classes. The process loads stud...

Oracle Database Backup and Restore Guide

This guide describes the backup and recovery process and the steps necessary to restore the PowerSch...