ODA Backup Restore Utility & ODA Rescue Live Disk

Oracle Database Appliance – Backup and Restore Utility
ODABR
Oracle Database Appliance – Rescue Live Disk
ODARescue
Oracle Product Development Architect
RACPack/MAA, Cloud Innovation and Solution Engineering Team
Ruggero Citton
@RuggeroCitton
https://www.linkedin.com/in/ruggerocitton
https://www.slideshare.net/RuggeroCitton

The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any
material, code, or functionality, and should not be relied upon in making purchasing decisions. The
development, release, timing, and pricing of any features or functionality described for Oracle’s
products may change and remains at the sole discretion of Oracle Corporation.
Safe harbor statement
Copyright © 2020, Oracle and/or its affiliates2

Product Development Architect
RACPack/MAA, Cloud Innovation & Solution Engineering Team
Ruggero Citton

5
4
3
2
1
ODARescue
ODABR DelSnap
ODABR Restore
ODABR Backup
ODA Backup & Restote
Agenda

ODA Backup and Restore - ODABR
ODA Administrators should create a backup before making significant changes to their
ODA System Node software:
 Application of ODA bundle patches
 Reconfiguration of significant operating parameters
 Deploying non-ODA RPMs or new versions of application software
With a backup ODA administrators can quickly restore a system disk if needed.

ODA Backup and Restore - ODABR
ODABR is a System Backup and Restore Utility that provides the ability to perform an
ODA System Node backup.
A backup is created using
• LVM (logical Volume Manager) snapshot feature of Linux.
and/or
• A remote backup version of the System Node is created with rsync (A fast, local and
remote file-copying), Linux’s feature.
This has been incorporated into a ‘single command’ to simplify the ODA backup and
restore process.

ODA node backup/recovery
ODA System Node Backup means backup:
• Root file system (/)
• Boot partition (/boot)
• opt file system: OAK/DCS,TFA,ASR (/opt)
• u01 file system: Grid Infrastructure, RDBMS binaries
• Grid Infrastructure OCR file

ODA System Node Backup/Restore With a Single Command
Usage:
odabr backup [-snap] [-destination <destination path> [-dryrun]]
[-osize <opt snap size>][-rsize <root snap size>][-usize <u01 snap size>]
odabr restore [-snap] [-boot] | [-source <source path> [-dryrun]]
odabr infosnap
odabr delsnap
where:
<destination path> - It's the destination path for the backup
<source path> - It's the source path for the restore
<root snap size> - It's the 'root' snapshot size in Gb (default 30 Gb)
<opt snap size> - It's the '/opt' snapshot size in Gb (default 60 Gb)
<u01 snap size> - It's the '/u01' snapshot size in Gb (default 100 Gb)
The destination/source can be one of the following:
PATH (local mountpoint)
ssh://USER@HOST:PATH
rsync://USER@HOST/PATH

ODABR Backup

Backup
ODABR: ODA Node Backup
ODABR backup is having a double functionality:
-snap (recommended functionality)
-destination ( rsync usage)
Usage:
odabr backup [-snap] [-destination <destination path> [-dryrun]]
[-osize <opt snap size>][-rsize <root snap size>][-usize <u01 snap size>]
where:
<destination path> - It's the destination path for the backup
<source path> - It's the source path for the restore
<root snap size> - It's the 'root' snapshot size in Gb (default 30 Gb)
<opt snap size> - It's the '/opt' snapshot size in Gb (default 60 Gb)
<u01 snap size> - It's the '/u01' snapshot size in Gb (default 100 Gb)
PATH (local)

Using "-snap" option, odabr will create a LVM snapshot for:
/dev/VolGroupSys/LogVolU01
/dev/VolGroupSys/LogVolOpt
/dev/VolGroupSys/LogVolRoot
The command option "-snap" is performing also
• a image copy of boot partition, storing the "/boot" partition image as
"/opt/odabr/out/hbi/boot.img”
• the Grid Infrastructure ocr backup as /opt/odabr/out/hbi/ocrbackup_<pid>.bck
Backup using «-snap»
ODABR System Node Backup to LVM Snapshot

By default ODABR creates LVM snapshots with the following default factory sizes:
• root LVM snapshot 30GB
• opt LVM snapshot 60GB
• u01 LVM snapshot 100GB
If for any reason, your LVM volumes are different in size and or you have less then 190Gb of
available free space, you could override these using these command options:
• -rsize
• -osize
• -usize
(Note: You must guarantee enough free space to keep all blocks changes, specify sizes in GBs)
ODABR Default Snapshot Sizes

ODABR System Node Backup with Remote Copy
Example – odabr backup –destination ssh://backup@remotehost:/backup
Creates copies at the remote location.
• Creates an LVM snapshot for "/u01", "/opt" and /or "root"
(based the user’s selection)
• Uses rsync to perform a physical copy of files to the
destination specified.
• This is important when there isn’t enough free space for
LVM Snapshot on the local volume and to keep the copy
remotely.
************************
ODA System Node backup
************************
choose the filesystem to backup:
0. All following filesystems
1. /boot filesystem
2. / filesystem
3. /opt filesystem
4. /u01 filesystem
5. exit
Enter your choice:
PATH (local mountpoint)

