Aller au contenu principal

Oracle Backup

XLServer provides deep integration with Oracle (standalone, RAC, and physical standby) to automate backups, snapshots, cloning, recovery, and data masking. This guide covers the full lifecycle for live Oracle databases in XLServer, from linking (golden image) to day-2 operations.

1) Prerequisites​

  • Oracle host(s) reachable from XLServer.
  • Database in ARCHIVELOG mode.
  • Valid Oracle user with backup privileges and access to catalog system views (see Appendix: Oracle User).
  • SSH access from XLServer to all database hosts (and all RAC nodes).
  • Oracle version ≥ 10gR1.
  • Sufficient free capacity in the XLServer datastore for the golden image + snapshots.
  • NFS client installed on database host(s).
Security tip

Do not attach production databases to the PUBLIC project.

Supported topologies

  • Standalone Oracle database
  • Oracle RAC (cluster database)
  • Physical Standby

Linking performs the initial full backup (the Golden Image Copy) into the XLServer datastore and registers the database as a Live Database.

  1. Open the Oracle database detail page (unlinked state).
    Non-linked Oracle DB

  2. Click Link Database (or Actions ▸ Link).

  3. Credentials → enter Oracle username/password → click CHECK CONNECTION.
    Proceed only if the connection succeeds.
    Check connection

  4. Linking Parameters

    • Mount Base: NFS mount point (e.g., /mnt/link)
    • RMAN Channels: number of channels (default 1, max 32)
    • Project: destination project (defaults to the environment’s project)
    • Default Snapshot Retention (days)
    • Archived Redo Logs Deletion Policy: e.g., delete when not needed for recovery/standby
    • Storage Optimization: enable compression and/or deduplication (space saving vs performance)
      Linking parameters

  5. Summary → verify settings.
    Linking summary

  6. Click CONNECT to start linking.

  7. Track job progress in Jobs.
    Linking progress

  8. When finished, the database shows as linked (Live Database).
    Linked DB detail

Note: Ensure the Oracle backup user has all required privileges. See Appendix: Oracle User. Also avoid attaching production DBs to PUBLIC.

3) Live Database Detail — Tabs & Layout​

The Live DB page has four tabs: Summary, Database Template, Data Masking, Performance.

3.1 Summary​

Database Parameters (key metadata & settings)

  • Vendor, Environment, Project
  • Oracle Home, RDBMS Version
  • DB Unique Name, DB ID
  • Character Set
  • Cluster / Physical Standby / Container flags
  • Backup Path (Mount Base)
  • Backup Strategy (if assigned)
  • Parallel (RMAN channels)
  • Quota (max clones; 0 = unlimited)
  • Snapshot Retention (default)
  • DB credentials
  • Generic Post Script Path (optional; executed on clone creation at target)
  • Connecting Mode (ONLINE)
  • Discovery (AUTO/MANUAL)
  • Linked On, Last Refresh Time, Last Sync Time
  • Created By

Database Services
List of service endpoints (auto-added at linking; can be managed manually).
Service list

Database Instances
All DB instances (1 for standalone; multiple for RAC).

Snapshots Calendar
Shows snapshots; green = recoverable, red = failed.
Snapshots calendar

Database Settings Reference​

SettingDescriptionDefaultModifiable
ProjectProject the DB belongs toNo
EnvironmentHost/cluster the DB runs onNo
VendorAlways ORACLEORACLENo
DB Unique NameOracle unique DB nameNo
Oracle HomeORACLE_HOMENo
Database VersionRDBMS versionNo
Character SetDatabase charsetNo
DB IDDatabase identifierNo
Cluster DatabaseRAC indicatorNo
Physical StandbyStandby indicatorNo
Container DatabaseCDB indicatorNo
Backup PathBase NFS mount pathYes
Backup StrategyAttached strategy nameYes
ParallelRMAN channelsYes
QuotaMax clones (0 = unlimited)10Yes
Snapshot RetentionDefault retention (days)7 daysYes
Database TypeAlways “Live Database”Live DatabaseNo
DB UserOracle credentialsYes
Generic Post Script PathSQL to run on clone (target host)Yes
Connecting ModeONLINE (current release)ONLINENo
DiscoveryAUTO or MANUALAUTONo
Linked OnDate/time linkedNo
Last Sync TimeLast snapshot creation timeNo
Last Refresh TimeLast metadata refreshNo
Created ByXLServer user who added itNo

