Oracle RAC - Backup Exec server settings

Oracle RAC Solution · Config document · referenced from Backup Exec server and RAC backup

The settings made in the console of the Backup Exec server for the two nodes and the RAC database: the logon accounts, the list of Oracle servers, the servers added by hand, and the logon accounts and credentials corrected afterwards.

The settings

Logon accounts, step [7.1]: Configuration and Settings, Logon Accounts, Manage Logon Accounts, Add. Every account the server needs except root: the two local accounts of the nodes that are members of beoper, and the two database accounts.

Oracle server list, step [7.2]: Configuration and Settings, Backup Exec Settings, Oracle. Every node and the virtual node.

Servers that appeared by themselves after the agents were restarted, step [8.1]. Nothing was set here; the list is what the agents announced.

Servers added by hand, step [9.0], after advertising was switched off on the agents: Backup and Restore, Add Server, Linux Computer.

Logon account corrected, step [9.1]: for the virtual node Backup and Restore, double click on the virtual node, Properties, Logon Account; for ORADB01.example.net the notes write Backup and Restore, double click on the node, Logon Account, without Properties. Backup Exec had not kept the account of the Oracle server list. After it, step [9.2], both entries were refreshed with the Refresh button.

Database credential, steps [9.3] and [9.4]: Backup and Restore, double click on the virtual node RAC-clsopdb-1234567890, Credentials, Oracle Database clsopdb.

Operating system backup, step [9.5]: Backup and Restore, double click on the node, Logon Account and Credentials.

The state at the end

What does not fit together

• Steps [9.1], [9.2] and [9.5] name the nodes without -BCK, although those entries were removed in step [8.2] and the servers added in step [9.0] carry -BCK. The notes do not say whether the plain names stand for the -BCK entries or whether the plain entries existed again.
• Step [9.1] corrects only ORADB01.example.net, and step [9.2] refreshes only that node and the virtual node; ORADB02 is not mentioned in either.
• The node's logon account is set to local/oracle in steps [9.0] and [9.1] and to local/be in step [9.5]. The table of the final state takes the later one.
• Step [9.4] gives "use server's logon account" as the original value, although step [9.3] had set clsopdb/BACKUP_EXEC before it.
• The database is clsopdb in every setting, while the database itself answers CLSDB to select NAME from v$database.

The notes hold no backup job, selection, schedule or storage setting, so none is listed.

Checked against Backup Exec 25.1

Why the nodes were detected as Windows under their backup-network names is not explained by any document that was checked.