DB2 Data Links Manager Quick Beginnings

Post-installation tasks

Once the db2setup utility has finished installing DB2 Data Links Manager on your system, you should ensure that it successfully created and catalogued the DLFM_DB database by listing the contents of the System Database Directory. Once you have verified that this database exists, you need to set up a backup and recovery scheme to aid in crash recovery and protect the integrity of your data.

To verify that the DLFM_DB database was successfully created and catalogued:

Run the db2profile or db2cshrc script as follows:

   . INSTHOME/sqllib/db2profile    (for bash, Bourne or Korn shell)
   source INSTHOME/sqllib/db2cshrc (for C shell)

where INSTHOME is the home directory of the instance owner.

Retrieve the entry for the DLFM_DB database in the System Database Directory by entering the following command:
```
   db2 list database directory
```
This command should return output similar to the following:
```
   System Database Directory
 
   Number of entries in the directory = 1
 
  Database 1 entry:
 
   Database alias                  = DLFM_DB
   Database name                   = DLFM_DB
   Local database directory        = /home/dlfm
   
   Database release level          = 9.00
   Comment                         =
   Directory entry type            = Indirect (1)
   Catalog node number             = 0
```
Notes:
1. On the DLFM server node in a DCE-DFS environment, the db2 list database directory command will return output similar to the above example. On DLFM client nodes, this command will return output similar to the above example except that Directory entry type will be Remote.
If this database does not exist, see Creating and Dropping the DB2 Database on the Data Links Server.

Choosing a backup method

Whenever a DATALINK value is inserted into a table with a DATALINK column that is defined for recovery, the corresponding DATALINK files on the Data Links server are scheduled to be backed up to an archive server. Currently, Disk Copy (default method) and Tivoli Storage Manager are the two options that are supported for file backup to an archive server. Future releases of DB2 Data Links Manager will support other vendors' backup media and software.

Disk Copy (default method)

When the backup command is entered on the DB2 server, it ensures that the linked files in the database are backed up on the Data Links server to the directory specified by the DLFM_BACKUP_DIR_NAME registry variable.

The default setting for this registry variable is to set the backup directory to INSTHOME/dlfm_backup in JFS environments, where INSTHOME is the home directory of the DB2 Data Links Manager Administrator.

In DCE-DFS environments, the default setting for this registry variable is to set the backup directory to /:/dlfm_backup. This directory must be a DFS fileset. For more information, see Performance Enhancements for Disk Backup in the DFS Environment.

Use the db2set command to change the setting of the DLFM_BACKUP_DIR_NAME registry variable.

For example, to set the DLFM_BACKUP_DIR_NAME registry variable so that backup files are stored in the /home/backup directory, enter the following commands:

   mkdir /home/backup
   chown dlfmid.dlfmgroup /home/backup
   db2set DLFM_BACKUP_TARGET=LOCAL
   db2set DLFM_BACKUP_DIR_NAME=/home/backup
   dlfm stop
   dlfm start

If you choose to change the location specified by the DLFM_BACKUP_DIR_NAME registry variable, you must ensure that the directory you specify is not located on a file system using a Data Links Filesystem Filter and that the required space is available in the directory you specified for the backup files.

We do not recommend that you specify a directory that is NFS mounted. If you do specify a directory that is NFS mounted, you must ensure that any username with root authority on this file server has read and write access to this mounted directory. The DB2 Data Links Manager Administrator's username must also exist on the machine from where this directory was NFS mounted and exported.

XBSA Archive Server

To use an XBSA storage manager as an archive server:

Install an XBSA client on the Data Links server. For more information, refer to your XBSA vendor product documentation.
Register the Data Links server client application with the XBSA server. For more information, refer to your XBSA vendor server documentation.

Add the required environment variables to the DB2 Data Links Manager Administrator's db2profile or db2cshrc script files. For example, Legato requires the following:

   (for bash, Bourne, or Korn shell)
   export NSR_SERVER=fully_qualified_server_hostname
   
   (for C shell)
   setenv NSR_SERVER=fully_qualified_server_hostname

Set the DLFM_BACKUP_TARGET registry variable to XBSA and set the DLFM_BACKUP_TARGET_LIBRARY to the fully-qualified shared library supplied by the vendor. The value of DLFM_BACKUP_DIR_NAME registry variable will be ignored in this case. This will activate the XBSA backup option.

Note:

The library name must also specify which shared object in the library is to be used. For example, with Legato:

   db2set DLFM_BACKUP_TARGET_LIBRARY=/usr/lib/libxdb2.a(bsashr10.0)

Please contact your XBSA vendor for the specific settings required.

Stop the Data Links File Manager by entering the dlfm stop command.
Start the Data Links File Manager by entering the dlfm start command.

You are now ready to set up a DB2 Data Links Manager environment and verify the installation. Go to Verifying the Installation on AIX for more information.

[ Top of Page | Previous Page | Next Page ]