ODABR System Node Backup with Remote Copy
Example – odabr backup –snap –destination ssh://backup@remotehost:/backup
Creates local snapshots
Copies the files from that point-in-time snapshot to a remote location

ODABR System Node Infosnap
Example: odabr infosnap
Using "infosnap" option, odabr will show the snapshot existence, the status and the size %. If a
snapshot become inactive it will print a warning that it is not valid for a restore.

ODABR Restore

ODABR restore is having a double functionality:
-snap -boot (recommended functionality)
-source( rsync usage)
ODABR System Node Restore
Usage:
odabr restore [-snap] [-boot] | [-source <source path> [-dryrun]]
The source can be one of the following:
- PATH
- ssh://USER@HOST:PATH
- rsync://USER@HOST/PATH

• Using "-snap", LVM snapshots "remastering" (for "/u01", "/opt" and "root filesystem") are
executed and a reboot is required to make the changes
• It may be necessary to restore the /boot partition too. As "/boot" is not using LVM, it's
necessary to restore using '-boot' command option
Restore using «-snap»
ODABR: ODA Node Restore from LVM Snapshot
Usage:
odabr restore -snap [-boot]

Restore using «-source»
ODABR: ODA Node Restore from Remote Copy (for customers)
• Using "-source", the user is receiving the message:
*********************************
* Please contact Oracle Support *
*********************************
Host restore leveraging on rsync can be tricky as the file copy back could fail if
process are running

