The ONCONFIG file contains a section for global parameters and individual sections for each storage-manager instance. You might need to specify multiple instances of storage managers to back up and restore data to all the coservers in Extended Parallel Server.
In Extended Parallel Server, you can use more than one storage-manager product, as follows:
If you use the onconfig.std template to configure a single coserver with one storage manager, copy the section "Storage-Manager instances" from onconfig.xps into your ONCONFIG file. Use the onconfig.xps template to configure multiple storage managers.
The global section includes parameters that apply to all storage managers. You can include ON–Bar parameters in the global section if they are the same for all storage-manager instances.
Put these parameters in the storage-manager section between the BAR_SM and END pair if they are different for each storage-manager instance.
You must define each storage-manager client that you install and configure in the storage-manager section, as illustrated in Defining a Storage Manager on a Five-Coserver System.
| Configuration Parameter | Reference | Purpose | Can Be Storage-Manager Specific | Always Storage-Manager Specific | Always Global |
|---|---|---|---|---|---|
| BAR_ACT_LOG | page BAR_ACT_LOG | Specifies the location and name for the ON–Bar activity log file. | X | ||
| BAR_BOOT_DIR | page BAR_BOOT_DIR (XPS) | Specifies the directory for the emergency boot files | X | ||
| BAR_BSALIB_PATH | page BAR_BSALIB_PATH | Specifies the path of the storage-manager library
To determine if BAR_BSALIB_PATH is supported on your platform, check your release notes. Specify BAR_BSALIB_PATH in the storage-manager section if the libraries are not in the same location on all nodes. |
X | ||
| BAR_DBS_COSVR | page BAR_DBS_COSVR (XPS) | Specifies coservers that send backup and restore data to the storage manager | X | ||
| BAR_HISTORY | page BAR_HISTORY | Specifies whether the sysutils database maintains a backup history | X | ||
| BAR_IDLE_TIMEOUT | page BAR_IDLE_TIMEOUT (XPS) | Specifies the maximum number of minutes that an onbar-worker process is idle before it is shut down | X | ||
| BAR_LOG_COSVR | page BAR_LOG_COSVR (XPS) | Specifies coservers that send log backup data to the storage manager | X | ||
| BAR_PROGRESS_FREQ | page BAR_PROGRESS_FREQ | Specifies in minutes how frequently the backup or restore progress messages display in the activity log | X | ||
| BAR_RETRY | page BAR_RETRY | Specifies how many times ON–Bar should retry a backup, logical-log backup, or restore operation if the first attempt fails | X | ||
| BAR_SM | page BAR_SM (XPS) | Specifies the storage-manager number
Is required; starts the storage-manager section. |
X | ||
| BAR_SM_NAME | page BAR_SM_NAME (XPS) | Specifies the storage-manager name | X | ||
| BAR_WORKER_COSVR | page BAR_WORKER_COSVR (XPS) | Lists the coservers that can access the storage manager This parameter is required. | X | ||
| BAR_WORKER_MAX | page BAR_WORKER_MAX (XPS) | Specifies the maximum number of onbar-worker processes
that the Backup Scheduler can start for this storage-manager instance
You can start additional onbar-worker processes manually. |
X | ||
| BAR_XFER_BUFSIZE | page BAR_XFER_BUFSIZE (XPS) | Specifies the size in pages of the buffers used between XPS and each onbar-worker process | X | ||
| BAR_XPORT_COUNT | page BAR_XPORT_COUNT (XPS) | Specifies the number of shared-memory data buffers for each onbar-worker process | X | ||
| ISM_DATA_POOL | page ISM_DATA_POOL | Specifies the volume pool that you use for backing up storage spaces | X | ||
| ISM_LOG_POOL | page ISM_LOG_POOL | Specifies the volume pool that you use for backing up logical logs | X | ||
| LOG_BACKUP_MODE | page LOG_BACKUP_MODE (XPS) | Specifies whether to back up full logical-log files automatically or manually | X |
This section shows sample storage-manager configurations for Extended Parallel Server. For more information about each configuration parameter, refer to Setting ON-Bar Configuration Parameters.
The following configuration example is for a storage manager that can run on coservers 1, 2, 3, 4, and 7. In this configuration, you have to start onbar-worker processes manually on coservers 1, 2, 3, 4, and 7, because BAR_WORKER_MAX is not set. All storage spaces and logical logs are backed up to this storage-manager instance.
# Backup/Restore Variables BAR_ACT_LOG /tmp/bar_act.log # Path of activity log BAR_RETRY 2 # Number of times to retry failures BAR_XPORT_COUNT 10 # Number of transport buffers per worker BAR_XFER_BUFSIZE 8 # Size of each transport buffer in pages LOG_BACKUP_MODE CONT # Backup as soon as logical log fills BAR_IDLE_TIMEOUT 5 # How long onbar-workers wait BAR_BSALIB_PATH /usr/lib/ibsad001.so # XBSA shared lib path # Storage-Manager Section BAR_SM 1 BAR_WORKER_COSVR 1-4,7 END
The following example is a simple storage-manager definition that automatically starts a single onbar-worker process on coserver 1. Data on coservers 1 through 5 is backed up or restored to the storage manager on coserver 1. If you omit the BAR_WORKER_MAX parameter, you must start onbar-worker processes manually. For more information, see Using start_worker.sh to Start onbar_worker Processes Manually (XPS).
# Storage Manager instances BAR_SM 1 # Storage manager ID BAR_SM_NAME A # Storage manager name BAR_WORKER_COSVR 1 # Storage mgr is on coserver 1 BAR_DBS_COSVR 1-5 # Route dbspaces to this storage mgr BAR_LOG_COSVR 1-5 # Route logs to this storage mgr BAR_WORKER_MAX 1 # Number of onbar-workers END
The following example defines different storage managers on two coservers. Because the global BAR_WORKER_MAX value is 3, the Backup Scheduler will start up to three onbar-worker processes on coserver 2 for storage-manager BAKER. For storage-manager ABEL, the local BAR_WORKER_MAX value overrides the global setting, so the Backup Scheduler will start only one onbar-worker process.
# Global section BAR_WORKER_MAX 3 # Global value for no. of onbar-workers # Storage Manager ABEL BAR_SM 1 BAR_WORKER_MAX 1 # only one onbar-worker defined BAR_DBS_COSVR 1 BAR_LOG_COSVR 1 BAR_WORKER_COSVR 1 END # Storage Manager BAKER BAR_SM 2 BAR_DBS_COSVR 2 BAR_LOG_COSVR 2 BAR_WORKER_COSVR 2 END
The configuration in Figure 9 shows how you might set up three storage managers and three backup devices:
Storage-manager ABEL can back up and restore storage spaces on coservers 1 and 3. Storage-manager BAKER can back up and restore storage spaces on coservers 4 and 2. Storage-manager CHARLY can back up and restore logs on all four coservers.
The ONCONFIG definitions for storage-managers ABEL, BAKER, and CHARLY appear in the following example:
# Storage manager section for storage manager A BAR_SM 1 BAR_SM_NAME ABEL BAR_WORKER_COSVR 1,3 BAR_DBS_COSVR 1,3 BAR_LOG_COSVR 0 BAR_WORKER_MAX 2 END # Storage manager section for storage manager B BAR_SM 2 BAR_SM_NAME BAKER BAR_WORKER_COSVR 4 BAR_DBS_COSVR 2,4 BAR_LOG_COSVR 0 BAR_WORKER_MAX 1 END # Storage manager section for storage manager C BAR_SM 3 BAR_SM_NAME CHARLY BAR_WORKER_COSVR 2 BAR_DBS_COSVR 0 BAR_LOG_COSVR 1 - 4 BAR_WORKER_MAX 1 ENDHome | [ Top of Page | Previous Page | Next Page | Contents | Index ]