Data storage

Use this topic when planning your data storage requirements for log data sets, Db2® storage, coupling facility storage, and page data sets.

Work with your storage administrator to determine where to put the queue manager data sets. For example, your storage administrator may give you specific DASD volumes, or SMS storage classes, data classes, and management classes for the different data set types.

• Log data sets must be on DASD. These logs can have high I/O activity with a small response time and do not need to be backed up.
• Archive logs can be on DASD or tape. After they have been created, they might never be read again except in an abnormal situation, such as recovering a page set from a backup. They should have a long retention date.
• Page sets might have low to medium activity and should be backed up regularly. On a high use system, they should be backed up twice a day.
• BSDS data sets should be backed up daily; they do not have high I/O activity.

All data sets are similar to those used by Db2, and similar maintenance procedures can be used for IBM MQ .

See the following sections for details of how to plan your data storage:

• Logs and archive storage

  How long do I need to keep archive logs describes how to determine how much storage your active log and archive data sets require, depending on the volume of messages that your IBM MQ system handles and how often the active logs are offloaded to your archive data sets.

• Db2 storage

  Db2 storage describes how to determine how much storage Db2 requires for the IBM MQ data.

• coupling facility storage

  Defining coupling facility resources describes how to determine how large to make your coupling facility structures.

• Page set and message storage

  Plan the page sets and buffer pools describes how to determine how much storage your page data sets require, depending on the sizes of the messages that our applications exchange, on the numbers of these messages, and on the rate at which they are created or exchanged.