Topics | How To | Related Topics
DB2 DPF instances are created as part of the procedure to create a DB2 DPF pseudo-client, and they are used to add, modify, and configure multiple DB2 DPF databases and their partitions. You can create one DB2 DPF instance per DB2 DPF pseudo-client.
At least one DB2 DPF backup set (database) must be configured within each DB2 DPF instance. The data in the instance that is backed up will be available until the configured DB2 DPF instance is hard-deleted.
See Instances for an overview of Instances. Given below is a list of what you need to provide before creating an DB2 DPF instance.
Providing the latter storage policy allows you to view and track the status of jobs in the Job Controller and Event Viewer.
Software compression for DB2 DPF Command Line Backups can be administered at the instance level. Software compression for data can be administered at the instance level, but it is more granularly managed at the subclient level.
After creating the DB2 DPF instance, you must Create Backup Sets for the instance.
Once the pseudo-client is created, it is configured, and the agent is therefore able to manage the data on the client computer. However, you can change certain aspects of the instance configuration to manage the data in the manner that best suits your needs.
You can view or change the instance configuration from the Instance Properties dialog box. The following information can be configured.
For the Oracle, Oracle RAC, and SAP for Oracle iDataAgents, you can change the Oracle Home directory. Similarly, you can change the Informix (Home) directory for the Informix iDataAgent, the Sybase Home directory for the Sybase iDataAgent, the MySQL Home directory for the MySQL iDataAgent, the PostgreSQL home directory for the PostgreSQL iDataAgent, and the Instance Home directory for the DB2 DPF pseudo-client.
See Change the Home Directory for step-by-step instructions.
From the General tab, you can select an option to auto-detect new and deleted database partitions for the instance. This option should be enabled by default.
You can add one or more eligible clients and their associated database partition(s) to the DB2 DPF instance. See Add a Client/Database Partition to the Instance for step-by-step directions.
You can associate one or more DB2 DPF database partitions with a different client. See Associate a Database Partition with a Different Client for step-by-step directions.
From the Storage Device tab, you can view or change the storage policy used to back up data via the command line for the selected instance, select a storage policy for backing up logs on the selected instance, or view or select a default storage policy for the selected instance. By defining a storage policy for command line backups, you can view and track the status of those same jobs in the Job Controller. If you redefine (i.e., select a new) storage policy for command line backups at the instance level, the storage policy will apply only to any new command line backup jobs (i.e., those backup jobs that you subsequently start). (See Storage Policies for an overview.) See the configuration section for your agent for more information on this feature.
You can change the Windows or Unix user accounts that are used by the system to access the application and in effect perform all data protection and recovery operations for the iDataAgent.
See the DB2 iDataAgents section in User Accounts and Passwords for more information.You can perform the following functions:
For more information, see User Administration and Security.