BEFORE YOU BEGIN
Check before you begin
This guide covers the inspected Linux SQL → Oracle / lin_oracle agent workflow. Instance identity, SID and DB unique name are distinct. RMAN, archive-log/PITR, RAC, Data Guard, PDB/CDB and TDE recovery were not validated end to end in this inspection; generic SQL or VM backup does not establish the same support.
Visual/acceptance limit: this guide is based on local Agent Policy and restore templates plus available technical documentation. The ongoing Firefox page-reading issue prevented new SQL Server/Oracle captures in this inspection; PostgreSQL or another engine’s screenshot was not substituted. No instance/policy was created and no backup/restore or log-finalization operation was executed. The installed release and end-to-end data acceptance require separate validation.
- Engine, agent/master releases and instance identity
- Database scope, method and access privileges
- Full base, log chain and repository access
- Isolated destination, collisions and application acceptance
011. Record instance and database scope
Record Oracle release/edition, Linux and agent releases, SID, DB unique name, ORACLE_HOME and topology with the DBA. Plan initial acceptance on a small isolated test instance. For CDB/PDB or RAC, validate the actual protected scope with the technical team.
Expected resultThe selection and relevant acceptance evidence are recorded.
022. Verify agent and engine access
Validate the correct Linux Agent service, Oracle access, OS/DB identity, environment and repository capacity. Scope privileges and credential records with the DBA; keep passwords and wallet keys out of screenshots. A responsive agent does not establish successful discovery/backup.
Expected resultThe selection and relevant acceptance evidence are recorded.
033. Prepare a SQL policy for the correct engine
Open Home → Policies → Agent Policy → Create Agent Policy. Select the correct Agent, Policy Name and Storage. Under Policy Type → SQL choose Oracle. Do not substitute File Backup or Bare Metal for a database policy. If the instance list is empty, validate access before creating an arbitrary connection.
Expected resultThe selection and relevant acceptance evidence are recorded.
044. Match the instance and elements in Clients
Inspect the Oracle instance record and INSTANCES ELEMENTS list in Clients. Verify SID, DB unique name and selected elements match the intended database/container. Empty discovery or a timeout is not a completed selection; Add Instance alone is not proof of live access.
Expected resultThe selection and relevant acceptance evidence are recorded.
055. Define the method and log chain with the DBA
Validate the actual backup method, online/offline consistency, archive-log requirements and control-file/SPFILE scope for the installed release with the technical team. An Oracle menu entry does not establish RMAN or point-in-time recovery support. Include TDE/wallet and archive-log retention dependencies in an independent recovery plan.
Expected resultThe selection and relevant acceptance evidence are recorded.
066. Plan scheduling and initial backup acceptance
Check scheduling and retention actually exposed for the engine/method in Advanced Settings and Schedules. Compare Full-base and dependent log/differential/incremental-chain retention with capacity; do not assume every method applies to each engine. In an approved small test, record task result, repository output and catalog method together.
Expected resultThe selection and relevant acceptance evidence are recorded.
077. Complete database and application acceptance
Use the separate engine restore guide to validate database startup, schema, sample queries, row counts and application access on an approved isolated target. Active, Last Backup or a success notification alone is not content acceptance. Record backup identity, method, time and the required chain in the report.
Expected resultThe selection and relevant acceptance evidence are recorded.
COMMON QUESTIONS
Does a successful task mean the application is ready?
Not by itself. Engine integrity, required log chains, data queries and application access need separate validation; HA/topology acceptance is assessed separately.