| Oracle® Secure Backup Migration Guide Release 10.1 Part Number B25049-02 |
|
|
View PDF |
| Oracle® Secure Backup Migration Guide Release 10.1 Part Number B25049-02 |
|
|
View PDF |
This chapter explains how to migrate from Reliaty Backup to Oracle Secure Backup. This chapter contains the following topics:
Introduction to Oracle Secure Backup for Reliaty Backup Users
Overview of the Migration from Reliaty Backup to Oracle Secure Backup
Preparing for Migration from Reliaty Backup to Oracle Secure Backup
Installing Oracle Secure Backup on the Administrative Server
Stopping Oracle Secure Backup and Reliaty Backup Daemons on Linux and UNIX
Oracle Secure Backup Administrator's Guide provides a comprehensive introduction to Oracle Secure Backup. This section describes only the features of Oracle Secure Backup most relevant to Reliaty Backup users who are migrating to Oracle Secure Backup. The most important points are as follows:
Oracle Secure Backup retains the ability to back up and restore UNIX, Linux, Windows, and NAS file systems in a manner completely compatible with its predecessor, Reliaty Backup.
Oracle Secure Backup adds support for the SBT API 2.0, thereby enabling Recovery Manager (RMAN) to use the Oracle Secure Backup SBT interface for media management operations (see Oracle Secure Backup Administrator's Guide to learn more about the SBT interface).
Thus, Oracle Secure Backup performs two separate functions: the backup and restore of Oracle databases and the backup and restore of other file system objects.
Note:
What was referred to as recovering data in Reliaty Backup is referred to as restoring data in Oracle Secure Backup. The term "recovery" refers exclusively to database recovery, which is the process of rolling forward a database backup.Whether you use Oracle Secure Backup to back up the database or the file system, you must first establish an administrative domain and define hosts, users, devices, and so forth just as you did with Reliaty Backup.
This section contains the following topics:
To support the backup of Oracle databases, Oracle Secure Backup includes the following additional object types and policies:
Note:
Oracle Secure Backup does not support BMC SQL-BackTrack or Microsoft's Exchange and SQL databases.When backing up an Oracle database, you can use a configuration object called a database backup storage selector to manage aspects of the backup. For example, you can configure device restrictions, the media family, and resource wait time for a backup. The Web tool and obtool support a new set of commands for managing storage selectors: mkssel, chssel, lsssel, and renssel.
See Also:
Oracle Secure Backup Reference to learn about the database backup storage selector commandsWhen performing a non-database backup, you can skip files that would be included in a database backup. Examples of such files include Oracle datafiles, control files, archived redo logs, flashback logs, and so forth. To exclude these files, specify the exclude oracle database files directive in your dataset. The corresponding entry for a backup description file (BDF) is ~files.
See Also:
Oracle Secure Backup Reference to learn about the dataset syntaxAn RMAN backup of an Oracle database results in a backup set, which is a logical container for one or more backup pieces. Each backup piece is a separate backup image.
Through the Web tool and obtool you can list backup pieces (lspiece) and remove them (rmpiece). The lssection, rmsection, and unrmsection commands give you control over the individual sections of a backup piece.
See Also:
Oracle Secure Backup Reference to learn about the backup piece commands
Oracle Secure Backup Reference to learn about section commands
Reliaty Backup recycled volumes based on an expiration time determined when the volume set was created. The expiration time was based on the write window and volume retention time defined in the media family for the volume. Oracle Secure Backup uses the same type of time-managed expiration policy. You can make file system backups or RMAN backups to volumes that use a time-managed policy.
You can also make RMAN backups, but not file system backups, to volumes that use a new content-managed expiration policy. When you create a media family you specify which type of expiration policy should be used. A content-managed volume expires when all backup pieces on the volume have been marked as deleted. You use the DELETE command in RMAN to mark tape backups as deleted.
When you install Oracle Secure Backup, the software includes a default content-managed media family named RMAN-DEFAULT. Oracle Secure Backup users are not permitted to delete, change, or rename this media family.
See Also:
Oracle Secure Backup Reference for a description of the media family commandsThe rmanrestorestartdelay operations policy controls how long Oracle Secure Backup waits before beginning an RMAN-initiated restore operation. The default is 10 seconds. This delay enables the Oracle Secure Backup scheduler to optimize tape position operations when confronted with multiple restore requests.
In some cases, terminology used in the Reliaty Backup documentation has changed in the Oracle Secure Backup documentation. Table 1-1 describes some of the more significant changes.
Table 1-1 Terminology Changes
| Old Term | New Term |
|---|---|
|
Backup section |
|
|
Backup database (maintained by Reliaty Backup on administrative host) |
Backup catalog (maintained by Oracle Secure Backup on administrative server) |
|
Recover |
Restore |
See Also:
Oracle Secure Backup Administrator's Guide for a glossary of Oracle Secure Backup termsThe Reliaty Backup root directory is now called the Oracle Secure Backup home directory. This directory and the files contained within it are named differently in Oracle Secure Backup.
Table 1-2 Name Changes for Reliaty Backup Files and Directories
| Old Name | New Name |
|---|---|
|
/usr/local/reliaty/backup |
/usr/local/oracle/backup |
|
C:\Program Files\Reliaty\Backup |
C:\Program Files\Oracle\Backup |
|
/usr/etc/rb |
/usr/etc/ob |
See Also:
Oracle Secure Backup Installation Guide for a description of Oracle Secure Backup files and directoriesThis section describes changes to the way users and classes are handled.
To control user access to Oracle database backups, Oracle Secure Backup includes new class rights. The access Oracle backups right determines which database backups an Oracle Secure Backup user can access. The perform Oracle backups and restores right enables class members to back up and restore Oracle databases.
When Oracle Secure Backup is installed, a new class of users called oracle is defined. Users in this class can perform RMAN backup and restore operations and have owner rights to Oracle database backups. The admin class also has all Oracle rights.
You can preauthorize an operating system user name for either RMAN or command-line access to Oracle Secure Backup when logged into a given host. This technique enables use of Oracle Secure Backup without going through the normal Oracle Secure Backup login requirements. When installing Oracle Secure Backup, you have the option of defining an operating system user named oracle who is preauthorized to execute RMAN operations.
The following changes have been made to the handling of login tokens:
Your login token, which Reliaty Backup used to retain, is no longer stored in your home directory. Oracle Secure Backup maintains login tokens on the administrative server (formerly called the administrative host).
In Reliaty Backup, the login token was stamped with an expiration time based on the security/loginduration policy. If the administrator subsequently changed the loginduration policy, it would not affect the login token. In Oracle Secure Backup, the login token is tagged with the time of the login and its expiration time is dynamically recalculated on every login attempt.
See Also:
Oracle Secure Backup Reference to learn about class rights
Oracle Secure Backup Reference to learn about user commands
Oracle Secure Backup Reference to learn about class commands
This section describes changes to how Oracle Secure Backup handles tape libraries and tape drives.
Oracle Secure Backup discontinues the autoswap and wrap-around modes of library operation that were part of the automount logic in Reliaty Backup. The only change to the user interface is the removal of the corresponding options to the mkdev and chdev commands in obtool (and their Web tool equivalents).
Tape drives vary considerably in the degree to which the position query frequency in use affects tape throughput. For this reason, you can establish the position query frequency for each tape drive by specifying the --queryfreq option to mkdev and chdev for tape drives. These values take effect only if the operations/positionqueryfrequency policy is set to the default value.
The importvol and exportvol library commands are available in obtool and the Web tool. These commands move tapes into and out of a tape library through the import/export mechanism.
In Reliaty Backup, you could specify -f and -Xf multiple times on the rbtar command line. For example, the following command specifies that rbtar should write to device tape1 after tape0 is full:
rbtar -g home_bdf -f tape0 -f tape1
Oracle Secure Backup does not support multiple specifications of -f or -Xf on the obtar command line.
See Also:
Oracle Secure Backup Reference for a description of the device commands
Oracle Secure Backup Reference for a description of the library commands
This chapter explains how to migrate a Reliaty Backup administrative domain to an Oracle Secure Backup administrative domain. The migration procedure is usable for any version of Reliaty Backup.
This chapter assumes that you want to replace your Reliaty Backup administrative domain with an Oracle Secure Backup administrative domain. More specifically, the instructions make the following assumptions:
The set of hosts in the Oracle Secure Backup domain is the same set of hosts as in the Reliaty Backup domain.
Every host in the new Oracle Secure Backup administrative domain will retain its old Reliaty Backup role of administrative server, media server, or client.
The Oracle Secure Backup domain will include the same tape devices that existed in the Reliaty Backup domain.
If you want to add, modify, or remove hosts or devices from the new Oracle Secure Backup domain, then you can perform this configuration after you have installed Oracle Secure Backup on the hosts in the domain.
Note that you cannot create a mixed domain that includes hosts running Reliaty Backup and hosts running Oracle Secure Backup. The software architecture and network messages of the two backup applications differ substantially. Also, you cannot run both Reliaty Backup and Oracle Secure Backup on the same host simultaneously because it results in contention for communication ports.
This section describes the basic steps of the migration. Each step includes a link to a section in this chapter that explains the task in detail.
To migrate Reliaty Backup to Oracle Secure Backup:
Identify all hosts and devices in the administrative domain and then back up the Reliaty Backup files on the administrative server.
This task is described in "Preparing for Migration from Reliaty Backup to Oracle Secure Backup".
Install Oracle Secure Backup on the administrative server.
During the installation, the install script detects the Reliaty Backup installation and asks whether you wish to run a conversion routine called osbcvt. This utility automatically converts the pertinent Reliaty Backup administrative files into the proper formats and locations within Oracle Secure Backup.
This task is described in "Installing Oracle Secure Backup on the Administrative Server".
Stop all Reliaty Backup daemons running on Linux and Solaris clients and media servers, and stop all Reliaty Backup services running on Windows clients and media servers.
On Linux and Solaris clients and media servers, use stoprb from the administrative server to stop the Reliaty Backup daemons. This task is described in "Stopping Oracle Secure Backup and Reliaty Backup Daemons on Linux and UNIX".
On Windows clients and media servers, you must stop the Reliaty Backup services locally, using the Servicies tool in the Windows Control Panel. The necessary procedures are described in "Uninstalling Reliaty Backup and Installing Oracle Secure Backup on Windows Media Servers" and "Uninstalling Reliaty Backup and Installing Oracle Secure Backup on Windows Clients".
Install Oracle Secure Backup on the media servers in the administrative domain.
After you have migrated the administrative server you are ready to migrate your remote media servers (if any). The procedure is essentially the same as for installing Oracle Secure Backup on the administrative server.
This task is described in "Installing Oracle Secure Backup on Media Servers".
Install Oracle Secure Backup on the clients in the administrative domain.
After you have migrated the administrative server and media servers you are ready to migrate your clients. You can use your administrative server's client update feature to bring the Linux and UNIX clients into the domain. You must log on to each Windows client locally.
This task is described in "Installing Oracle Secure Backup on Clients".
Perform post-installation review and configuration of the administrative domain.
This task is described in "Performing Post-Installation Review and Configuration".
Uninstall Reliaty Backup from all Linux and UNIX hosts in the administrative domain.
This task is described in "Uninstalling Reliaty Backup from Linux and UNIX".
Your first task is to prepare for the migration. You should make backups of important files, cancel active and scheduled backup jobs, and stop Reliaty Backup daemons on the administrative server.
Note that these instructions refer to the administrative server, which was known as the administrative host in Reliaty Backup. Reliaty Backup did not support the use of a Windows host for an administrative server.
The Reliaty Backup home is the directory in which Reliaty Backup is installed. By default, this home directory is /usr/local/reliaty/backup on Linux and UNIX and C:\Program Files\Reliaty\Backup on Windows (see Table 1-2).
Follow these steps to prepare for the migration:
Log in to the Reliaty Backup Web tool and display all hosts and devices in the administrative domain. Copy this information to a convenient location.
Log on to the administrative server and back up the following Reliaty Backup files and directories, making sure to use a backup tool other than Reliaty Backup:
In this file you can locate the paths to other files that you want to back up. The following sample file shows typical directories:
local db dir: /usr/etc/rb temp dir: /usr/tmp rb dir: /usr/local/reliaty/backup admin dir: /usr/local/reliaty/backup/admin
The admin directory in the Reliaty Backup home (as specified in rbconfig)
The local database directory (as specified in rbconfig)
The install/rbparameters file in the Reliaty Backup home
Another backup method is to copy the rbconfig file, local database directory, and device files into the parent directory of your Reliaty Backup home. Afterwards, use tar to create an archive of this directory.
Assuming the paths shown in the preceding example of /etc/rbconfig, you would create the archive as follows:
cd /usr/local/reliaty # navigate to parent directory of Reliaty Backup home cp -r /etc/rbconfig /usr/etc/rb . # copy rbconfig and local db cd .. # navigate to superdirectory tar -cvf reliaty.tar reliaty # create TAR file
Note:
This backup can be quite large because it includes all of the Reliaty Backup catalog data for all backups on all hosts. Ensure that you have sufficient disk space for the backup.You could then use ftp to transfer the TAR file to another host on your network and remove the original TAR from your local administrative server. Other alternatives include a native tar backup to a local tape drive or writing the files and directories to removable media.
Change into the Reliaty Backup home and run the install/probedev utility. The command generates probedev.out in /tmp.
As shown in Step 7 of "Installing Oracle Secure Backup on the Administrative Server", you can use probedev.out as a reference for configuring the SCSI devices attached to your media servers.
Copy the install/rbparameters file in your Reliaty Backup home to a convenient location.
You will compare rbparameters to your new obparameters file to make sure that your installation locations are consistent.
Make sure that no active backups are running.
Check for active backups by using an lsjob command in rbtool or by checking jobs status in the Reliaty Backup Web tool. If active jobs exist, then wait for them to finish or cancel them with the canceljob command. If jobs are pending for today, then cancel them as well. You can cancel all pending and active jobs as follows:
rbtool lsjob -s | xargs rbtool canceljob
Stop all Reliaty Backup processes on the administrative server.
If you are using a Linux or UNIX system, then you can use the following command to list the processes:
/bin/ps -ef | grep rb
If your domain includes remote media servers, then gather the device information for these servers. Follow these steps:
Log on to each remote media server.
Change into the Reliaty Backup home and run the install/probedev utility.
Rename the probedev.out file for each media server so that the host of origin is included in the name: probedev_brhost2.out, probedev_brhost3.out, and so forth.
Transfer the renamed probedev.out files for all media servers into the same directory that contains the probedev.out file on the administrative server.
After you have completed the tasks in this section, you are ready to install Oracle Secure Backup on the administrative server.
The instructions for installing Oracle Secure Backup on the administrative server are essentially the same as the instructions in "Loading and Installing the Oracle Secure Backup Software on Linux or UNIX" in Oracle Secure Backup Installation Guide. The setup and most of the installation is identical.
The migration diverges from a standard installation if the installob script detects that Reliaty Backup is installed on your system. In this case, the script prompts you to migrate Reliaty Backup to Oracle Secure Backup. The script runs a migration utility called osbcvt.
The procedure in this section makes the following assumptions:
Your local host runs Linux or UNIX. Reliaty Backup does not support Windows as the administrative server.
Your local host was configured as an administrative server in Reliaty Backup.
You have convenient access to a copy of Oracle Secure Backup Installation Guide. Rather than duplicating information, some steps in this section refer to instructions in the installation manual.
The sample output in this section is for an installation on a Solaris host called sun_host with an attached tape drive and tape library. The instructions are equally applicable to Linux and UNIX.
To install Oracle Secure Backup on an administrative server:
Use the Linux or UNIX script utility (or another method of your choosing) to generate a transcript of the migration. This transcript may be useful if you need assistance from Oracle Support.
Stage the installation software as described in "Accessing Oracle Secure Backup Installation Software" in Oracle Secure Backup Installation Guide.
Follow Steps 1 through 7 in "Loading and Installing the Oracle Secure Backup Software on Linux or UNIX" in Oracle Secure Backup Installation Guide. Make the following choices:
When prompted to load packages, load all the packages that will be used by hosts in the administrative domain.
When prompted to review the obparameters file, compare the obparameters file to the old rbparameters file that you saved to a safe place in "Preparing for Migration from Reliaty Backup to Oracle Secure Backup".
Typically, obparameters has the following settings:
customized obparameters: yes start daemons at boot: yes start daemons at install: yes
Sometimes you need to customize the paths to the installation directories. Refer to Oracle Secure Backup Installation Guide to learn how to configure the parameters in this file. When you are satisfied with the obparameters file contents, enter yes at the installob prompt.
Choose the interactive mode of installation.
When prompted to select a role for your host, select the option for the administrative server.
When the installob script detects the Reliaty Backup installation, the script displays output similar to the following, which varies among operating systems:
An installation of Reliaty Backup has been detected on this host. If you have not already backed up your Reliaty Backup installation, Oracle recommends that you do so now. As a part of the migration the Oracle Secure Backup installer will disable any startup scripts used by Reliaty Backup. This is required to prevent the contention for port 400 by the Reliaty Backup and Oracle Secure Backup service daemons. Do you wish to proceed? [yes]
Enter yes to proceed.
The installob script asks you to confirm the migration:
Would you like to migrate the admin directory from Reliaty Backup to Oracle Secure Backup? [yes]
Enter yes to confirm the migration of the admin directory.
At this point the installob script launches the osbcvt utility and starts migrating the data. The script installs the Oracle Secure Backup device driver automatically. The script displays output similar to the following:
Starting data migration from Reliaty Backup to Oracle Secure Backup.
The Reliaty Backup admin data will be moved to /space/oracle/backup.051011
Data migration from Reliaty Backup is complete.
Beginning the installation. This will take just a minute and will produce
several lines of informational output.
Installing Oracle Secure Backup on sun_host (solaris version 5.7)
generating links for admin installation with Web server
checking Oracle Secure Backup's configuration file (/etc/obconfig)
setting Oracle Secure Backup directory to /space/oracle/backup.051011 in
/etc/obconfig
setting local database directory to /usr/etc/ob in /etc/obconfig
setting temp directory to /usr/tmp in /etc/obconfig
setting administrative directory to /space/oracle/backup.051011/admin in
/etc/obconfig
protecting the Oracle Secure Backup directory
installing /etc/init.d/OracleBackup for observiced start/kill ops at
operating system run-level transition
installing start-script (link) /etc/rc2.d/S92OracleBackup
installing kill-script (link) /etc/rc1.d/K01OracleBackup
installing kill-script (link) /etc/rc0.d/K01OracleBackup
initializing the administrative domain
NOTE: installing Oracle Secure Backup driver in order to identify SCSI
busses...
NOTE: /space/oracle/backup.051011/.drv.solaris/ob copied to /usr/kernel/drv/ob
NOTE: /space/oracle/backup.051011/.drv.solaris/ob.conf copied to /usr/kernel/drv/ob.conf
NOTE: /space/oracle/backup.051011/.drv.solaris/ob64 copied to
/usr/kernel/drv/sparcv9/ob
NOTE: The Oracle Secure Backup device driver has been successfully installed.
Is sun_host connected to any tape libraries that you'd like to use with
Oracle Secure Backup [no]?
If the local host is not a media server, then answer no to the next three questions to complete the administrative server installation; you can skip ahead to "Stopping Oracle Secure Backup and Reliaty Backup Daemons on Linux and UNIX". Otherwise, proceed to the next step to configure tape devices.
If you have tape libraries or tape drives attached to this host that you used with Reliaty Backup, then obtain the SCSI target ID and SCSI LUN for each device attached to your system.
"Finding SCSI Device Information on Linux and UNIX" explains how to obtain SCSI device information for these operating systems.
Create the device special files as explained in the section "Creating Device Special Files with installob" in Oracle Secure Backup Installation Guide. For each device attached to your system, supply the SCSI target ID and SCSI LUN obtained in the preceding step.
Note:
The sample output shown in this step is provided as an illustration, not as data for you to enter in your own installation.The following sample output shows how to configure the tape library and tape drive from the previous step:
Is sun_host connected to any tape libraries that you'd like to use with
Oracle Secure Backup [no]? yes
How many Oracle Secure Backup tape libraries are attached to sun_host [1]?
Please describe each tape library by answering the following questions.
Logical unit number [0]:
SCSI bus name-instance [pci1000,f0]:
SCSI target ID [3]: 1
SCSI lun 0-7 [0]:
Is the information you entered correct [yes]?
Is sun_host connected to any tape drives that you'd like to use with
Oracle Secure Backup [no]? yes
How many Oracle Secure Backup tape drives are attached to sun_host [1]?
Please describe each tape drive by answering the following questions.
Logical unit number [0]:
SCSI bus name-instance [pci1000,f0]:
SCSI target ID [4]: 0
SCSI lun 0-7 [0]:
Is the information you entered correct [yes]?
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Beginning device driver configuration and device special file creation.
NOTE: table for devlinks...
type=ddi_pseudo;name=ob;addr=0,0;minor=pci1000,f0 obt0
Could not read symbolic link /dev/bd.off
/dev/obt0 created
NOTE: table for devlinks...
type=ddi_pseudo;name=ob;addr=1,0;minor=pci1000,f0 obl0
Could not read symbolic link /dev/bd.off
/dev/obl0 created
- - - - - - - - - - - - - - - - - - - - - - - - - - -
NOTE: You must configure the new devices via the Web interface or via
the command line using the obtool 'mkdev' command.
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you like to install Oracle Secure Backup on any other machine [yes]?
Enter the name of a host onto which you'd like to install Oracle Secure Backup:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Would you like to install Oracle Secure Backup on any other machine [yes]?
Answer no when asked whether to install the software on other machines.
The following sample output shows the summary of the installation:
Would you like to install Oracle Secure Backup on any other machine [yes]? no
Installation summary:
Installation Host OS Driver OS Move Reboot
Mode Name Name Installed? Required? Required?
admin sun_host solaris no no no
Oracle Secure Backup is now ready for your use.
At this stage of the migration, you are now to stop the daemons in preparation for the installation on the remaining hosts in the domain.
The Reliaty Backup and Oracle Secure Backup service daemons use the same ports. If you have rbserviced running on a client or media server, then you will not be able to start observiced on the same host. Thus, you should stop the Reliaty Backup processes on the clients and media servers. You should also stop the Oracle Secure Backup processes running on the administrative server.
To stop Oracle Secure Backup and Reliaty Backup daemons:
Log on the administrative server (if you are not already logged on).
Stop all Oracle Secure Backup processes running on the administrative server.
You can use the following command to list the processes:
/bin/ps -ef | grep ob
Use a kill -9 command to stop each of the Oracle Secure Backup processes.
You can stop the Reliaty Backup daemons on Linux and UNIX media servers and clients by running the install/stoprb utility on the administrative server. You already stopped the Reliaty Backup daemons on the administrative server in "Preparing for Migration from Reliaty Backup to Oracle Secure Backup", so you do not need to stop the daemons on this host.
Note:
To stop the Reliaty Backup service on Windows hosts you must log on locally to each Windows host. This procedure is explained in This procedure is explained in "Uninstalling Reliaty Backup and Installing Oracle Secure Backup on Windows Media Servers" and "Uninstalling Reliaty Backup and Installing Oracle Secure Backup on Windows Clients".The procedure varies depending on whether you have remote shell (rsh) as root to the hosts on which the Reliaty Backup daemons are running:
If you have rsh enabled, then navigate to the Oracle Secure Backup home and use the install/stoprb utility on the administrative server.
You can use this utility to stop Reliaty Backup daemons on multiple hosts by specifying a space-separated list after the stoprb command. For example, the following command stops Reliaty Backup daemons on brhost1, brhost2, and brhost3:
# install/stoprb brhost1 brhost2 brhost3
If rsh is not enabled, then log on to each Linux and UNIX host in the domain and stop the processes.
You can use the following command to show the processes:
/bin/ps -ef | grep rb
Use the kill -9 command on the associated process IDs.
At this stage of the migration, only the administrative server has Oracle Secure Backup installed. You have stopped all Oracle Secure Backup and Reliaty Backup daemons running on Linux and UNIX hosts in the administrative domain.
You are now ready to install Oracle Secure Backup on the media servers and clients in the domain. If any of these hosts run the Windows operating system, then you will stop the Reliaty Backup services on these hosts, uninstall Reliaty Backup, and then install Oracle Secure Backup.
If your administrative domain uses media servers other than the administrative server, then install Oracle Secure Backup on each media server. Otherwise, skip to "Installing Oracle Secure Backup on Clients".
The installation instructions vary depending on the operating system of the media server. This section assumes that you have convenient access to a copy of Oracle Secure Backup Installation Guide. Rather than duplicating information, some steps in this section refer to instructions in the installation manual.
Note:
In this phase of the migration, you configure only the device special files and drivers for the media servers. The Reliaty Backup device names and other device configuration data is migrated to Oracle Secure Backup automatically. You can make changes to this data in "Performing Post-Installation Review and Configuration".The instructions for installing Oracle Secure Backup on media servers are basically the same as "Installing Oracle Secure Backup on the Administrative Server". You must log on to each host, access the installation software by mounting the distribution media or downloading a ZIP file, and then run setup and installob. The differences are as follows:
The instructions in this section apply to Windows media servers only. The instructions are written to be as generic as possible, so the names of the GUI elements may vary slightly among the various Windows platforms.
Before installing Oracle Secure Backup on a Windows host, you must stop the Reliaty Backup services and uninstall Reliaty Backup. Unlike in the case of Linux and UNIX, you cannot run a batch program to stop the Reliaty Backup daemons on Windows hosts remotely from the administrative server.
To uninstall Reliaty Backup and install Oracle Secure Backup on a Windows media server:
Stop the Reliaty Backup service as follows:
Open the Control Panel.
Double-click Administrative Tools.
Double-click Services.
Right-click Reliaty Backup and select Stop from the shortcut menu.
Uninstall the Reliaty Backup software as follows:
Open the Control Panel.
Double-click Add or Remove Programs.
Select Reliaty Backup.
Click Remove.
Click Yes to remove Reliaty Backup.
Remove the Reliaty Backup device driver as follows:
Open the Control Panel.
Double-click System.
Click the Hardware tab.
Click Device Manager.
Right-click the rbt driver and select Uninstall from the shortcut menu.
Click OK.
Restart the system.
Install Oracle Secure Backup on this host and configure it as a media server. This task is explained in Oracle Secure Backup Installation Guide.
When Oracle Secure Backup is installed on all media servers in your administrative domain, you are ready to install Oracle Secure Backup on the clients.
This section assumes that you have convenient access to a copy of Oracle Secure Backup Installation Guide. Rather than duplicating information, some steps in this section refer to instructions in the installation manual.
The installation instructions for a client vary depending on the host operating system. Installation instructions for all Linux or Unix clients are similar, and use the setup and installob scripts. The installation process for Windows is based upon a standard Windows installer.
Full instructions for performing client installation on Linux or Unix are contained in Oracle Secure Backup Installation Guide.
You must install the Oracle Secure Backup software individually on each client. Use the CD-ROM, mounted locally or through NFS, or installation media downloaded from OTN and extracted from a Zip file.
To install Oracle Secure Backup on Linux and UNIX clients:
Edit the obparameters file if necessary, comparing it to the old rbparameters file that you saved to a safe place in "Preparing for Migration from Reliaty Backup to Oracle Secure Backup".
Typically, obparameters has the following settings:
customized obparameters: yes start daemons at boot: yes start daemons at install: yes
Sometimes you need to customize the paths to the installation directories. Review the obparameters file and make sure that it contains the correct entries. Refer to Oracle Secure Backup Installation Guide to learn how to configure the parameters in this file.
Change to your Oracle Secure Backup home directory and run installob.
If you have installed Oracle Secure Backup in the default location, then you run the installation program as follows:
cd /usr/local/oracle/backup install/installob
When prompted, choose the options for interactive installation, and for the client role only.
After the client installation completes, the following prompt is displayed:
Would you like to install Oracle Secure Backup on any other machine [yes]?
Enter no at this prompt to exit the installob script.
The instructions in this section apply to Windows clients only. The instructions are written to be as generic as possible, so the names of the GUI elements within the Windows Control Panel may vary slightly among the various Windows platforms.
Before installing Oracle Secure Backup on a Windows host, you must stop the Reliaty Backup services and uninstall Reliaty Backup. Unlike in the case of UNIX and Linux, you cannot run a batch program to stop the Reliaty Backup daemons on Windows hosts remotely from the administrative server.
To uninstall Reliaty Backup and install Oracle Secure Backup on a Windows client:
Log on to the Windows client as an administrator.
Stop the Reliaty Backup service as follows:
Open the Control Panel.
Double-click Administrative Tools.
Double-click Services (you may have to double-click Computer Management and then Services).
Right-click Reliaty Backup and select Stop from the shortcut menu.
Uninstall the Reliaty Backup software as follows:
Open the Control Panel.
Double-click Add or Remove Programs.
Select Reliaty Backup.
Click Remove.
Click Yes to remove Reliaty Backup.
Shut down and restart Windows.
Install Oracle Secure Backup on this host and configure it as a client, using the instructions in Oracle Secure Backup Installation Guide. When prompted for roles to install on this host, select the media server role.
When Oracle Secure Backup is installed on all hosts in your administrative domain, you are ready to review the domain configuration and make any changes.
This section describes the following tasks:
The first time you run obtool after migration, you must reinitialize the administrative server to recognize the new security features of Oracle Secure Backup.
Note:
If you do not perform this step, then the first time you try to useobtool after migration, the following error message is displayed:
Error: Can't fetch this host's information --UID not found.
To reinitialize the administrative domain after migration:
Use the ps -ef command to identify any running Oracle Secure Backup processes:
ps -ef |grep ob
Stop each process identified in Step 1 with kill -9:
kill -9 pid
Run the obtool command with following options to reinitialize the administrative server:
obtool --initnewdomain --force
Inspect the configuration data for the administrative domain to ensure that it migrated correctly from Reliaty Backup. This section explains how to perform administrative tasks by means of the Oracle Secure Backup Web tool.
This section assumes that you are acquainted with the Web tool and have convenient access to Oracle Secure Backup Administrator's Guide. It also assumes that you have stopped the Oracle Secure Backup processes on the administrative server as described in Step 2 in "Stopping Oracle Secure Backup and Reliaty Backup Daemons on Linux and UNIX".
To review Oracle Secure Backup settings:
Log on to the administrative server and start the Oracle Secure Backup service daemon, which automatically starts the Apache Web server. For example:
/etc/observiced
Start the Web tool as explained in "Using the Web Tool" in Oracle Secure Backup Administrator's Guide. For example, if the administrative server is named sun_server, then enter the following URL in your browser:
https://sun_server
Log in to the Oracle Secure Backup administrative domain as admin.
The admin password for Oracle Secure Backup is the same password used for Reliaty Backup. As explained in Oracle Secure Backup Administrator's Guide, you can change the password for this user by clicking the Configure tab, Users, and then Change Password.
If you are backing up Windows clients and have Windows domains, then check the admin user settings to be sure that they are correct. Otherwise, skip this step and proceed to the next step.
Follow these steps to configure Windows domain settings:
Click the Configure tab and then click Users.
Select the admin user and click Edit.
Click Windows Domains.
Enter the Windows Domain Name, Administrative User, and password for each of the Windows Domains for Windows clients that you plan to back up with Oracle Secure Backup.
When defining an user for a Windows Domain, choose the Administrator or a user configured by the Administrator. This user must belong to the Backup Operators group, must not be required to change password at login, must have a non-expiring password, and must have the right to back up files and directories, restore files and directories, log in as a service, act as part of the operating system, increase quotas, and replace a process level token.
Review the configuration data for the hosts in your administrative domain.
Oracle Secure Backup Administrator's Guide explains how to review information for hosts and perform configuration tasks. Follow these steps:
From the home page, click the Configure tab and then Hosts.
Use the Hosts page as a base for the tasks in this step.
Optionally, select a host and click Rename to rename to change the name of a host within the administrative domain.
Select each host and click Ping to make sure that each host is resolvable to an IP address.
You can use nslookup or the /etc/hosts file on the administrative server to resolve IP address issues. Alternatively, click Edit to edit the properties of the host and define one or more resolvable names in IP interface name(s).
Ensure that the roles assigned to each host are correct. For example, ensure that the hosts with the media server role really are media servers.
Select each host and click Edit to confirm that the properties are set correctly. If a host is no longer in your network but has backups in the catalog for legacy reasons, then check Suppress communication with host and then Apply.
Select any obsolete hosts (that is, hosts no longer in the network and with no backups in the catalog that you need) and click Remove to delete the hosts from the domain.
Review the information for the tape devices in your administrative domain.
Oracle Secure Backup Administrator's Guide explains how to configure devices. Follow these steps:
Click the Configure tab and then click Devices.
Use the Devices page as a base for the tasks in this step.
Select each device and click Show Properties to review the properties to confirm that the settings are correct.
Note:
In most cases, tape devices are automatically migrated with the correct settings. You should verify the settings for each device. If some of them are not correct, use the process below to enter the new settings.For each device, click Edit and then Attachments. Attachments identify the host and internal name by which Oracle Secure Backup accesses the device.
The new device special files will be named hostname:/dev/obtOSB_LUN for tape drives and hostname:/dev/oblOSB_LUN for libraries, where OSB_LUN is a placeholder for the Oracle Secure Backup logical unit number.
To remove the existing attachment for a Reliaty Backup device (hostname:/dev/rb*) and replace it with the Oracle Secure Backup attachments, select the media server in Host and enter the raw device name. Typically, if you are replacing hostname:/dev/rbt0, then your new device will be hostname:/dev/obt0.
Click Apply to save your attachments settings and return to the Devices page.
Optionally, click Add to add any devices attached to Windows media servers that were not migrated from Reliaty Backup.
Click Ping for each device to make sure that it is accessible.
Optionally, select a device name and click Rename to rename any devices that you would like to identify by a different name.
Note:
Any pre-existing backup schedules have been imported from Reliaty Backup with the former device names. If you change the device names, then remember to update the backup schedules to use these new names.Edit each media family, and update it with the needed time management parameters.
Note:
If you do not perform this step, then when you try to use a migrated media family, the following error is displayed:Need to be time managed, can't be content managed
Inspect the remaining configuration data for datasets, media families, backup schedules, and so forth to make sure that it migrated properly.
At this stage of the migration, you have reviewed the settings in the administrative domain and confirmed that they are correct. You can take this opportunity to configure additional Oracle Secure Backup settings.
In this section, you have an opportunity to modify your administrative domain configuration. For example, you can create new users. This section assumes that you have convenient access to Oracle Secure Backup Administrator's Guide, which provides detailed configuration instructions.
To configure additional domain settings:
Optionally, add classes that define different rights other than those found in the default classes installed by Oracle Secure Backup.
The section "Configuring Classes" in Oracle Secure Backup Administrator's Guide explains how to perform this task.
Add other Oracle Secure Backup users as needed. You way want to create users who can log in with limited rights.
The section "Configuring Users" in Oracle Secure Backup Administrator's Guide explains how to perform this task.
Edit your defaults and policies settings to custom configure them to your site.
The section "Configuring Defaults and Policies" in Oracle Secure Backup Administrator's Guide explains how to perform this task.
Configure a job summary schedule so that you can have backup status summaries produced and mailed at user-defined intervals.
The section "Configuring Job Summary Schedules" in Oracle Secure Backup Administrator's Guide explains how to perform this task.
Configure preauthorizations, database backup storage selectors, and media families needed for RMAN backups.
The section "Configuring RMAN and Oracle Secure Backup" in Oracle Secure Backup Administrator's Guide explains how to perform this task.
At this stage of the migration, the Oracle Secure Backup administrative domain is configured. You are now ready to begin creating backups schedules in preparation for normal backup operations.
Before resuming normal backup operations, ensure that your backup settings are configured correctly and the tape devices are prepared.
This section refers to administrative tasks that you can perform with the Oracle Secure Backup Web tool. If you need additional information about how to perform these tasks, refer to Oracle Secure Backup Administrator's Guide.
Check your media servers to confirm that their inventory status is current.
Log in to the Web tool as the admin user and perform the following steps:
In the home page, Click Manage and then Libraries.
In the Libraries page, select each library name and then select Inventory from Library Commands. Click Apply.
Check Force to force an inventory and then click OK.
In the Libraries page, select each library and click List Volumes.
Check that your backup schedules have the right host and device names specified to reflect any changes made to your configuration.
Oracle Secure Backup Administrator's Guide explains how to configure backup schedules. Follow these steps:
From the home page, click Backup and then Schedules.
Select each schedule and click Edit to display the properties and modify them if necessary.
Click Triggers to display the trigger information and modify it if necessary.
Restart the schedule daemon.
Oracle Secure Backup Administrator's Guide explains how to manage daemons. Follow these steps:
Click the Manage tab and then click Daemons.
In the Type list, select obscheduled.
In the Host list, select the administrative server.
Click Suspend and then Resume.
From the home page, Click Manage and then Jobs to make sure that backups scheduled for today are displayed.
From the home page, click Backup and then Backup Now to create a test backup job. For example, create a subdirectory called testbkup in your /tmp directory, copy a few small files to this directory, and then back up /tmp/testbkup.
From the home page, click Restore and then Backup Catalog. To test a restore operation, restore the backup that you created in the previous step.
You are now ready to resume normal backups operations with Oracle Secure Backup.
At this point the migration from Reliaty Backup to Oracle Secure Backup is almost complete. You can now uninstall Reliaty Backup from your Linux and UNIX hosts.
Note:
You do not need to uninstall Reliaty Backup from Windows hosts because you perform this task in "Uninstalling Reliaty Backup and Installing Oracle Secure Backup on Windows Clients".To uninstall Reliaty Backup from the Linux and UNIX hosts in your domain:
Log on as root to the host that was the administrative server for your Reliaty Backup domain.
Change into the Reliaty Backup root directory:
cd /usr/local/reliaty/backup
install/uninstallrb
Answer the questions asked by uninstallrb to remove Reliaty Backup from each Linux and UNIX host in your administrative domain. Be sure to start with your clients and uninstall your administrative server last.
Oracle Secure Backup Installation Guide provides a general description of how to obtain device information on Linux and UNIX when installing Oracle Secure Backup. You can find the information for your Reliaty Backup devices by examining the probedev.out file that you generated in Step 3 of "Preparing for Migration from Reliaty Backup to Oracle Secure Backup".
On Solaris, search the file for the string /var/adm/messages and look for a line that includes a target and LUN for the SCSI device. Example 1-1 shows an example of the relevant section on a Solaris system.
Example 1-1 probedev Output for Solaris
/var/adm/messages... Oct 13 09:52:25 sun_host unix: rb0: <EXABYTE EXB-85058SQANXR1> Oct 13 09:52:25 sun_host unix: rb0 at glm0: Oct 13 09:52:25 sun_host unix: target 0 lun 0 Oct 13 09:52:25 sun_host unix: rb0 is /pci@1f,0/pci@1/scsi@1/rb@0,0 Oct 13 09:52:25 sun_host unix: rb2: <EXABYTE EXB-10i> Oct 13 09:52:25 sun_host unix: rb2 at glm0: Oct 13 09:52:25 sun_host unix: target 1 lun 0 Oct 13 09:52:25 sun_host unix: rb2 is /pci@1f,0/pci@1/scsi@1/rb@1,0
In Example 1-1, the EXB-8505 tape drive uses SCSI target ID 0 and SCSI lun 0. The EXABYTE EXB-10i tape library uses SCSI target ID 1 and SCSI lun 0.
On Linux, search the file for the string /proc/scsi/scsi and look for a line that includes a target and LUN for the SCSI device. Example 1-2 shows an example of the relevant section on a Linux system.
Example 1-2 probedev Output for Linux
/proc/scsi/scsi... Attached devices: Host: scsi0 Channel: 00 Id: 03 Lun: 00 Vendor: ADIC Model: FastStor DLT Rev: 0115 Type: Medium Changer ANSI SCSI revision: 02 Host: scsi0 Channel: 00 Id: 04 Lun: 00 Vendor: Quantum Model: DLT4000 Rev: D98C Type: Sequential-Access ANSI SCSI revision: 02
In Example 1-2, the FastStor DLT Library is using SCSI target ID 03 and SCSI lun 0. The DLT4000 tape drive uses SCSI target ID 04 and SCSI lun 0.
In addition to specifying SCSI device information, you must also assign an Oracle Secure Backup logical unit number during the configuration process. This number, which is between 0 and 31, is used to generate unique device special file names during device configuration. Sample device special file names are /dev/obt0 and /dev/obt1.
Typically, Oracle Secure Backup logical unit numbers start at 0 and increment for each additional device of a given type, whether library or drive. Do not confuse the Oracle Secure Backup logical unit number with the SCSI LUN. The SCSI LUN is part of the hardware address of the device, whereas the Oracle Secure Backup logical unit number is a value you assign arbitrarily, that is used in creating the device special file name. The Oracle Secure Backup logical unit number is the first number queried for each device during the configuration process.
