About using FSAUtility with EMC Celerra/VNX placeholders
|Article:HOWTO74985|||||Created: 2012-03-31|||||Updated: 2013-07-12|||||Article URL http://www.symantec.com/docs/HOWTO74985|
Read this section if you want to use FSAUtility with placeholders on EMC Celerra/VNX volumes.
FSAUtility can use either of the following methods to identify a placeholder on an EMC Celerra/VNX device:
A Windows API call. This method is efficient, but it cannot identify placeholders on DART 5.5 volumes if the Celerra's backup mode is set to passthrough.
A Celerra/VNX HTTP API call. This method identifies placeholders correctly, regardless of the Celerra/VNX configuration. However, this method is more resource intensive than using the Windows API call.
Table Table: FSAUtility options' default API call for detecting Celerra/VNX placeholders lists the API call that FSAUtility uses by default with each of its placeholder-related options.
Table: FSAUtility options' default API call for detecting Celerra/VNX placeholders
Note that by default FSAUtility with the -pm parameter uses the Celerra/VNX API call. This default helps to ensure that placeholder migration always succeeds, regardless of the Celerra/VNX configuration. If you use FSAUtility -pm with any supported Celerra/VNX configuration other than DART 5.5 with passthrough backup mode, you may want to change the setting for this option to use the more performance-efficient Windows API call.
With the other placeholder-related parameters (-b, -c, -m, and -o) FSAUtility uses the efficient Windows API call by default. However, these commands fail by default for a DART 5.5 volume if the Celerra device's backup mode is set to passthrough.
If you want to use FSAUtility with -b, -c, -m, or -o on DART 5.5, you must do one of the following:
Ensure that the Celerra backup mode is set to offline, not passthrough.
Or configure FSAUtility to use the Celerra/VNX API call.
You can configure the API call that FSAUtility uses for each placeholder-related option by editing the
See About FSAUtility
Article URL http://www.symantec.com/docs/HOWTO74985