3.2 Database Template​

Attach a Database Template so future clones inherit preset parameters.
Actions: ATTACH TEMPLATE, MODIFY TEMPLATE, DETACH TEMPLATE.
Attach template

3.3 Data Masking​

Attach Data Masking Templates so clones can mask sensitive data automatically.
(Full workflow in section 6. Data Masking.)

3.4 Performance​

Operational insights:

  • Snapshots for the last 7 days
    Snapshots list (last 7 days)
    “See all” view with more details:
    Snapshots detail list
  • KPI mini-cards: Disk Usage, Compression, Deduplication, RPO
  • Backup duration trends (last day / 7 days / 30 days)
    Backup performance
  • Storage breakdown & health pies
    Pie charts
  • Time-series: Backup Size, DB Size, Compression Ratio, Backup Duration
    Performance lines

4) Day-2 Operations (Actions Menu)​

4.1 Snapshot (Incremental Sync + Snapshot)​

Creates an incremental backup (merged into the golden image) and a ZFS snapshot.

  • Actions ▸ Snapshot → confirm.
    Snapshot confirmation
  • Track progress in Jobs.
    Snapshot progress
  • Browse snapshots via calendar (click the day to list):
    Snapshot list
  • View snapshot detail:
    Snapshot detail

From a snapshot’s cog menu you can:

  • Create Virtual Database
  • Create Physical Database
  • Mount snapshot (source env)
  • Restore
  • Delete (only if unused and not the last snapshot)
  • Close
Snapshot optimization

Configuring Block Change Tracking (BCT) on live database will help to create snapshot quickly.

4.2 Backup Archivelogs​

Creates a snapshot after backing up archived redo logs.

  • Actions ▸ Backup Log → confirm.
    Backup log confirmation

A new snapshot is created when the archivelogs backup finishes.

4.3 Refresh (Metadata only)​

Refreshes database metadata/parameters without creating a snapshot.

  • Actions ▸ Refresh → confirm.
    Refresh

4.4 Create Virtual Database (Instant Clone)​

  • Actions ▸ Create Virtual Database to clone up to the latest snapshot.
  • To clone from a specific snapshot, open that snapshot’s detail and use its cog menu.

See Database Cloning chapter for the full wizard and parameters.

4.5 Create Physical Database​

Same entry points as virtual clone, but creates a full, independent copy.

See Database Cloning chapter.

4.6 Mount Snapshot (Source Environment)​

Mounts snapshot contents on the source environment for manual inspection or recovery tasks.

Important: Mounting creates a staging clone; backups are blocked while it is mounted. Unmount as soon as finished.

See Database Recovery chapter.

4.7 Restore​

Restores the live DB to the latest snapshot (from Actions menu) or to a selected snapshot (from snapshot cog).

See Database Recovery chapter.

4.8 Disable / Enable​

  • Disable: blocks operations (e.g., for maintenance; prevents backups and cloning).
  • Enable: re-allows operations.

4.9 Delete Live Database​

Actions ▸ Delete → confirm.
Delete live DB

You cannot delete a live DB while it still has clones. Delete clones first.

5) Editing Settings​

5.1 Edit a Single Setting​

Click the pencil next to a setting (e.g., Quota), change the value, VALIDATE.
Edit quota

5.2 Bulk Edit​

Click EDIT SETTINGS, modify multiple fields, SAVE (or CANCEL).
Bulk edit settings

5.3 Change DB Credentials​

From the live DB page, click the pencil near credentials, enter Username/Password, VALIDATE.
Change DB credentials

If credentials are invalid, you’ll receive an error.

6) Data Masking​

XLServer supports:

  • Column-level masking via templates (e.g., names, emails, SSNs).
  • Whole-table shuffling (preserve distributions while anonymizing).

Masked data is applied during clone creation.

