Instance Properties (Database)

Oracle | DB2 | SQL

This tab is available after a successful discovery operation and the fields are displayed as per the Relational Database Management System (RDBMS) with which the Docbase is created.

Prior to configuring the Documentum iDataAgent, the SQL iDataAgent should be installed and configured if the database is not present on the primary Documentum Content Server host.

Use this tab to specify the SQL database properties. The SQL database contains the database and log files to be backed up by the Documentum iDataAgent.

Client

Enter the name of the client computer on which the database has been installed. This could be the same or a different client computer on which the Documentum iDataAgent has been installed. Use the dropdown box and select from the list of client computers.

iDataAgent

Displays the type of database iDataAgent that will be backed up by the Documentum iDataAgent. This is automatically populated after Discover has been selected in the General tab.

Instance

Enter the name of the SQL instance that is created for the database.

Home

Enter the path to the database installation Home directory.

User Account

Click Configure Password to specify the application User account used by the system to perform all Data Protection and Recovery operations for the SQL instance.

The Documentum iDataAgent requires an SQL account with sufficient privileges to perform the following:

The SQL Server iDataAgent requires a Windows user account that has sufficient privileges for the software to:

  • Perform backups and restores
  • Access the Windows registry
  • Stop or start the SQL Server services.

By default, the local system account is used. The following table illustrates the requirements for a user-defined account:

If the SQL Server Is The User Account Should Be:
Member of a WorkGroup
  • Local Administrator of the computer on which the SQL Server resides, like computer_name\user1.
  • Member of the SQL sysadmin fixed server role.
Member of a Domain An account other than the Domain Administrator account that has Administrator and SQL sa privileges. The account should have interactive logon rights on the computer where the SQL Server resides.

Initially, the user credentials are not provided during the agent installation and by default, the local system account is used. You can change the user account at the CommCell, client computer group, agent, and instance levels. Accounts configured at each level will be used for all entities within that level as described in the following sections.

You can use any SQL account that satisfies the account requirement or use a user account from which SQL Server services are running by providing their respective login credentials.

In order to access the SQL Server databases to perform data protection and recovery operations, the SQL sysadmin rights are required.

For more information about the SQL sysadmin privileges, go to the Microsoft Support website and search for Microsoft KB article 2926557, SQL Server VDI backup and restore operations require Sysadmin privileges.