10.3 Simultaneously taking client backup to primary pool, copy pool and active data storage pools

Simultaneously Writing data to multiple Storagepools

We can simultaneously write data to multiple storage pools at the same time when the client backup is running. You should have enough tape drive resources and memory resources to handle the pressure on the TSM server. You can simultaneously take backup to primary pools and up to three copy pools and active-data pools. There are some limitations if you are using Deduplication technology in you environment. If you back up a large number of clients during your backup time window, you might exceed the number of drives that are available. Simultaneous write operations works on the following operations
  • Client backup, archive, and space-management operations
  • Server import operations
  • Storage pool migration
To write client data simultaneously to multiple copy storage pools, the storage pool must contain a list of the additional copy storage pools (up to ten) defined. The following apply
  • You must not change the copy storage pool list that is in the storage pool hierarchy. If there is a different copy storage pool list, then all resources that are currently held are released in order to obtain the resources of the new copy storage pool list.
  • Target pools can have different device classes.
  • Availability of mount points might be limited.
  • Use simultaneous write operations in conjunction with a storage pool backup.
When the migration process is running, data can be written simultaneously to as many as three copy storage pools, including active-data pools. Creates a copy storage pool list at the beginning of a process and is active for the life of the process. While the process is active, writes to the copy storage pools in the list. Simultaneous write migration is not supported for the server data movements, such as reclamation, move data, move nodedata, or cloning.

Also Read: Points to remember when taking backup to multiple storagepools simultaneously

Simultaneous migration improves the client backup and archive operations by providing the features as follows
  • The combined processing time for migration and storage pool backups reduces the storage pool backup time window.
  • Simultaneous migration is faster than simultaneous write to primary and copy storage pools during client backup or archive operations.
  • Reduces the need for excessive mount points.

How to configure Simultaneous Writing to Copy stgpool and active data storagepool

You can use the DEFINE STGPOOL or UPDATE STGPOOL commands to configure the simultaneous writing operations. For example, use the below command will simultaneoulsy write data to 2 copy stgpools and 1 active data pools when the client backsup data to primary diskpool.
update stgpool diskpool copystgpools=copypool1,copypool2 activedatapools=activedatapool

You can also monitor the simultaneous writing operation by using AUTOCOPY parameter in the DEFINE STGPOOL or UPDATE STGPOOL. You can when to enable this simultaneous writing operations.
update stgpool diskpool autocopy=NONE|CLIENT|MIGRATION|ALL

None: The administrator can disable simultaneous write altogether. This option is useful for administrators who want to disable simultaneous write without having to update the storage pool, remove the copy or active-data pool list, and then redefine them to re-enable it.
CLient (default): Only writes to copy or active-data pools during client store operations. This default option enables simultaneous write to continue to operate without having to update or change definitions. This option also applies to IMPORT. When importing data, files are only written to a copy storage pool. Active-data pools are not written to during import operations.
MIGRation: Only write to copy or active-data pools during migration to this storage pool.
All: Perform simultaneous write during client store or migration.

0 Comment to "10.3 Simultaneously taking client backup to primary pool, copy pool and active data storage pools"

Post a Comment