| Oracle® Secure Backup Administrator's Guide Release 10.1 Part Number B14234-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Secure Backup Administrator's Guide Release 10.1 Part Number B14234-02 |
|
|
PDF · Mobi · ePub |
This chapter explains how to restore file system objects backed up by Oracle Secure Backup. This chapter contains the following topics:
See Also:
"Database Backup and Recovery" for an overview of Oracle Secure Backup restore functionality
Oracle Secure Backup Reference for a description of the restore commands in obtool
This chapter assumes that you have read "File System Restore Operations". You can restore file system data in the following ways:
By browsing the catalog
In this case, you browse the catalog to select the files to restore (see "Backup Catalog").
By identifying the media on which the backup is located
In a raw restore operation, you specify a backup image file number and the volume ID of the volume on which it is stored.
By using obtar
In this case, you use obtar to access tapes directly. It is recommended that only expert users restore files by means of obtar.
This chapter explains how to perform catalog-based and raw restore operations. Restoring files with obtar is considered an advanced practice.
The sequence of steps is basically the same for both catalog-based and raw restore operations.
Create a file system restore job as follows:
Log in to the administrative domain as admin or a user with the rights needed to browse and restore files. You need the following rights:
perform restores as privileged user right if you restore files in privileged mode or restore to an NDMP host.
perform restores as self right if you restore files in unprivileged mode.
browse backup catalogs with this access right set to a value other than none if you want to browse the catalog. The possible access values are privileged, notdenied, permitted, named, and none.
Identify the backups that you want to restore.
For a catalog-based restore, locate the files in the catalog. "Browsing the Backup Catalog" explains how to perform this task.
For a raw restore, identify the volumes and backup section file numbers from which to restore the backups. "Displaying Backup Sections" explains how to perform this task.
Create one or more restore requests.
To create catalog-based restore requests, see "Sending Catalog-Based Restore Requests to the Scheduler".
To create raw restore requests, see "Sending Raw Restore Requests to the Scheduler".
Note:
All restore requests that have not yet been sent to the scheduler persist until the background timeout expires. The background timeout value identifies the maximum idle time of certain
obtool background processes. See "Preferences" for more information.Delete the queued restore requests (if needed).
To remove a catalog-based restore request, see "Removing a Catalog-Based Restore Request".
To remove a raw restore request, see "Removing a Raw Restore Request".
Send the restore requests to the Oracle Secure Backup scheduler so that the requests become jobs and are eligible to run. The Oracle Secure Backup scheduler runs the jobs according to their priority.
To create catalog-based restore jobs, see "Sending Catalog-Based Restore Requests to the Scheduler".
To create raw restore jobs, see "Sending Raw Restore Requests to the Scheduler".
This section describes how to create a restore request by browsing a backup catalog. This section contains the following topics:
In the Restore page, click Backup Catalog to display the Backup Catalog page, which is shown in Figure 8-1. You can use this page to browse the catalog for backups of files and directories.
To browse the catalog and designate specific data to restore:
In the Browse Catalog page, select a host name from the Host Name list box. The host should be the one on which the data was originally backed up.
In the Data Selector box, select one or more data selectors. See Oracle Secure Backup Administrator's Guide for a description of valid values for data selectors. Note the following data selector options:
If you select backup ID, enter one or more comma-delimited backup IDs in the Backup ID text box. "Listing All Backups of a Client" explains how to obtain a backup ID from the list of backups for this client.
If you select as of date, enter a date and optionally a time in the As of date box. For example, enter 5/2.
If you select date range, enter the range in the Date range text box. For example, enter 2005/5/1-2005/5/31.
Select a View mode. See "Catalog View Modes" for a description of the inclusive and exact view modes.
In the Path box, you can optionally enter the path name of the directory to browse. If you do not enter a path, then Oracle Secure Backup displays the top-most directory in the client's naming hierarchy.
Click Browse Host.
Oracle Secure Backup displays the Browse Host page with the selected directory contents displayed.
Click a directory name to make it your current directory and view its contents. You can repeat this operation until you find the data to be restored.
The Web tool displays the contents of the selected directory, with the directory name in gray if you have visited it, in orange if you have not.
You can change the Data Selector at any time without leaving this page as follows:
Optionally, adjust the selections in the Data Selector list box.
Optionally, update the Backup ID, As of date, or Date range text boxes if any apply.
Click Apply.
Oracle Secure Backup redisplays the page with the new data selector applied. If the view mode is inclusive, it will look the same as the previous page. The instances of file system objects selected when you display properties, however, will reflect the new data selector setting.
You can change the View mode without leaving this page as follows:
Select either Inclusive or Exact view mode.
Click Apply.
Oracle Secure Backup applies the new view mode and redisplays the page.
In "Browsing the Backup Catalog", you located the data you want to restore. In this section, you specify various restore options in order to finalize the restore request.
To create a catalog-based restore request:
Check the box next to the name of each file system object you want to restore. By performing this action, you are requesting that Oracle Secure Backup restore each instance of the object identified by the data selector.
To learn the identity of those instances, click the adjacent properties button view to display the object's properties page. When you are done viewing the page, click Close.
Click Add.
Note:
You must click Add before leaving the page containing your check box selections. If you do not, then Oracle Secure Backup discards those selections.The New Restore page appears.
Optionally, enter an alternate path name for each file or directory to restore. For example, enter /tmp.
The original path name of each object you previously selected appears in lower left portion of this page. To its right is a text box in which you can enter the alternate path name. If you leave this box blank, then Oracle Secure Backup restores the data to its original path.
Caution:
Some NAS data servers, including Network Appliance's Data Ontap, limit your ability to rename restored data. If you try to violate that constraint, then the restore job fails.Optionally, select Device radio button to select a tape drive to use to perform the restore. By default, Oracle Secure Backup automatically selects the best drive.
Choose whether you want the restore to operate in unprivileged or privileged mode. Unprivileged mode is the default.
An unprivileged restore runs under your UNIX user identity or Windows account identity, as configured in your Oracle Secure Backup user profile (see "Configuring Users".) Your access to file system data, therefore, is constrained by the rights of the UNIX user or Windows account having that identity.
Note:
On UNIX systems, a privileged restore job runs under the root user identity. On Windows systems, the job runs under the same account identity as the Oracle Secure Backup service on the Windows client.Optionally enter one or more obtar options in the Obtar option(s) box. For example, -J enables debug output and provides a high level of detail in restore transcripts.
See Also:
Oracle Secure Backup Reference for a summary of
obtar optionsCheck the No high speed positioning box if you do not want to use available position data to speed the restore.
Click NDMP incremental restore to direct NAS data servers to apply incremental restore rules. This option applies only to NAS data servers that implement this feature. This option does not apply to file system backups created with obtar.
Normally, restore operations are additive: each file and directory restored from a full or an incremental backup is added to its destination directory. If files have been added to a directory since the most recent Oracle Secure Backup backup, then a restore operation will not remove the newly added files.
When you select NDMP incremental restore, NAS data servers restore each directory to its state in the last incremental backup image applied during the restore job. Files that were deleted prior to the last incremental backup are deleted by the NAS data service when restoring this incremental backup.
For example, assume you make an incremental backup of /home, which contains file1 and file2. You delete file1 and make another incremental backup of /home. After a normal restore of /home, the directory would contain file1 and file2; after an NDMP incremental restore of /home, the directory would contain only file2.
Click Replace existing files to overwrite any existing files with those restored from the backup image.
Alternatively, click Keep existing files to keep any existing files instead of overwriting them with files from the backup image.
If you are restoring to a Windows system, click Replace in use files to replace in-use files with those from the backup image. Windows deletes each in-use file when the last user closes it.
Alternatively, click Keep in use files to leave any in-use Windows files unchanged.
Click OK.
Oracle Secure Backup displays the Browse Host page. The restore request appears in the Restore items list box. Oracle Secure Backup should display the message "Success: file(s) added to restore list" in the Status area.
To create additional catalog-based restore requests, return to "Browsing the Backup Catalog".
This section explains how to remove a catalog-based restore request that you have created, but have not yet sent to the scheduler.
To remove a catalog-based restore request:
In the Backup Catalog page, select any host from the Host Name list.
Click Browse Host.
Oracle Secure Backup displays the Browse Host page.
In the Restore items list, select the restore request you want to remove.
Click Remove.
Oracle Secure Backup redisplays the page. The restore request you selected no longer appears in the Restore items box.
This section explains how to send all pending catalog-based restore requests to the scheduler.
To send catalog-based restore requests to the scheduler:
In the Backup Catalog page, select any host from the Host Name list box.
Click Browse Host.
Oracle Secure Backup displays the Browse Host page.
Click Go.
The Web tool sends each restore request that appears in the Restore items box to the scheduler.
A message appears in the Info bar for each request acknowledged by the scheduler. For example:
1 catalog restore request item submitted; job id is admin/240.
Oracle Secure Backup deletes each restore request upon its acceptance by the scheduler. As a result, the Restore items list box is empty upon completion of the Go operation.
Display the transcript of the job to ensure that it completed successfully. See "Displaying Job Transcripts" to learn how to display job output.
This section explains how to obtain a detailed listing of all backups of a client.
To list all backups of a client:
From the Backup Catalog page, select any host from the Host Name list box.
Click Browse Host.
Oracle Secure Backup displays the Browse Host page.
Click List Host Backups. A properties page appears.
This section explains how to restore data without using a backup catalog. This section contains the following topics:
In the Restore page, click Directly from Media to display the page shown in Figure 8-2. You can use this page to perform a raw restore operation.
To perform a raw restore of file system objects, you must know the following:
The absolute path names of file system objects you want to restore
The identity (volume ID or barcode) of the tape volumes to which they were backed up
To create a raw restore request:
In the Directly from Media page, click Add.
The Options page appears.
In the Device section, you can optionally click Device to select a tape drive to use for the restore operation. By default, Oracle Secure Backup automatically selects the best drive.
Choose whether you want the restore to operate in unprivileged or privileged mode. Unprivileged mode is the default.
In the File Number text box, enter the backup image file number from which to restore data. See "Volume Sets" to learn about file numbers.
In the Volume ID(s) box, enter the first volume ID from which to begin data restore. See "Volume Sets" to learn about volume IDs.
Optionally, enter the volume tag of the first volume from which to begin restoring in the Tag(s) text box. As explained in "Volumes", tag is the machine-readable barcode affixed to the volume.
Note:
Enter a Volume ID, a tag, or both. You cannot leave both fields blank.Optionally enter one or more obtar options in the Obtar option(s) box.
See the Oracle Secure Backup Reference for details on obtar options.
Check NDMP incremental restore to direct certain NAS data servers to apply incremental restore rules.
Normally, restore operations are additive: each file and directory restored from a full or an incremental backup is added to its destination directory.
When you select NDMP incremental restore, NAS data servers that implement this feature restore each directory to its exact state as of the last incremental backup image applied during the restore job. Files that were deleted prior to the last incremental backup are deleted by the NAS data service upon restore of that incremental backup.
Click Replace existing files to overwrite any existing files with those restored from the backup image.
Alternatively, click Keep existing files to keep any existing files instead of overwriting them with files from the backup image.
If you are restoring to a Windows system, click Replace in use files to replace in-use files with those from the backup image. Windows deletes each in-use file when the last user closes it.
Alternatively, click Keep in use files to leave any in-use Windows files unchanged.
Select All to restore the entire contents of the backup image file you selected.
Alternatively, select File to restore a specific file or directory. If you select File, then do the following:
Enter the name of the file or directory to restore in the text box to the right of the File radio button.
If you know the position of the file in the backup image as reported previously by Oracle Secure Backup, then enter it in the Position box. If you do not, leave this field blank.
In the To host list, select a host to which to restore the data.
In the Alternate path text box, enter a path name if you want to restore data using a different name than the one that was saved.
For example, assume that you want to restore the home directory for brhost2. The absolute path for the directory on the brhost2 file system was /export/home/brhost2. To restore to an alternate directory, enter the new path and the desired final directory name. For example, you could restore /export/home/brhost2 to /tmp/brhost2-restored. The same technique works for individual files. For example, you could restore /export/home/brhost2/.cshrc to /tmp/.cshrc-restored.
Click OK to accept your selections or Cancel to discard them.
Oracle Secure Backup returns you to the Restore from Media page. If you clicked OK, the raw restore request you just made appears in the list box. Oracle Secure Backup displays the message, "Success: restore task created" in the Status area.
This section explains how to remove a raw restore request that you have created, but have not yet sent to the scheduler.
To remove a raw restore request:
In the Directly from Media page, select the request that you want to remove.
Click Remove.
Oracle Secure Backup redisplays the page. The restore request that you selected no longer appears in the list box.
This section explains how to send all pending raw restore requests to the scheduler.
To send raw restore requests to the scheduler:
In the Directly from Media page, click Go.
The Web tool sends each restore request that appears in the Restore from Media list box to the scheduler.
A message appears in the status area for each request acknowledged by the scheduler. For example:
raw restore request 1 submitted; job id is admin/7.
Oracle Secure Backup deletes each restore request upon its acceptance by the scheduler. As a result, the Restore from Media list box is empty upon completion of the Go operation.
Display the transcript of the job to ensure that it completed successfully. See "Displaying Job Transcripts" to learn how to display job output.
This section assumes that you have been making regular backups of the administrative server as recommended in "Backing Up Critical Data on the Administrative Server". This section describes the basic procedure for restoring the admin directory in the event of media failure or loss of the administrative server.
The instructions for installing Oracle Secure Backup on the administrative server are explained in "Loading and Installing the Oracle Secure Backup Software on Linux or UNIX" in Oracle Secure Backup Installation Guide. You should refer to this manual when reinstalling Oracle Secure Backup.
The sample output in the following procedure restores the administrative data on a UNIX host named ella. This host has an attached tape library that contains a single tape drive. Note that the sample output is often truncated or reformatted because of space constraints.
To restore the administrative data after a media failure:
If the administrative server is a Linux or UNIX media server, then gather the SCSI information needed to create the device special files. If you saved a print copy of this information with your backup volume, then you can use this saved information; otherwise, obtain the SCSI information as described in Oracle Secure Backup Installation Guide.
Run setup to load the Oracle Secure Backup software from the installation media. The following example loads Linux and UNIX packages:
# /cdrom/cdrom0/setup
Welcome to Oracle's setup program for Oracle Secure Backup. This
program loads Oracle Secure Backup software from the CD-ROM to a
filesystem directory of your choosing.
This CD-ROM contains Oracle Secure Backup version 10.1.060119.
Please wait a moment while I learn about this host... done.
Would you like to load the Oracle Secure Backup software into your
current directory /export/home/oracle/backup?
(Oracle recommends using /usr/local/oracle/backup as the Oracle
Secure Backup home)
A 'yes' answer proceeds to use the current directory [yes]:
- - - - - - - - - - - - - - - - - - - - - - - - - - -
You may load any of the following Oracle Secure Backup packages:
1. linux32 (RH 2.1, RHEL 3, RHEL 4, SuSE 8, SuSE 9)
administrative server, media server, client
2. solaris64 (Solaris 2.8 and later, SPARC)
administrative server, media server, client
Enter a space-separated list of packages you'd like to load. To load all
packages, enter 'all' [2]:
.
.
.
Loading of Oracle Secure Backup software from CD-ROM is complete.
You may unmount and remove the CD-ROM.
Would you like to continue Oracle Secure Backup installation with
'installob' now? (The Oracle Secure Backup Installation Guide
contains complete information about installob.)
Please answer 'yes' or 'no' [yes]:
Install the Oracle Secure Backup software, assigning this host the role of administrative server. Note that the following message is expected behavior: Error: can't connect to local observiced.
Welcome to installob, Oracle Secure Backup's UNIX installation program.
.
.
.
Please wait a few seconds while I learn about this machine... done.
Have you already reviewed and customized install/obparameters for your
Oracle Secure Backup installation [yes]? yes
Verifying that installation parameters are correct... done.
- - - - - - - - - - - - - - - - - - - - - - - - - - -
You can choose to install Oracle Secure Backup in one of two ways:
(a) interactively, by answering questions asked by this program, or
(b) in batch mode, by preparing a network description file
Use interactive mode to install Oracle Secure Backup on a small number
of hosts. Use batch mode to install Oracle Secure Backup on any number
of hosts.
Which installation method would you like to use (a or b) [a]?a
- - - - - - - - - - - - - - - - - - - - - - - - - - -
Oracle Secure Backup is not yet installed on this machine.
Oracle Secure Backup's Web server has been loaded, but is not yet configured.
You can install this host one of three ways:
(a) administrative server
(the host will also be able to act as a media server or client)
(b) media server
(the host will also be able to act as a client)
(c) client
If you are not sure which way to install, please refer to the Oracle
Secure Backup Installation Guide. (a,b or c) [a]?
Beginning the installation. This will take just a minute and will produce
several lines of informational output.
Installing Oracle Secure Backup on ella (solaris version 5.9)
You must now enter a password for the Oracle Secure Backup 'admin' user.
Oracle suggests you choose a password of at least 8 characters in length,
containing a mixture of alphabetic and numeric characters.
Please enter the admin password:
Re-type password for verification:
.
.
.
initializing the administrative domain
Error: can't connect to local observiced - error opening single sign on wallet
WARNING: administrative domain initialization failed (1) -- see the
message above.
generating links for admin installation with Web server
.
.
.
NOTE: The Oracle Secure Backup device driver has been successfully installed.
Is ella connected to any tape libraries that you'd like to use with
Oracle Secure Backup [no]? yes
If the administrative server is also a media server, then specify the SCSI information for the attached tape devices. The following example configures ella as an administrative server and specifies SCSI information for an attached tape library and tape drive:
How many Oracle Secure Backup tape libraries are attached to ella [1]?
Please describe each tape library by answering the following questions.
Oracle Secure Backup logical unit number [0]:
SCSI bus name-instance [glm1]:
SCSI target ID [3]: 1
SCSI lun 0-7 [0]:
Is the information you entered correct [yes]?
Is ella 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 ella [1]?
Please describe each tape drive by answering the following questions.
Oracle Secure Backup logical unit number [0]:
SCSI bus name-instance [glm1]:
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=glm1 obt0
/dev/obt0 created
NOTE: table for devlinks...
type=ddi_pseudo;name=ob;addr=1,0;minor=glm1 obl0
/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]? no
Installation summary: Installation Host OS Driver OS Move Reboot
Mode Name Name Installed? Required? Required?
admin ella solaris64 no no no
Oracle Secure Backup is now ready for your use.
Obtain the process ID for observiced and then terminate the process. For example:
# ps -auwx | grep observiced root 975 0.4 1.222336 5960 pts/2 S 14:00:36 0:02 observiced -s # kill -9 975 # ps -auwx | grep observiced #
Force a reinitialization of the administrative domain. Note that you need to specify a new password for the admin user. For example:
# obtool --initnewdomain --force Please enter a password for the "admin" user. Password: Password (again):
If the administrative server is a media server, then reconfigure your tape devices through the Web tool or obtool; otherwise you must add a separate media server to the domain that you can use to restore the data. The following example configures a tape library and tape drive attached to ella:
ob> lshost
ella admin,client (via OB) in service
ob> mkdev --type library --attach ella:/dev/obl0 ellalib
Info: added "mediaserver" role to host ella.
ob> mkdev --type tape --library ellalib --dte 1 --uselist all --attach
ella:/dev/obt0 ellatapeob> lshost
ella admin,mediaserver,client (via OB) in service
Force an inventory of the tape library and then list the volumes. For example:
ob> inventory --drive ellatape --force
ob> lsvol -L ellalib
Inventory of library ellalib:
in 1: occupied
in 2: occupied
in 3: occupied
in 4: occupied
in 5: occupied
in 6: occupied
in 8: occupied
in 9: occupied
in 10: occupied
in dte: occupied
ob>
Use the identifyvol command to populate the Oracle Secure Backup catalog with metadata about the volumes in the library. If you know that the volumes in the library do not contain a backup of the admin directory, then load the disaster restore volume that you store offsite (see "Backing Up Critical Data on the Administrative Server").
An identifyvol command of slots 1 through 9 reveals the following information about the contents of the volumes in the library:
ob> identifyvol --import -D ellatape 1-9 Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 1 full-000001 1 1 jfersten-sun2 0 2006/01/17 07:05:22 1 full-000001 2 1 jfersten-sun2 0 2006/01/17 08:41:05 1 full-000001 3 1 jfersten-sun2 0 2006/01/17 09:26:13 1 full-000001 4 1 jfersten-sun2 0 2006/01/17 09:28:17 1 full-000001 5 1 jfersten-sun2 0 2006/01/17 11:02:18 1 full-000001 6 1 ella 0 2006/01/20 14:49:54 1 full-000001 7 1 ella 0 2006/01/20 15:21:10 1 full-000001 8 1 ella 0 2006/01/23 15:16:25 End of volume; the next volume in the volume set is full-000001. Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 1 VOL000001 1 1 jfersten-sun2 0 2006/01/17 07:14:23 End of volume set. Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 5 offsite-000080 2 5 atreyu 0 2003/05/05 10:34:10 5 offsite-000080 3 1 bigguy 0 2003/05/06 02:10:29 5 offsite-000080 4 1 ivan 0 2003/05/06 03:39:06 5 offsite-000080 5 1 pikachu 0 2003/05/06 03:39:14 End of volume set. Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 1 test1-000002 1 1 jfersten-sun2 0 2005/12/16 08:57:42 End of volume set. Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 2 full-000002 8 2 ella 0 2006/01/23 15:16:25 End of volume set. Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 2 VOL000002 5 2 jfersten-sun2 0 2005/11/15 10:16:31 2 VOL000002 6 1 fez 0 2005/11/16 09:04:01 2 VOL000002 7 1 fez 0 2005/11/16 09:37:52 2 VOL000002 8 1 jfersten-sun2 0 2005/11/17 15:16:52 2 VOL000002 9 1 fez 0 2005/11/17 15:31:13 2 VOL000002 10 1 N nh4flrlab53 0 2005/11/18 13:24:21 End of volume set. Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 1 ella-OSB-home-000001 1 1 ella 0 2006/01/24 13:05:00 1 ella-OSB-home-000001 2 1 ella 3 2006/01/24 13:37:55 1 ella-OSB-home-000001 3 1 ella 0 2006/01/24 15:38:12 1 ella-OSB-home-000001 4 1 ella 3 2006/01/24 15:39:04 End of volume set. Seq Volume Volume Archive Client Backup Archive Create # ID Tag File Sect Host Level Date & Time 1 VOL000001 1 1 jfersten-sun2 0 2005/09/07 07:29:07 1 VOL000001 2 1 fez 0 2005/09/07 07:34:47 1 VOL000001 3 1 jfersten-sun2 0 2005/09/09 06:17:44 1 VOL000001 4 1 jfersten-sun2 0 2005/11/07 15:48:29 1 VOL000001 5 1 jfersten-sun2 0 2005/11/15 10:16:31 End of volume; the next volume in the volume set is VOL000001. Error: this tape is not labeled.
The tape from slot 7 has the volume ID prefix ella-OSB-home. This is the tape that contains the needed backups of the admin directory. At this stage, you cannot use obtool or the Web tool to restore files from tape, but you can use obtar to identify and restore the needed files.
Load the volume containing the admin directory into the tape drive. For example:
ob> loadvol -D ellatape 7
Use obtar -tvf to display the contents of the volume and obtain the path to your admin directory. The following sample output (which has been truncated) shows that the admin directory is in a nondefault location:
# obtar -tvf ellatape -F 1
drwxrwxrwxroot 0 Jan 20 08:48 2006 /export/home/oracle/backup-cdrom060119jwf/
.
.
.
drwxrwxrwxroot 0 Jan 20 08:48 2006
/export/home/oracle/backup-cdrom060119jwf/admin
Use obtar -x to restore the admin directory to a location that does not conflict with existing files or directories. As explained in "Restoring Data to a Different Location", you can use obtar -x with the -s syntax to specify a new path. The following example restores the admin directory from backup file 1 to /export/home (the backslash indicates line continuation and is not a literal):
# obtar -xvf ellatape -F 1 /export/home/oracle/backup-cdrom060119jwf/admin \ -s,/export/home/oracle/backup-cdrom060119jwf,/export/home, /export/home/admin/ /export/home/admin/config/ /export/home/admin/config/class/ /export/home/admin/config/class/admin /export/home/admin/config/class/operator . . .
If you have a full backup of this directory as well as incremental backups, then restore the incremental backups to the same directory. The following example restores an incremental backup of the admin directory from backup file 2 to /export/home (the backslash indicates line continuation and is not a literal):
# obtar -xvf ellatape -F 2 /export/home/oracle/backup-cdrom060119jwf/admin \ -s ,/export/home/oracle/backup-cdrom060119jwf,/export/home, Searching tape for requested file. Please wait... /export/home/admin/ /export/home/admin/config/ /export/home/admin/config/class/ /export/home/admin/config/dataset/ . . .
Also restore the /usr/local/ob directory to the same location. The following example restores an incremental backup of the admin directory from backup file 2 to /export/home:
# obtar -xvf ellatape -F 2 /usr/etc/ob -s ,/usr/etc,/export/home, Searching tape for requested file. Please wait... /export/home/ob/ /export/home/ob/.hostid /export/home/ob/wallet/ /export/home/ob/wallet/b64certificate.txt /export/home/ob/wallet/cwallet.sso . . .
Use the ps command to obtain the process IDs for the Oracle Secure Backup daemons (see "Daemons and Services") and then terminate them. For example:
# ps -awux | grep ob root 2041 0.1 1.322720 6368 pts/2 S 14:19:33 0:34 observiced -s . . . # kill -9 2014 2043 2062 2063 2064 2065 2066 2067 2100 2197 # ps -awux | grep ob #
Move the admin directory in the Oracle Secure Backup home to a new location and then move the restored admin directory to the Oracle Secure Backup home. For example:
# pwd/export/home/oracle/backup# mv admin admin.orig# mv /export/home/admin .
Follow the same procedure for the /usr/etc/ob directory:
# mv /usr/etc/ob /usr/etc/ob.orig# mv /export/home/ob /usr/etc/ob
Restart observiced as follows:
# /etc/observiced
Your environment is now restored to the point of your last backup of the admin directory. You can use obtool or the Web tool to review your administrative domain configuration.
|
 Copyright © 2006, Oracle. All rights reserved. Legal Notices |
|