ODABR Suggested Workflow for Backup/Restore Snapshot:
It's best to take a backup on BOTH nodes in an ODA HA before you start the upgrade on any of the
nodes. It's also a good idea to check the disposition of your backup after it's created and before it's used
to restore to be certain it is not marked inactive.
1. odabr backup -snap -destination ssh://backup@remotehost:/backup (Takes a Snapshot and creates
a remote copy of the files)
2. odabr infosnap (Let's you verify the Snapshot is successful)
3. Apply patches or updates, if patches or updates have a problem and after all attempts to repair have
been unsuccessful, you can restore the System Node Snapshot following the remaining steps.
4. odabr infosnap (Make sure the backup has not been marked inactive. If not marked inactive
continue with the restore).
5. odabr restore -snap -boot (Restore from Snapshot, if the Snapshot restore should fail, CONTACT
ORACLE SUPPORT to restore from the remote file copies).
6. If patching or updating is successful you can reboot the node(s)

ODABR DelSnap

• Using "delsnap" option
 odabr will remove the LVM snapshots created for /u01, /opt, root filesystem.
• This should be done after the patching activity and once required post-
upgrade check has been done.
delsnap
ODABR Delete Snapshot (for customers)

ODABR Considerations and Limitations

• ODABR works on ODA BM(Bare Metal) only, but will work on both the OAK and DCS
stacks.
• If you need to perform a remote restore, Contact Support for assistance.
• It's important to understand that ODABR is NOT for backing up or restoring the Oracle
Database itself and you can't use ODABR to back up ASM (Automatic Storage
Management) content.
• When restoring an LVM snapshot and the previous Grid Infrastructure binaries, it may be
necessary to restore the OCR/Voting file as well. ODABR save the current OCR under
"/opt/odabr/out/hdi/ocrbackup_<pid>.bck". (Documentation explains how to restore the
OCR - (https://docs.oracle.com/en/database/oracle/oracle-
database/12.2/cwadd/managing-oracle-cluster-registry-and-voting-
files.html#GUID-648BB199-AFB9-416A-8438-E0331C255E78).
• ODABR cannot be used as a tool to perform a Grid Infrastructure downgrade
ODABR System Node Backup and Restore

• Distributed as an rpm
Install: rpm –Uvh /tmp/odabr-2.0.1-X.noarch.rpm (installs in: /opt/odabr)
Uninstall: rpm –e odabr-2.0.1-X/odabr2.0.1X.noarch.rpm
• Logging: Creates a log for all activities:
• Snapshot log: - /opt/odabr/out/log/odabr_<pid>.log
• Rsync Log: /opt/odabr/out/log/rsync_<pid>.log
ODABR Administration
Available on My Oracle Support
- ODABR a System Backup/Restore Utility (Doc ID 2466177.1)

• ODABR restore should be the last resort. Try to complete the complete the upgrade
manually if possible.
• Check infosnap before restore for warning. In case of having inactive snaps restore might
not be straightforward.
• Collect logs before restore otherwise Support can’t analyze why the upgrade attempt
failed.
Best Practices
ODABR

1. Boot ODA from ILOM using ODARescue ISO
2. At login prompt, you can login using "odalive"
user (root user is possible with password
"welcome1")
How To Use
ODARescue Live Disk

ODARescue commands (1/2)
ODARescue Live Disk
[odalive@localhost ~]$ odarescue
Usage: odarescue [ help | -h ]
odarescue lvmount
odarescue snapinfo
odarescue snapmount
odarescue snaprestore
[odalive@localhost /]$ odarescue lvmount
INFO: Checking 'LogVolRoot'
INFO: Checking 'LogVolOpt'
INFO: Checking 'LogVolU01'
INFO: Scanning VG
INFO: Activating LVM
INFO: Making required '/mnt/sysimage'
INFO: Mounting 'LogVolRoot'
INFO: Mounting 'LogVolOpt'
INFO: Mounting 'LogVolU01'
INFO: Mounting 'proc'
INFO: Mounting 'sys'
INFO: Mounting 'dev'
------------------------------------------
You can now execute 'sudo chroot /mnt/sysimage'
------------------------------------------
[odalive@localhost /]$ sudo chroot /mnt/sysimage
[odalive@localhost /]$ /opt/odabr/odabr
--------------------------------------------------------
odabr - ODA node Backup Restore
Author: Ruggero Citton <ruggero.citton@oracle.com>
RAC Pack, Cloud Innovation and Solution Engineering Team
Copyright Oracle, Inc. 2013, 2019
Version: 2.0.1-39
--------------------------------------------------------
Command option is missing!
One of following operation are possible:
- Backup operation:
backup
- Restore Operation:
restore
- Get LVM snapshot info:
infosnap
- Clean-up LVM snapshot:
delsnap
[odalive@localhost ~]$ odarescue snapinfo
--------------------------------------------------------
odarescue version 2.0 Dated 04-Jan-2019
--------------------------------------------------------
|-----------|-----------------------------------|------------|---------|
| root_snap | active destination for LogVolRoot | 30.00 GiB | 0.02% |
| opt_snap | active destination for LogVolOpt | 60.00 GiB | 0.01% |
| u01_snap | active destination for LogVolU01 | 100.00 GiB | 0.01% |
|-----------|-----------------------------------|------------|---------|

ODARescue commands (2/2)
ODARescue Live Disk
[odalive@localhost ~]$ odarescue
Usage: odarescue [ help | -h ]
odarescue lvmount
odarescue snapinfo
odarescue snapmount
odarescue snaprestore
[odalive@localhost ~]$ odarescue snaprestore
--------------------------------------------------------
odarescue version 2.2 Dated 21-Jan-2020
--------------------------------------------------------
INFO: Checking 'LogVolOpt'
INFO: Scanning VG
INFO: Activating LVM
INFO: Making required '/mnt/sysimage'
INFO: Mounting 'LogVolOpt'
WARNING: '/dev/VolGroupSys/LogVolOpt' already mounted
INFO: Checking boot backup image
INFO: Restoring boot backup image on '/dev/sda1'
SUCCESS: boot backup image restore done successfully
INFO: umount 'LogVolOpt'
INFO: Checking 'root_snap'
INFO: Checking 'opt_snap'
INFO: Checking 'u01_snap'
INFO: Restore LVM snapshot 'root_snap'
SUCCESS: LVM snapshot 'root_snap' restored done successfully
INFO: Restore LVM snapshot 'opt_snap'
SUCCESS: LVM snapshot 'opt_snap' restored done successfully
INFO: Restore LVM snapshot 'u01_snap'
SUCCESS: LVM snapshot 'u01_snap' restored done successfully
----------------------------------------------
Please reboot the host to activate the changes
----------------------------------------------

ODARescue configure_firstnet
ODARescue Live Disk
[odalive@localhost ~]$ configure_firstnet
Usage:
configure_firstnet add -i <Interface>
-ip <IPv4 address>
-n <Netmask>
-g <Gateway>
configure_firstnet del -i <Interface>
configure_firstnet list
Example:
configure_firstnet add -i eth0
-ip 10.10.100.21
-n 255.255.255.0
-g 10.10.100.1

• ODABR a System Backup/Restore Utility (Doc ID 2466177.1)
• ODRescue Live Disk (Doc ID 2495272.1)
ISO is available via Patch 29214531
Reference
 purgeLogs: Cleanup traces, logs in one command (Doc ID 2081655.1)

Ruggero Citton (Ruggero.Citton@oracle.com)
Oracle Product Development Architect
@RuggeroCitton
https://www.linkedin.com/in/ruggerocitton
https://www.slideshare.net/RuggeroCitton

ODA Backup Restore Utility & ODA Rescue Live Disk

ODA Backup Restore Utility & ODA Rescue Live Disk

More Related Content

What's hot

Similar to ODA Backup Restore Utility & ODA Rescue Live Disk

Recently uploaded

ODA Backup Restore Utility & ODA Rescue Live Disk