If you upgrade Business Continuity Manager to 8.1.4 or later, journal volume information will not be acquired by remote scan or NG scan. Take note of the following points:
If you only upgrade Business Continuity Manager to 8.1.4 or later, the journal volume information in the disk configuration definition files that were created by using a remote scan or NG scan when the version of Business Continuity Manager was earlier than 8.1.4 will not be deleted. To delete the journal volume information, delete the disk configuration definition files, and then scan the storage system to re-create disk configuration definition files.
If you assign dummy device numbers in the Edit Device Number for CU panel, dummy device numbers are assigned in ascending order of the command control address values. Scans for Business Continuity Manager version 8.1.4 or later skip the command control addresses of journal volumes. For this reason, the command control addresses will not correspond to the dummy device numbers on one-to-one basis. For example, if the command control address of a journal volume is 02 and the beginning value of the dummy device numbers is 0000, the relationship of "command control address: dummy device number" will be as follows:
00: 0000
01: 0001
03: 0002
04: 0003
If necessary, in the CCA Selection List for Edit devn panel, correct the relationship of "command control address: dummy device number".
If you link Business Continuity Manager with Replication Manager, journal volume information will not be acquired by remote scan or NG scan.