By default, after the Metallic agent is installed, database instances are automatically discovered.
Autodiscovery depends on the following conditions:
-
Oracle database services must be running prior to configuring backups from the Metallic Configuration wizard. If database services are not running then instance discovery fails.
-
By default, autodiscovery runs once every 24 hours. If you want to immediately discover databases, see Discovering Databases Manually or Automatically.
-
Metallic uses instances that are defined in the Oracle oratab file, which is created by Oracle at installation and which functions as a database registry file. Verify that this file is accurate and updated. On Solaris systems, this file is normally located in the /var/opt/oracle directory. On Linux/UNIX systems, it is located in the /etc directory.
-
Metallic discovers single (non-clustered) Oracle instances that are in the NOMOUNT, MOUNT, or OPEN state. It does not discover database instances that are shut down.
Instances that are automatically discovered are configured with the "/" (slash) character as the connect string. However, for out-of-place restores and duplicating a database in a cloud environment (AWS, Azure, or OCI), the connect string for the target database instance properties must be configured in USERNAME/PASSWORD@SERVICENAME format. Also, the target database instance properties must be configured in this format if you will be running data masking on the target machine in a cloud environment.