Софт Hitachi ShadowImage свои ошибки в log-файле не расшифровывает, поэтому, чтобы определить, что же за проблемы у нас возникли открываем лог (обычно он находится где-то тут /HORCM/log0/curlog/horcmlog_`hostname`/horcm.log )
и ищем там вот такую строчку:
16:26:26-15981-99999- SSB = 0xb9a0,232a.
Вот 232a — это и есть код нашей ошибки. Ну а расшифровку можно взять из секции troubleshooting в  ShadowImage User’s Guide или из нижеприведенной таблички:

Error code Error content
b9a0/b9a1/b9a2 Error occurred in ShadowImage pair operation.
2089 Because the volume specified as a P-VOL was undergoing quick format, the quick restore operation was rejected.
208a Because the volume specified as an S-VOL was undergoing quick format, the quick restore operation was rejected.
2093 The volume specified as a P-VOL was an S-VOL of a TrueCopy asynchronous pair. Because the status of the TrueCopy asynchronous pair was not Suspend, the Split operation was rejected.
2094 The volume specified as a P-VOL was an S-VOL of a TrueCopy asynchronous pair. Because the consistency time of the consistency group is not equal to the consistency time of the TrueCopy asynchronous pair, the Split operation was rejected.
2097 When you performed the quick restore command, the quick restore operation was rejected because of one of the following reasons: .. The P-VOL of the ShadowImage pair was a Dynamic Provisioning V-VOL, and the S-VOL of the ShadowImage pair was a normal volume. .. The P-VOL of the ShadowImage pair was a normal volume, and the S-VOL of the ShadowImage pair was a Dynamic Provisioning V-VOL.
209b Because the emulation type of only one of volumes in the ShadowImage pair was OPEN-0V, the quick restore operation was rejected.
209c Because the updated information about system configuration was being backed up, the quick restore operation on the volume was rejected.
20a0 The specified pairs contain the volumes of the TrueCopy asynchronous pairs. Because the CLPRs of the P-VOL and S-VOL of the specified pair were different, the quick restore operation was rejected.
20a2 Because the P-VOL was the Dynamic Provisioning V-VOL whose capacity was increasing, the create pair operation was rejected.
20a3 Because the S-VOL was the Dynamic Provisioning V-VOL whose capacity was increasing, the create pair operation was rejected.
235b The volume specified as a P-VOL was a P-VOL of a TrueCopy synchronous or asynchronous pair. Because the status of the TrueCopy pair was not Suspend, the reverse copy or the quick restore operation was rejected.
235c The volume specified as a P-VOL was an S-VOL of a TrueCopy synchronous or asynchronous pair. Because the status of the TrueCopy pair was not Suspend, the reverse copy or the quick restore operation was rejected.
235d The volume specified as an S-VOL was a P-VOL of a TrueCopy synchronous or asynchronous pair. Because the status of the TrueCopy pair was not Suspend,the reverse copy or the quick restore operation was rejected.
2060 The volume specified as a P-VOL was a volume of a Universal Replicator pair.Because the status of the Universal Replicator pair was invalid, the pair operation was rejected.
2061 The volume specified as an S-VOL was a volume of a Universal Replicator pair. Because the status of the Universal Replicator pair was invalid, the pair operation was rejected.
232a Because pairs that would exceed the license capacity were going to be created, the create pair operation was rejected.
2346 The volume specified as an S-VOL was a P-VOL of a TrueCopy synchronous or asynchronous pair. Because the status of the TrueCopy pair was invalid, the pair operation was rejected.
2347 The volume specified as an S-VOL was an S-VOL of a TrueCopy synchronous or asynchronous pair. Because the status of the TrueCopy pair was invalid, the pair operation was rejected.

Обсуждение закрыто.