General Backup Instructions

1. Download and install the Reliable Data Protection Backup Manager
   • Windows
   • Mac OS X
   • Unix/Linux
   • Novell Netware
2. Open the backup manager
3. Create a new backup set
   1. From the menu, choose [Backup Set] -> [New] -> the type of backup you would like to perform
   2. Enter a name for your backup set
   3. Select the files/databases to back up
   4. Enter a temporary directory for storing the backup files before they are sent to the Reliable Data Protection Backup Server (when appropriate)
   5. Set the backup schedule for this backup set
   6. Set encryption algorithm, encryption mode, and encrypting key for the backup set
4. Run backup
   1. Select the backup set you want to run on the left panel and press the [Start Backup] button
   2. Select the backup type you would like to run
   3. Select [Off-site Backup Server] to start backing up your files to the backup server

After this first manual backup, all other backups will run automatically, according to the backup schedule you set up. Note that some types of backups have special requirements that must be set up before a backup can take place. These requirements are listed below.

What are the requirements for backing up:

Oracle 8i/9i/10g

• Reliable LifeSaver Manager must be installed onto the computer that can connect to your Oracle 10g server using TCP/IP protocol.

• Data from Oracle 10g database will be backed up to a temporary directory before they are sent to the Reliable Data Protection Backup Server. Please make sure you have sufficient space on your computer to store the data when you run the backup job.

• Database must be in archived log mode

  • Set the parameters below in the PFILE to enable automatic archiving

  LOG_ARCHIVE_DEST = [directory where archive redo logs will be stored]
  LOG_ARCHIVE_FORMAT = ‘log%t_%s_%r.arc’
  LOG_ARCHIVE_START = TRUE

  • Set ORACLE_SID to your database’s System Identifier (SID)

  export ORACLE_SID=GDB1 (assuming your database’s SID is GDB1)

  • Run SQL Plus and connect to database as SYSDBA

    For Oracle 9i/10g

  sqlplus “/ as sysdba”

  For Oracle 8i

  connect internal ;

  • Shutdown database

  shutdown immediate

  • Start and mount database

  startup mount;

  • Switch database to archived log mode

  Salter database archivelog;

  • Open database

  alter database open;

  • Enable Oracle JVM for Oracle 8i/9i, please do the following

    • Please make sure shared pool size is larger than 50MB and java pool size is larger than 20MB in the PFILE. For example:

    java_pool_size = 20971520
    shared_pool_size = 52428800

    • Run the scripts below

For Oracle 8i

SVRMGRL> connect internal
SVRMGRL> @?/javavm/install/initjvm.sql;
SVRMGRL> @?/rdbms/admin/catalog.sql;
SVRMGRL> @?/rdbms/admin/catproc.sql;
SVRMGRL> @?/javavm/install/initdbj.sql;

For Oracle 9i

SQL> connect sys/change_on_install as sysdba
SQL> @?/javavm/instal/initjvm.sql;
SQL> @?/xdk/admin/initxml.sql;
SQL> @?/xdk/admin/xmlja.sql;
SQL> @?/rdbms/admin/catjava.sql;

For Oracle 10g
Oracle JVM is enabled by default. No additional steps required

• JAVASYSPRIV role must be granted to system account
  You can grant this role to system account by executing (Oracle 9i/10g):
  > SQL> grant JAVASYSPRIV to system;

For Oracle 8i:

SVRMGRL> connect internal
SVRMGRL> @?/javavm/install/initjvm.sql;
SVRMGRL> @?/rdbms/admin/catalog.sql;
SVRMGRL> @?/rdbms/admin/catproc.sql;
SVRMGRL> @?/javavm/install/initdbj.sql;
SQL> grant javasyspriv to system;

Micrsoft SQL

• Reliable Data Protection Manager must be installed onto the computer running Microsoft SQL Server.
• Data from Microsoft SQL Server will be backed up to a temporary directory before they are set to the Reliable Data Protection Backup Server. Please make sure you have sufficient

space on your computer to store these data when you run the backup job. - If you wish to perform a differential or transaction log backup, make sure that the recovery model is FULL.

Lotus Domino / Notes

• Reliable Data Protection Manager must be installed onto the computer running Lotu Domino server/ Notes client.
• The computer running Lotus Domino server / Notes client must be on a Windows platform.
• Data from Lotus Domino server / Notes client will be backed up to a temporary directory before they are sent to the Reliable LifeSaver Backup Server. Please make sure you have sufficient space on your computer to store the data when you run the backup job.
• Lotus Domino server must run with archive logging enabled.
  1. Ensure that all databases to be logged reside in the Domino data directory, either at the root or in subdirectories.
  2. From the Domino Administrator, click the Configuration tab.
  3. In the “User Directory on” field, choose the server’s Domino Directory.
  4. Click Server Configuration, and then click Current Server Document.
  5. Click the Transactional Logging tab.
  6. Complete these fields, and then save the document

