Instances - MySQL - How To

Topics | How To | Related Topics

Create an Instance

Modify an Instance

Delete an Instance

Browse the Latest Data

Change the Home Directory

Change the Archive Log Index File

Change the Configuration File

Change the Socket File

Change Account for Accessing Instances

Select a Storage Policy for Log Backups

Create/Modify an Instance

Before You Begin

• For the Oracle, Oracle RAC or SAP for Oracle iDataAgent, if you have custom SQL settings, you must turn off these settings to ensure that the instance browse works correctly and that the instance status is correctly fetched. To do this, create and edit the cvlogin.sql file with the appropriate contents at ORACLE_HOME/sqlplus/admin. For example, run the following command:

  edit file $ORACLE_HOME/sqlplus/admin/cvlogin.sql

  Then include the following contents in the cvlogin.sql file:

  set heading on;

  set pause off;

Required Capability: See Capabilities and Required Actions

To create/modify an Instance

1. To create an instance, from the CommCell Browser, locate the correct client computer node, and right-click the agent node for which you want the new instance created, click All Tasks, and then click New Instance from the shortcut menu.

   To modify an existing instance, from the CommCell Browser, right-click the instance you want to modify, and then click Properties from the shortcut menu.

2. From the General tab, enter the name (up to 32 characters) for the instance. In addition, provide the required access information for this instance.

   For various iDataAgents, you can add/modify an application/database user account. See the appropriate section as follows in User Accounts and Passwords for more information:

   • DB2 iDataAgent
   • Informix iDataAgent
   • Microsoft SQL Server iDataAgent
   • Oracle iDataAgents (Oracle, Oracle RAC, SAP for Oracle)
   • Sybase iDataAgent
   • MySQL iDataAgent
3. If your agent uses the Details tab, enter the required database connect string and other optional parameters.
   • For the Oracle, Oracle RAC and SAP for Oracle iDataAgents, see the Oracle iDataAgents section in User Accounts and Passwords for more information.
4. From the Storage Device tab, select storage policy copies to be used for, as applicable, data backups, command line data backups and log backups. Within these tabs you can click Data Paths to display the details of the data paths associated with the primary storage policy copy of the selected storage policy.
5. If your agent uses the Software Compression tab, and you want to enable software compression for the selected backups, click the tab and select the option appropriate to your environment.
6. If you want to enable data encryption, from the Encryption tab select encryption settings for third-party or RMAN command line backups.
7. Click OK to save the instance.
8. A message advises you to schedule backups for your new instance. It is recommended you elect to set a schedule now. You can also associate this instance with an All Agent Types schedule policy (which is automatically created by the system, or can be a user defined Data Protection schedule policy). If you have already associated a schedule policy at a previous level (Agent, Client, or Client Computer Group) the schedules defined in the Schedule Policy will be automatically applied to the new instance. See Schedule Policy for more information.
   • For agents that offer an OK option, click OK to acknowledge the message. This procedure is now complete.
   • For agents that offer Yes and No options to this message, click No if you don't want to create a backup schedule at this time, and this procedure is complete. If you click Yes, a dialog box prompts you to back up all subclients of this instance.
9. Click Yes. The Backup Options dialog box appears, which allows you to create the necessary schedules.
10. From the Backup Options dialog box, select the type of backup that you want to schedule.
11. If you want to access Advanced Backup Options, click Advanced.
12. After selecting the backup type and any advanced options, click OK. The Schedule Details dialog box appears.
13. From the Schedule Details tab of the Schedule Details dialog box, select the scheduling options that you want to apply, then click OK.

NOTES

• A default subclient is created for the Oracle instance, which includes all the objects in the instance. When you are done with this procedure, open the Subclient Properties dialog box for the default subclient and verify that the Resync Catalog option available in the Backup Arguments tab is selected. This would help you to successfully perform a full system restore in the event of destroyed or damaged client.
• After creating the instance for DB2, you can now create one or more Backup Sets for this instance.

