Instances - DB2 DPF - How To
Topics |
How To | Related Topics
Modify an Instance
Delete an Instance
Create Backup Sets/Migration Sets
Select a Storage Policy for Third Party User Commands
Configure Third-party Command Line
Operations for Encryption
Change the Home Directory
Change Account for Accessing Databases/Applications (DB2 on Windows)
Add a Client/Database Partition to the Instance
Associate a Database Partition with a Different Client
Required Capability: See
Capabilities and Required Actions
To modify an Instance
- From the CommCell Browser, right-click the instance you want to modify, and then click
Properties from the shortcut menu.
- Click the General tab of the
Instance properties box to change the required access information for
this instance.
- 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.
- 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.
- 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.
- For an Oracle instance, click the Details
tab to change the database connect string and other optional parameters.
- For an Oracle RAC instance, go to the next step. Otherwise, go to
Step 12.
- 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.
- Click the Oracle instance (Client/Instance/Status) that you want to
modify. Then click Modify.
- In the
Update Instance dialog box, update the desired field values by typing or
browsing as appropriate. Then click OK.
- Repeat the previous two steps for each Oracle instance that you want to
modify.
- 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.
- 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.
- If you want to enable data encryption, from the
Encryption tab
select encryption settings for third-party or RMAN command line backups.
- Click OK to save the configuration changes.
- 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.
- Click Yes.
The Backup Options dialog box appears, which allows you to create the
necessary schedules.
- From the Backup Options
dialog box, select the type of backup that you want to schedule.
- If you want to access Advanced Backup Options,
click Advanced.
- After selecting the backup type and any advanced options, click OK.
The Schedule Details dialog box appears.
- From the Schedule
Details tab of the Schedule Details dialog box, select the scheduling options
that you want to apply, then click OK.
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
- From the CommCell Browser, right-click the instance that you want to
delete, click All Tasks and then click Delete.
- Click Yes to confirm the deletion. (Clicking No
cancels the deletion and retains the node.)
- 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)
- Right-click the Oracle RAC instance, click Properties, and
click Details.
- Click the instance that you want to delete within
Client/Instance/Status and click Delete.
- Repeat the previous step for each Oracle
iDataAgent instance (except the last
one remaining) within the Oracle RAC
instance that you want to delete.
- Click OK. This should delete the Oracle
iDataAgent instance(s).
|
With the exceptions noted above, you can no longer access the corresponding
backup data for restore purposes. |
Required Capability: See
Capabilities
and Permitted Actions
To
create backup sets/archive sets for the client computer:
- From the CommCell Browser, locate the correct client computer node, right-click
the iDataAgent, Agent or instance
node (depending on your agent's functionality) for which you want the backup
set/archive set created, select All Tasks and then click Create New
Backup Set or Create New Archive Set.
- For most agents, from the Create New Backup Set or Create New
Archive Set dialog box, enter a New Backup Set Name or New Archive
Set Name (up to 32 characters) of the backup set/archive set that you
want to create. For the DB2 or DB2 DPF iDataAgent,
from the same dialog box, click the desired database (backup set) name under
Available DB Names and move this name under Selection.
NOTES
- For DB2 or DB2 DPF, to prevent archive log backup failures, ensure that the name
that you select is the actual name of the database and not the alias name
for the database. If the database name and the corresponding alias name
are different, both names are displayed under Available DB Names;
if both names are the same, the name that is displayed is the database name.
To find out about database names and their aliases, run the following command
as a DB2 or DB2 DPF instance owner on the DB2 or DB2 DPF client: db2 list db directory.
- Where applicable, if you want to designate this backup set/archive set as
the default backup set/archive set, select Make this the Default backup set
or Make this the Default Archive Set; otherwise, leave the check box
cleared.
- For most agents, verify that the storage policy copy associated with the
default subclient is the storage policy that you want. If you want to select
a different storage policy, click the storage policy box and select the one
you want from the list. If the agent supports a system-state subclient, repeat
this step for that subclient. For the DB2 or DB2 DPF
iDataAgent,
to establish a storage policy for all the log files, click the storage policy
in the list provided.
- Where applicable, if you want to create additional subclients within this
backup set/archive set:
- Click Add.
- Follow Create a New Subclient
procedure.
- Repeat this step for each additional subclient that you want to define
within this backup set/archive set.
- When all subclients have been added, click OK.
- A message will advise you to schedule backups for your new backup set.
It is recommended that you elect to set a schedule now. You can also associate
this backup set/archive set 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 backup set/archive
set. See Schedule Policy
for more information.
- If you want to associate this backup set/archive set with an All
Agent Types schedule policy, click Associate with Generic Schedule
Policy, and then select that schedule policy from the drop-down
list box. Click OK.
- If you have selected to define a schedule for this backup set/archive
set:
- Click Schedule.
- If applicable, from the Backup Options dialog box, select
the type of backup that you want to schedule.
- If you want to set Advanced Backup/Archive Options, click
Advanced.
- After selecting the backup type and any advanced options, click
OK. The Schedule Details dialog box appears.
- From the
Schedule
Details tab, select the scheduling options that you want to
apply, then click OK.
- If you don't want to create a backup/archive schedule at this time,
click Do Not Schedule, and then click OK.
The new backup set/archive set is displayed in the CommCell Browser.
|
A content example for NetWare File System is SYS:\public, and an
example for NDS content is OU=prospects.O=engineering.[Root]. |
Required Capability: See
Capabilities and Required Actions
When backing up data through third-party command line functions rather than
the CommCell Console, the specific storage policy for the backups of the
affected non-Oracle RAC agents is established
and maintained through the Creating New Instance screen for the
appropriate iDataAgent. For the
Oracle RAC iDataAgent, the storage
policy is established when you create the associated pseudo-client or when you
modify the pseudo-client instance.
To
select a storage policy for third-party user commands for non-Oracle RAC agents:
- From the CommCell Browser, right-click the supported server/instance icon, click
All Tasks, and then click
New Instance.
- Within the Creating New Instance dialog box,
click the Storage Device tab on server/instance properties.
- From the Command
Line Backup tab, select from the list of existing storage policies
- Click OK to save your settings.
To
select a storage policy for third-party user commands for the Oracle RAC iDataAgent:
- From the CommCell Browser, if you are creating a RAC pseudo-client,
right-click Client Computers, click New Client, click
RAC Client in the Add New Client dialog box, and then click OK.
If you are modifying the pseudo-client instance, right-click the instance
and then click Properties.
- Click
Storage Device.
- From the Command
Line Backup tab, select from the list of existing storage policies.
-
Use the other tabs as appropriate to configure the subclient and then click
OK to save your settings.
Encryption settings made at the instance level for third-party Command Line
operations are not related in any way to settings made at the subclient level.
Subclient encryption settings are only for data protection and recovery
operations run from the CommCell Console.
See Data
Encryption - Support for a list of supported
products.
Before You Begin
Encryption must be enabled at the client level prior to configuring any
instances residing on that client. See
Configure the Client for Data
Encryption.
Required Capability:
Capabilities and Permitted Actions
To
configure the instance for encryption of third-party command line operations:
- From the CommCell Console, right-click the instance and click Properties.
- From the respective
Encryption
tab, select an option based on the
criteria described in the Encryption tab help.
- Click OK to save your settings and close the properties dialog
box.
|
For third-party Command Line data recovery operations to succeed when
using pass-phrase security, you must export the pass-phrase to the
destination client. |
Required Capability: See
Capabilities and Required Actions
To
change the Home Directory:
- From the CommCell Browser, right-click the icon for any
supported instance and then click
Properties.
- 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.
- 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.
- For Oracle RAC, from the
Details tab of
the Properties dialog box, click the appropriate client/instance/status and
then click Modify.
- In the Update Instance dialog box, enter the path in the Home box or use
Browse to locate the path.
- Click OK to save your settings.
- Continue to make additional settings as desired.
Required Capability: See
Capabilities
and Permitted Actions
To change
a user account for accessing DB2 databases:
- From the CommCell Browser, expand the tree if necessary to view the desired
level icon.
- From the agent level, right-click the agent icon, click All Tasks
from the short-cut menu, click New Instance, and go to the next step.
- From the instance level, right-click the instance icon, click Properties
from the short-cut menu, and go to Step 3.
- From the backup set level, right-click the backup set icon, click
Properties from the short-cut menu, and go to Step 4.
- Use the Creating New Instance dialog box to create and configure
the instance. Thereafter, from the General tab, click the Change
button associated with the User Account information. Then go to Step 5.
- From the General tab of the Instance Properties dialog box,
click the Change button associated with the User Account information.
Then go to Step 5.
- From the General tab of the Backup Set Properties dialog box,
ensure that the Connect as a Different User option is selected. Then
click the Change button associated with the User Account information.
- Enter the required information in the
Set DB2
User Account dialog box.
- Click OK to save the settings.
To change
a user account for accessing Oracle or SAP for Oracle applications on Windows not associated with QR Agent:
- From the CommCell Browser, expand the tree if necessary to view the desired
level icon.
- From the agent level, right-click the agent icon, click All Tasks
from the short-cut menu, and click New Instance (Oracle SID).
- From the instance level, right-click the instance icon and click
Properties from the short-cut menu.
- From the General tab, click the Change button associated with the
User Account information.
- Enter the required information in the
Impersonate
NT User dialog box.
- Click OK to save the settings.
To change
a user account for accessing Oracle applications for QR Agent:
- From the CommCell Browser, expand the tree if necessary to view the QR agent
icon. Then right-click the icon and click Properties.
- From the Authentication
tab, click the Oracle sub-tab.
- From the Oracle sub-tab, either click Add Instance or select an Oracle
instance to edit and then click Edit Instance.
- From the Add Oracle Instance to QR Agent dialog box, click Change.
- Enter the required information in the
Impersonate
NT User dialog box.
- Click OK to save the settings.
To change
a user account for accessing Informix, Oracle, or SAP for Oracle applications on
Unix:
- From the CommCell Browser, expand the tree if necessary to view the
desired level icon. From the agent level, right-click the agent icon, click
All Tasks from the short-cut menu, click New Instance, and go
to the next step. From the instance level, right-click the instance icon,
click Properties from the short-cut menu, and go to Step 3.
- Use the New
Instance dialog box to create and configure the instance.
- From the General
tab of the Instance Properties dialog box, do one of the following, as
appropriate.
- For Informix, type the name of the user account in the INFORMIX USER
field.
- For Oracle or SAP for Oracle, type the name of the user account in
the ORACLE USER field.
- Click OK to save the settings.
Required Capability: See
Capabilities and Required Actions
To add
a client/database partition to the DB2 DPF instance:
- From the CommCell Browser, right-click the appropriate DB2 DPF instance and then click
Properties from the shortcut menu.
- Click the Details
tab.
- In the Add Clients/Client space,
click the name of the client that you want to add to the DB2 DPF instance.
Then click Add/Refresh. The name of the client and its corresponding
database partition(s) should be displayed in the
DB2 Partition Clients space.
- Repeat this procedure for each client and corresponding partition(s)
that you want to include in the DB2 DPF instance.
- Click OK to apply the changes.
Required Capability: See
Capabilities and Required Actions
To
associate a DB2 DPF database partition with a different client:
- From the CommCell Browser, right-click the appropriate DB2 DPF instance and then click
Properties from the shortcut menu.
- Click the Details
tab.
- In the DB2 Partition Clients space,
click the partition/client pair for the database partition whose client
association you want to change and then click Modify.
- From the list in the
Edit
Directory Share Name Pair dialog box, click the name of the new client for the
partition. Then click OK.
- Repeat this procedure for each partition/client association you want to
modify.
- Click OK to apply the changes.
Back to Top