Setting performance tunables for storage migration

The performance tunables are set at default values. However you can define these values, to optimize the storage migration performance:

I/O size

To read or write data to the disks during migration.

To trade off between application performance and storage migration performance.

The I/O size tuning is not applicable for migration of striped volumes, if you do not change the layout.

IO size, default value (in sectors) = 4096, Lower Bound = 128, Upper Bound = 16384

Task threads

To perform the subdisk move

Can be specified separately for storage migration tasks

Operations that are initiated from array migration and storage migration wizards, use task threads value that is specified under storage migration tunables.

Task threads, default value = 1, Lower Bound = 1, Upper Bound = 20

Task Throttling

No new parameters are added to the task throttling tab. However, to further optimize the application performance during storage migration, you can modify the parameters for MirrorCreate (in case of volume relayout) and SDMove (without volume relayout and array migration). These parameters are available on the Task Throttling tab.

Perform the following steps from the system where the storage (disk group volumes or array enclosure disks) is mounted and online.

To set the storage migration performance tunables

  1. Launch VEA from Start > All Programs > Veritas > Veritas Storage Foundation > Veritas Enterprise Administrator or, on Windows 2012 operating systems, from the Apps menu in the Start screen.

    Connect to the local system.

  2. Click Control Panel in the left panel and then double-click Task Settings in the right pane.
  3. On the localhost - Task Settings window, click the Configuration task performance tuning tab to view the new performance tunables.
  4. In the Storage migration tunable box, define appropriate values for the new tunables, I/O size and Task threads, and then click OK.

    The attribute values take effect immediately and apply to all the storage migration operations run subsequently.

    These settings do not apply to the storage migration operations that are already in progress.