Modify an Instance

Required Capability: See Capabilities and Required Actions

To modify an Instance

1. From the CommCell Browser, right-click the instance you want to modify, and then click Properties from the shortcut menu.
2. Click the General tab of the Instance properties box to change the required access information for this instance.
3. If your agent uses the Accounts tab, use this tab to specify the Windows account used by the system. For MySQL iDataAgent, use this tab to specify the MySQL Server user account.
4. If your agent uses the Restore View Names tab, use this tab to enter or modify a list of text patterns for the view through which the system displays a database's data documents when you browse.
5. If your agent has the Security tab, you can view CommCell resource associations to enable or disable user groups that can perform system operations on associated resources.
6. For an Oracle instance, click the Details tab to change the database connect string and other optional parameters.
7. For an Oracle RAC instance, go to the next step. Otherwise, go to Step 12.
8. Click the Details tab, and type or select values for the fields at the bottom of the dialog box as appropriate. For the DB2 DPF instance, to associate a database partition with a different client, click the affected partition in the DB2 Partition Clients field, click Modify, and click from the list in the Edit Directory Share Name Pair dialog box the name of the new client for the partition. Then click OK.
9. Click the Oracle instance (Client/Instance/Status) that you want to modify. Then click Modify.
10. In the Update Instance dialog box, update the desired field values by typing or browsing as appropriate. Then click OK.
11. Repeat the previous two steps for each Oracle instance that you want to modify.
12. From the Storage Device tab(s), select storage policy copies to be used for, as applicable, data backups, command line data backups and log backups. Within these tabs you can click Data Paths to display the details of the data paths associated with the primary storage policy copy of the selected storage policy.

    For the MySQL iDataAgent, select the storage policy for the log backups from the Log Backups tab.

13. If your agent uses the Software Compression tab, and you want to enable software compression for the selected backups, click the tab and select the appropriate option.
14. If you want to enable data encryption, from the Encryption tab select encryption settings for third-party or RMAN command line backups.
15. Click OK to save the configuration changes.
16. A message advises you to schedule backups for your new instance. It is recommended you elect to set a schedule now. If you click No, this procedure is now complete. If you click Yes, a dialog box prompts you to back up all subclients of this instance.
17. Click Yes. The Backup Options dialog box appears, which allows you to create the necessary schedules.
18. From the Backup Options dialog box, select the type of backup that you want to schedule.
19. If you want to access Advanced Backup Options, click Advanced.
20. After selecting the backup type and any advanced options, click OK. The Schedule Details dialog box appears.
21. From the Schedule Details tab of the Schedule Details dialog box, select the scheduling options that you want to apply, then click OK.

Delete an Instance

Before You Begin

• For most agents except Oracle and SQL Server, you cannot delete an instance if there is only one instance present for an agent. To delete the final instance for most agents except the ones identified, you must first remove the agent software from the client computer. For Oracle RAC, which does not involve agent software, you can delete the instance under the RAC pseudo-client.
• When you delete a specific instance positioned in the level below the corresponding agent or pseudo-client in the CommCell Console, the following actions occur:
  • The corresponding backup data for that instance becomes immediately unavailable, thus making it inaccessible for restore purposes. In effect, the backup data is deleted.
  • All child levels contained within the level are deleted in the CommCell Browser.
  • All job schedules and job histories that pertain to any of the levels within the deleted instance are deleted.
• If you delete an Oracle iDataAgent instance included within an Oracle RAC instance (node), the backup data is not deleted, and it is available for restore by another eligible client.
• You cannot delete an instance if it is being backed up. Attempts to delete an instance under such conditions cause the deletion to fail. If a backup is in progress, either wait for the backup to complete or kill the backup job using the Job Manager. Once the backup is no longer in progress, you can delete the instance level.

Required Capability: See Capabilities and Required Actions

