BCV Sync Script

Creating BCV sync Script for new Host/server.

Once completion of P-Vol creation we create S-Vol for those respected production volumes.

Once copy is completes we will kept the pair in split state. But we have to take the Incremental or Full copy of the P-Vol depending on the priority of the host.

So that’s why we are creating Sync script and schedule it, once created it will automatically starts and stop the copy between those devices.

Ø  First we have to create HORCM (Hitachi online remote copy) instances.

HORCM instances, if you want to use Hitachi’s Local Replication (Shadow Image) you need two HORCM instances on the recovery site, the instance ID for the Local Replication (Shadow Image) must be +1 of the replicated LUNS (LDEV’s as Hitachi calls them) so if you used HORCM10 for the instance for the replicated LUNS you must use HORCM11 for the Local Replication or running test fail-over’s will not work.

Ø  Once the services have been installed you must create the horcmX.conf files and place them in C:\HORCM\etc, again X is the HORCM instance ID.

              horcm00    11000/udp    # hormc0

              horcm101    11001/udp    # hormc1

             

              (Name of services must correspond to names of config files.)

               cd /etc/services –HORCM Instances location.

The simplest input for horcm00.conf:

          *********************** HORCM_MON******************************

          #ip_address                      service                            poll (10ms)    timeout (10ms)

          hostname or ip-address *      name-of-service-registered **          1000              3000

          HORCM_CMD

          #dev_name

#dev_group                      dev_name                        Serial#         CU: LDEV(LDEV#)  MU#

          \\.\PhysicalDrive2 or UUID  \\.\Volume

HORCM_INST

#dev_group                      ip_address      service

   *dev_group =Host Group Name

   * Paste name of your management host or its IP address.

   * Paste name of service registered in C:/etc/horcm*.conf UNIX or C:\winnt\horcm*.conf Windows details below.
*HORCM_CMD-Command Device id in ctd format.

(The Command Device is dedicated to CCI communications and should not be used by any other applications)

  

 The simplest input for horcm101.conf:

 *********************** HORCM_MON******************************

          #ip_address                      service                            poll (10ms)    timeout (10ms)

          hostname or ip-address *      name-of-service-registered **          1000              3000

          HORCM_CMD

          #dev_name

#dev_group                      dev_name                        Serial#         CU: LDEV(LDEV#)  MU#

          \\.\PhysicalDrive2 or UUID  \\.\Volume

HORCM_INST

#dev_group                      ip_address      service

              

Ø  After this initial configuration you can run CCI but with some basic "scripting".

cat horcm00.conf – EX: Configuration file

Testing:

## horcmstart.sh 00 – For running the instance

Ø  Second step is Create the configuration scripts Run the instance and check it is opening or not. If not check out the HORCM log for where exactly error is coming.

Cd /HORCM --- for Log files

Ø  Once horcmstart is successfull, then add the reaming P-Vol and S-Vols.

 After that we have to go the oracle home location add the new host details in tnsnames.ora.

            cd  /u01or u02 or u03 or u04 /app/oracle/product/network/admin

Ø  After that Add the given Oracle SID, Password & Control file backup location Path.

                     cd    /u01/app/oracle/script/.passwd

Ø  Then Finally Create or edit the Sync Script with new Horcm instances, Host Groups and Oracle Sid.

=========================****===============================