X

An Oracle blog about Database and Grid Infrasructure Maintenance

  • April 15, 2020

(FPPBR) Fleet Patching and Provisioning - Backup & Restore Utility

Ruggero Citton
Product Development Architect

Oracle Fleet Patching & Provisioning (formerly known as Oracle Rapid Home Provisioning) presents a standard method for provisioning, patching and upgrading the Oracle Database estate in a unified manner across an entire enterprise. Oracle FPP solution standardizes and simplifies software distribution and lifecycle management.

(see the whitepaper for a better understanding at https://www.oracle.com/technetwork/database/database-technologies/cloud-storage/acfs/learnmore/oraclefpp-19c-wp-5486894.html)

 

FPPBR - Backup & Restore Utility

It's a new tool to perform the Fleet Patching and Provisioning Server (RHPS/FPPS) Backup and Restore, either on the same or different hardware.

You can get FPPBR from MOS <FPPBR Fleet Patching and Provisioning - Backup & Restore Utility DOCID:2566782.1>

FPPBR is offering following operations:

  • backup - Fleet Patching and Provisioning Server Backup
  • restore - Fleet Patching and Provisioning Server Restore
  • diff - Fleet Patching and Provisioning Server Check differences
  • query - Fleet Patching and Provisioning Server Query

FPPBR - Backup

Usage:
fppbr backup --destination <destination path>
            [--compression <compression level 1..9>] [--force] [--limited]

fppbr OPTIONS
  --destination <destination path> - It's the destination path for the backup
  --compression - GoldImage compress level (1..9)
  --force - It'll make the gold image compress file also if already present
  --limited - It'll compress gold images with limited cpu/io resource

Example:

fppbr backup --destination /mnt/nfs
fppbr backup --destination /mnt/nfs --compression 0
fppbr backup --destination /mnt/nfs --limit

This command will perform the FPP Server backup collecting the FPP server and storage configurations and compressing the goldimages. If the goldimage is already present it will skip it (incremental backup).

FPPBR - Restore

This command will perform the FPP Server restore

Usage:
fppbr restore --source <destination path>
             [--force] [--limited]

fppbr OPTIONS
  --source <source path> - It's the source path for the restore
  --force - It'll recreate the FPP server and ACFS gold iamge location
  --limited - It'll uncompress gold images with limited cpu/io resource

Example:
  fppbr restore --source /nfs/backup
  fppbr restore --source /nfs/backup --limited

FPPBR - Diff   

This command will perform a "diff" between the "rhpctl query" command outputs done post backup (.bck) and post restore (.res) showing differences

Usage:
fppbr diff --source <source path> [--query]

fppbr OPTIONS
  --source <source path> - It's the source path for the backup
  --query - It will diff between data query files at backup and query time

Example:
  fppbr diff --source /mnt/nfs

FPPBR - Query

This command is executing several rhpctl query commands collecting most important configurations details (the file extension is '.out'). Using '-details' it will perform also the rhpctl query command for the related object

Usage:
fppbr query --destination <destination path>
           [--details]

Example:
  fppbr query --destination /mnt/nfs
  fppbr query --destination /mnt/nfs --details

Resource Limits

Due to the nature of the actions performed automatically by fppbr such compress files (CPU bound)/copy files (IO bound) we can limit, on stressed fpp server, the resource pressure (CPU/IO) leveraging on "-limit" command option. Without "-limit" fppbr will use unlimited resource, with "-limit" fppbr will limit CPU/IO usage.

FPPBR Limitations

  • The restore is possible only on a cluster where the "clustername" is the same of the cluster source backup.
  • FPPBR is working with GI 12.2, 19c and above
  • With 19c GI, you must execute "fppbr backup/restore" from the node where the management database (-MGMTDB/GIMR) is running

 

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.