To delete an instance positioned in the level below the corresponding agent or pseudo-client

1. From the CommCell Browser, right-click the instance that you want to delete, click All Tasks and then click Delete.
2. Click Yes to confirm the deletion. (Clicking No cancels the deletion and retains the node.)
3. Type the requested phrase in the Enter Confirmation Text dialog box and click OK. This should delete the instance.

To delete an Oracle iDataAgent instance included within an Oracle RAC instance (node)

1. Right-click the Oracle RAC instance, click Properties, and click Details.
2. Click the instance that you want to delete within Client/Instance/Status and click Delete.
3. Repeat the previous step for each Oracle iDataAgent instance (except the last one remaining) within the Oracle RAC instance that you want to delete.
4. Click OK. This should delete the Oracle iDataAgent instance(s).

Browse the Latest Data

The following procedure can be used to browse data from the instance level for MySQL iDataAgent.

Required Capability: See Capabilities and Permitted Actions

To browse the latest data:

1. From the CommCell Browser, right-click the Instance level whose data you want to browse, click All Tasks, and then click the Browse/Browse Backup Data option from that level.
2. From the Browse Options dialog box, click OK to execute the browse using the Browse the Latest Data option.

Change the Home Directory

Required Capability: See Capabilities and Required Actions

To change the Home Directory:

1. From the CommCell Browser, right-click the icon for any supported instance and then click Properties.
2. For agents other than Oracle RAC, from the General tab of the Properties dialog box, type the path in the Home or Dir (Directory) box or use Browse to locate the path. Then go to Step 6.
3. For the MySQL iDataAgent, from the General tab of the Properties dialog box, type the path in the Binary Directory box or use Browse to locate the path. Also, type the path to the MySQL data directory in the Data Directory box or use Browse to locate the path. Then go to Step 6.
4. For Oracle RAC, from the Details tab of the Properties dialog box, click the appropriate client/instance/status and then click Modify.
5. In the Update Instance dialog box, enter the path in the Home box or use Browse to locate the path.
6. Click OK to save your settings.
7. Continue to make additional settings as desired.

Change the Archive Log Index File

Required Capability: See Capabilities and Required Actions

To change the Archive Log Index file:

1. From the CommCell Browser, right-click the icon for any supported instance and then click Properties.
2. From the General tab of the Properties dialog box, enter the path for the archive index file in the Archive Log Index File field or use Browse to locate the path.
3. Click OK to save your settings.

Change the Configuration File

Required Capability: See Capabilities and Required Actions

To change the configuration file:

1. From the CommCell Browser, right-click the icon for any supported instance and then click Properties.
2. From the General tab of the Properties dialog box, enter the path for the configuration file in the Config File field or use Browse to locate the path.
3. Click OK to save your settings.

Change the Socket File

Required Capability: See Capabilities and Required Actions

To change the Archive Log Index file:

1. From the CommCell Browser, right-click the icon for any supported instance and then click Properties.
2. From the General tab of the Properties dialog box, enter the path for the archive index file in the Socket File field or use Browse to locate the path.
3. Click OK to save your settings.

Change Account for Accessing Instances

Required Capability: See Capabilities and Permitted Actions

To change a user account for accessing an instance:

1. From the CommCell Browser, expand the tree to view the instance for the affected agent. Then right-click the instance, click Properties, and click Accounts.
2. In the Instance Properties (Accounts) tab, enter (for SQL, MySQL, or Sybase) the user name information. For Sybase and MySQL, also enter SA-related information.
3. Click OK to save the settings.

Select a Storage Policy for Log Backups

Required Capability: See Capabilities and Required Actions

To select a Storage Policy for Log Backups:

1. From the CommCell Browser, right-click the icon for any supported instance and then click Properties.
2. From the Log Backups tab of the Properties dialog box, select from the list of available storage policies.
3. Click OK to save your settings.

Back to Top