Installation Manual

Troubleshooting414
property, the entity concludes that the connection is no longer functioning. The CIM
extension stops attempting to make a connection. When this occurs on the side of the
management server, the management server attempts to re-connect (and continues the
attempt until the host becomes available). The default value is 1,000 ms. You are modifying
it to wait 200,000 ms or 3.33 minutes.
3. Click Save.
ERROR replicating APPIQ_EVAStorageVolume during Discovery Data
Collection for an EVA array
Errors similar to ERROR replicating APPIQ_EVAStorageVolume might occur when an
EVA-specific data cache is updated during a Discovery Data Collection operation. For example,
when Data Protector creates a snapshot, a new virtual disk is automatically created on the EVA
array, and the EVA database used by the management server is updated to reflect this change.
If the EVA database is changed during a Discovery Data Collection operation, small replication
errors may be seen as a result. The array information will be updated with the correct information
next time Discovery Data Collection runs.
Recalculating the Topology
When Recalculating the topology or running Discovery Data Collection, other tasks using the
management server can be delayed.because the management server must recalculate the
topology, which is a resource intensive operation. Recalculation occurs after a Discovery Data
Collection when provisioning is done, and when you choose to recalculate the topology manually.
During the recalculation period, you may not be able to log into the application. If you are already
logged into the application, navigation may not be possible until the topology recalculation is
complete.
Troubleshooting Provisioning
This section contains the following topics:
• Cannot Access a Resource Owned by Another Controller, page 414
• Error -56, page 414
• “Can't delete this zone” Message, page 415
• Changes in EFC Manager Requiring Discovery Data Collection, page 415
Cannot Access a Resource Owned by Another Controller
If you receive a message about not being able to access a resource owned by another controller, it
is because you tried to access a controller that has not been discovered. You should discover all
controllers on the LSI storage system.
For example, assume you discovered only one of the controllers on an LSI storage system with two
controllers. If you want to change a volume, such as add or delete a LUN, you will not be able to
make the change to the volume associated with the controller that has not been discovered.