Field	Enter
Transactional Logging	Choose Enabled. The default is Disabled
Log path	Path name location of the transaction log. The default path name is LOGDIR in the Domino data directory, although it is strongly recommended to store the log on a separate, mirrored device, such as a RAID (Redundant Array of Independent Disks) level 0 or 1 device with a dedicated controller. The separate device should have at least 1GB of disk space for the transaction log. If you are using the device solely for storing the transaction log, set the “Use all available log device” field to Yes.
Maximum log space	The maximum size, in MB, for the transaction log. Default is 192MB. Maximum is 4096MB (4GB). Domino formats at least 3 and up to 64 log files, depending on the maximum log space you allocate.
Use all available space on log device	Choose one: Yes to use all available space on the device for the transaction log. This is recommended if you use a separate device dedicated to storing the log. If you choose Yes, you don’t need to enter a value in the “Maximum log space” field. No to use the default or specified value in the “Maximum log space” field.
Automatic fixup of corrupt databases	Choose one: Enabled (default). If a database is corrupt and Domino cannot use the transaction log to recover it, Domino runs the Fixup task, assigns a new DBIID, and notifies the administrator that a new database backup is required. Disabled. Domino does not run the Fixup task automatically and notifies the administrator to run the Fixup task with the -J parameter on corrupt logged databases.
Runtime / Restart performance	This field controls how often Domino records a recovery checkpoint in the transaction log, which affects server performance. To record a recovery checkpoint, Domino evaluates each active logged database to determine how many transaction would be necessary to recover each database after a system failure. When Domino completes this evaluation, it: Create a recovery checkpoint record in the transaction log, listing each open database and the starting point transaction needed for recovery Forces database changes to be saved to disk if they have not been saved already Choose one: Standard (default and recommended). Checkpoints occur regularly. Favor runtime. Domino records fewer checkpoints, which requires fewer system resources and improves server run time performance. Favor restart recovery time. Domino records more checkpoints, which improves restart recovery time because fewer transactions are required for recovery.
Logging Style	Choose Archive. The default is Circular

Note: You can only run transaction log backup if you have transaction logging enabled and you are using archive mode. You will be unable to run transaction log backup if you have transaction logging enabled not in archive mode, or if transaction logging is not enabled at all. If you try to issue the command, you will receive an error message.

Microsoft Exchange Server

• Microsoft Exchange Server 2000 with Services Pack 3 and post-SP3 update rollup installed. Please refer to http://www.microsoft.com/exchange/ for more information.
  or
  Microsoft Exchange Server 2003.
• Reliable Data Protection Manager must be installed onto the computer running Microsoft Exchange Server 2000/2003.
• Data from Microsoft Exchange Server will be backed up to a temporary directory before they are sent to Offsite Backup Server. Please make sure you have sufficient space on your computer to store the data when you run the backup job.

Windows System State

• Microsoft Windows XP Professional / 2003
• Reliable Data Protection Manager must be installed onto the computer containing the system state you want to backup.
• Windows system state will be backed up to a temporary file before it is sent to the Reliable Data Protection Backup Server. Please make sure you have sufficient space on your

computer to store the temporary file when you run the backup job.

Individual Mail Level for Microsoft Exchange Server

• Microsoft Exchange Server 2000 with Services Pack 3 and post-SP3 update rollup installed. Please refer to http://www.microsoft.com/exchange/ for more information.
  or
  Microsoft Exchange Server 2003.
• Reliable Data Protection Manager must be installed onto the computer running Microsoft Exchange Server 2000/2003.
• mail Level Backup requires “Full Mailbox Access” permission for the user running Reliable Data Protection Manager. Normally, the manager can acquire the permission on its own but if you encounter ‘Access Denied’ errors, you need to manually grant access privileges to the user running Reliable Data Protection Manager using one of the following instructions below:

For one specific mailbox

Use the following procedure to grant access to an Exchange 2000 or an Exchange 2003 mailbox:

1. Start Active Directory Users and Computers.
2. On the View menu, ensure that the Advanced Features check box is selected.
3. Right-click the user whose mailbox you want to give permissions to and choose Properties.
4. on the Exchange Advanced tab, click Mailbox Rights.
5. Notice that the Domain Admins and Enterprise Admins have both been given Deny access to Full Mailbox access.
6. Click Add, click the user or group who you want to have access to this mailbox, and then click OK.
7. Be sure that the user or group is selected in the Name box.
8. In the Permissions list, click Allow next to Full Mailbox Access, and then click OK.
9. Click OK all the way out.
10. Restart the Microsoft Exchange Information Store.

For mailboxes located within a specific mailbox store

Use the following procedure to grant access to an Exchange 2000 or an Exchange 2003 mailbox found on a specific mailbox store:

1. Start Exchange System Manager.
2. Drill down to your server object within the appropriate Administrative Group. Expand the server object and find the required mailbox store within the appropriate Storage Group. Right-click it and choose Properties.
3. In the Properties window go to the Security tab.
4. Click Add, click the user or group who you want to have access to the mailboxes, and then click OK.
5. Be sure that the user or group is selected in the Name box.
6. In the Permissions list, click Allow next to Full Control, and then click OK.
7. Click ‘Apply’ and ‘OK’.
8. Restart the Microsoft Exchange Information Store.

For mailboxes located within a specific server

1. Start Exchange System Manager.
2. Drill down to your server object within the appropriate Administrative Group. Right-click it and choose Properties.
3. In the Properties window go to the Security tab.
4. Click Add, click the user or group who you want to have access to the mailboxes, and then click OK.
5. Be sure that the user or group is selected in the Name box.
6. In the Permissions list, click Allow next to Full Control, and then click OK.
7. Click OK all the way out.
8. Restart the Microsoft Exchange Information Store.

MySQL Server

• Reliable Data Protection Backup Manual must be installed onto the computer running MySQL server.

• Data from MySQL server will be backed up to a temporary directory before they are sent to the Reliable Data Protection Backup Server. Please make sure you have sufficient space on your computer to store the data when you run the backup job.

• There must be a MySQL account which can be used to connect from localhost.
  Add two new MySQL accounts for the Backup Manager

  mysql> GRANT ALL PRIVILEGES ON ∗.∗ TO ‘root’@’localhost’
  -> IDENTIFIED BY ‘some_pass’;
  mysql> GRANT ALL PRIVILEGES ON ∗.∗ TO ‘root’@’localhost.localdomain’
  -> IDENTIFIED BY ‘some_pass’;
  mysql> FLUSH PRIVILEGES;

  They are superuser accounts with full privileges to do anything with a password of some_pass.