6.1 Column-Level Masking​

  1. Data Masking tab → ADD TEMPLATE.
  2. Enter DB credentials → CHECK CONNECTION.
    DM: check creds
  3. Select a table.
    DM: select table
  4. Select columns to mask → click + to add a rule/template.
    DM: select columns
  5. Choose a template and fill required parameters → VALIDATE.
    Attach template to column
  6. Confirm the rule shows as attached.
    Column shows attached template
  7. Repeat for all sensitive columns → Next → review → FINISH.
    Review

All attached templates list under Data Masking.
Templates list

  • To remove: select rows → REMOVE TEMPLATE.
  • To edit: click the pencil.

6.2 Whole-Table Shuffling​

  1. SHUFFLING DATA → enter DB creds → CHECK CONNECTION.
    Shuffle: creds
  2. Choose table.
    Shuffle: table
  3. Define up to three Column Sets (each set can contain multiple columns).
    Shuffle: column set
  4. Review & FINISH.

Shuffling definitions appear in the SHUFFLING DATA grid.
Shuffle list

  • To edit: open SHUFFLING DATA again and modify.
  • To remove a set: click the trash icon for that row.

7) Manage Database Services​

Services are the endpoints XLServer uses to connect to the Oracle database.

  • View services in Summary ▸ Services.
    Service list

Add a Service​

Click + (top-right of Services card) and provide:

  • Host Address
  • Port Number (default 1521)
  • Service Name
    Add service

Remove a Service​

Click the trash icon next to a service → confirm or cancel.
Delete service

At least one service must remain; deleting the last one is not allowed.

8) Manage Snapshots​

Use the Snapshots Calendar to navigate:

  • Green dots = recoverable snapshots, red = failed.
  • Click a day to list all snapshots on that date.
    Calendar
  • Click a snapshot to open detail.
    Snapshot detail

From the snapshot cog menu:

  • Create Virtual Database
  • Create Physical Database
  • Mount snapshot
  • Restore
  • Delete (only if unused and not the last)
  • Close

9) Backup Strategy (Protection Policies)​

To meet your SLA/RPO/RTO, attach a Backup Strategy to the live DB. If none fits, create a custom one.
See Backup Strategy Management.

Assign a Backup Strategy​

Open the live DB page → click the Backup Strategy pencil:

  • Choose a strategy from Backup Strategy list.
  • Enable Archivelogs Backup (optional), then:
    • Set Run every X hours (interval)
    • Set Archivelogs snapshot retention
    • Choose Days of week
      Assign strategy

Modify Strategy​

Open the same dialog:

  • Pick another strategy, or toggle archivelogs backup.
    Modify strategy

Remove Strategy​

Select No protection from Backup Strategy list.
Remove strategy

10) Performance Analytics​

Use the Performance tab to:

  • Check snapshot cadence & health
  • Monitor backup duration
  • Verify compression/dedup efficiency
  • Track storage usage vs snapshots
  • Keep RPO in check

(See screenshots in 3.4 Performance above.)

12) Appendix: Oracle User (Required Privileges)​

To allow XLServer to perform backups, snapshots, and recovery operations, you should create a dedicated Oracle database user with the correct privileges.
This user will be used when linking and snapshot the database in XLServer.

Example SQL Script​

-- Connect as SYSDBA
sqlplus / as sysdba

-- Create the backup user
CREATE USER xlsbackup IDENTIFIED BY strong_password
  DEFAULT TABLESPACE users
  TEMPORARY TABLESPACE temp
  QUOTA UNLIMITED ON users;

-- Grant required privileges
GRANT CONNECT, RESOURCE TO xlsbackup;
GRANT RECOVERY_CATALOG_OWNER TO xlsbackup;

-- Grants for backup operations
GRANT SYSBACKUP TO xlsbackup;

-- Grants for catalog access
GRANT SELECT_CATALOG_ROLE TO xlsbackup;

-- Additional privileges (required for RMAN and snapshots)
GRANT CREATE SESSION TO xlsbackup;
GRANT SYSDBA TO xlsbackup;

-- (Optional) For clustered/RAC environments:
GRANT SYSOPER TO xlsbackup;