Versions Compared

Old Version 5

changes.mady.by.user Jan Klinke

Saved on

compared with

New Version Current

changes.mady.by.user Jan Klinke

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

Code Block
C:\Users\Administrator>acfsutil info storage
Diskgroup      Consumer      Space     Size With Mirroring  Usable Free  %Free   Path
ACFS                         19.65              19.65           0.54        2%
                DBVISIT      19.00              19.00          18.22       95%   C:\dbvisit
CRS                           4.99               4.99           4.64       92%
DATA                         39.29              39.29          39.18       99%
FRA                          19.65              19.65          17.88       91%
----
unit of measurement: GB

  • Make sure the Oracle Grid Infrastructure is deployed as per Oracle documentation. The group membership for oracle and grid users needs to be correct. Dbvisit supports cluster role separation (oracle and grid user) as well as simple configuration (oracle user only)

  • Verify that the primary oracle database is SEHA enabled:

...

To enable SEHA failover for dbvagentmanager, we recommend integrating them into Oracle Grid by using an action script. Here is a single action Action script for dbvagentmanager and dbvcontrol :

...

can downloaded from Dbvisit Software Github repository:

https://github.com/dbvisitsoftware/standby/blob/main/cluster-action-scripts/dbvcrs.bat

Dbvcontrol will not be installed on the primary cluster, but the same action script will be used for dbvagentmanager and dbvcontrol on the standby cluster.

...

Note

Do NOT change the script name nor script location. If you do, you will have to make on your own adjustments in the script and in the cluster commands.

Info

...

Be sure to check

...

Code Block
cd C:\dbvisit\app\bin C

the README:

https://github.com/dbvisitsoftware/standby/blob/main/cluster-action-scripts/README.md

2.4  Creating dbvagentmanager service on the 2nd SEHA node

On the 2nd SEHA node, we need to create the Windows service manually, set its startup mode to manual, and change the password (use an actual password):

Code Block
C:\Users\Administrator>C:\dbvisit\app\bin>dbvcrs.bat stop dbvagentmanager\bin\dbvagentmanager service install --user "dbvisit\oracle"
C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanagerUsers\Administrator>sc config dbvagentmanager start=demand
[SC] ChangeServiceConfig SUCCESS
C:\dbvisitUsers\app\bin>dbvcrsAdministrator>sc.batexe startconfig dbvagentmanager C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat clean dbvagentmanager

C:\dbvisit\app\bin>dbvcrs start dbvagentmanager
Starting service dbvagentmanager
The Dbvisit StandbyMP Agent service is starting.
The Dbvisit StandbyMP Agent service was started successfully.

Checking service dbvagentmanager

SERVICE_NAME: dbvagentmanager
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : password= "mysecret"
[SC] ChangeServiceConfig SUCCESS

Set the permissions to full control on service dbvagentmanager for “Service Logon User” and “Interactively logged-on user”:

Code Block
sc sdset dbvagentmanager "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;IU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)"
[SC] SetServiceObjectSecurity SUCCESS
Note

Do NOT start the service on 2nd node

2.5  Creating dbvagentmanager Cluster Resource

Make sure the dbvagentmanager service is stopped on both SEHA nodes. Now we can finally create the dbvagentmanager action script and test VIP + dbvagentmanager relocation:

Code Block
crsctl add resource dbvagentmanager -type generic_application -attr "START_PROGRAM='/dbvisit/app/bin/dbvcrs.bat start dbvagentmanager',STOP_PROGRAM='/dbvisit/app/bin/dbvcrs.bat stop dbvagentmanager',CHECK_PROGRAMS='/dbvisit/app/bin/dbvcrs.bat check dbvagentmanager',CLEAN_PROGRAM='/dbvisit/app/bin/dbvcrs.bat clean dbvagentmanager',CHECK_INTERVAL=10,START_DEPENDENCIES='hard(dbvisit-vip34) pullup(dbvisit-vip34) attraction(dbvisit-vip34)',STOP_DEPENDENCIES='hard(dbvisit-vip34)',PLACEMENT='favored',HOSTING_MEMBERS='w19ora19seha3 w19ora19seha4',ACL='owner:dbvisit\oracle:rwx,pgrp::r-x,other::r--'"

Try to start dbvagentmanager via crsctl and check the service status afterward (must be RUNNING):

Code Block
C:\dbvisit\app\bin>crsctl start res dbvagentmanager
CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha3'
CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha4' succeeded

C:\dbvisit\app\bin>sc query dbvagentmanager

SERVICE_NAME: dbvagentmanager
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

You need to receive the correct output for each command (service is stopped, started, etc ..).

It is expected that command dbvcrs.bat check dbvagentmanager will close the current command line window if the dbvagentmanager service isn’t running.

2.4  Creating dbvagentmanager service on the 2nd SEHA node

On the 2nd SEHA node, we need to create the Windows service manually, set its startup mode to manual, and change the password (use an actual password):

...

Test relocation of the VIP address back and forth:

Code Block
C:\dbvisit\app\bin\dbvagentmanagerbin>crsctl servicerelocate installresource dbvisit-vip34 -user "dbvisit\oracle"
C:\Users\Administrator>sc config dbvagentmanager start=demand
[SC] ChangeServiceConfig SUCCESS
C:\Users\Administrator>sc.exe config dbvagentmanager password= "mysecret"
[SC] ChangeServiceConfig SUCCESS

Set the permissions to full control on service dbvagentmanager for “Service Logon User” and “Interactively logged-on user”:

Code Block
sc sdset dbvagentmanager "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;IU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)"
[SC] SetServiceObjectSecurity SUCCESS
Note

Do NOT start the service on 2nd node

2.5  Creating dbvagentmanager Cluster Resource

Make sure the dbvagentmanager service is stopped on both SEHA nodes. Now we can finally create the dbvagentmanager action script and test VIP + dbvagentmanager relocation:

Code Block
crsctl add resource dbvagentmanager -type generic_application -attr "START_PROGRAM='/dbvisit/app/bin/dbvcrs.bat start dbvagentmanager',STOP_PROGRAM='/dbvisit/app/bin/dbvcrs.bat stop dbvagentmanager',CHECK_PROGRAMS='/dbvisit/app/bin/dbvcrs.bat check dbvagentmanager',CLEAN_PROGRAM='/dbvisit/app/bin/dbvcrs.bat clean dbvagentmanager',CHECK_INTERVAL=10,START_DEPENDENCIES='hard(dbvisit-vip34) pullup(dbvisit-vip34) attraction(dbvisit-vip34)',STOP_DEPENDENCIES='hard(dbvisit-vip34)',PLACEMENT='favored',HOSTING_MEMBERS='w19ora19seha3 w19ora19seha4',ACL='owner:dbvisit\oracle:rwx,pgrp::r-x,other::r--'"

Try to start dbvagentmanager via crsctl and check the service status afterward (must be RUNNING):

Code Block
f
CRS-2673: Attempting to stop 'dbvagentmanager' on 'w19ora19seha3'
CRS-2677: Stop of 'dbvagentmanager' on 'w19ora19seha3' succeeded
CRS-2673: Attempting to stop 'dbvisit-vip34' on 'w19ora19seha3'
CRS-2677: Stop of 'dbvisit-vip34' on 'w19ora19seha3' succeeded
CRS-2672: Attempting to start 'dbvisit-vip34' on 'w19ora19seha4'
CRS-2676: Start of 'dbvisit-vip34' on 'w19ora19seha4' succeeded
CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha4'
CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha4' succeeded

C:\dbvisit\app\bin>crsctl startrelocate res dbvagentmanagerresource dbvisit-vip34 -f
CRS-26722673: Attempting to startstop 'dbvagentmanager' on 'w19ora19seha3w19ora19seha4'
CRS-26762677: StartStop of 'dbvagentmanager' on 'w19ora19seha4' succeeded

C:\dbvisit\app\bin>sc query dbvagentmanager

SERVICE_NAME: dbvagentmanager
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

Test relocation of the VIP address back and forth:

Code Block
C:\dbvisit\app\bin>crsctl relocate resource dbvisit-vip34 -f
CRS-2673: Attempting to stop 'dbvagentmanager' on 'w19ora19seha3'
CRS-2677: Stop of 'dbvagentmanager' on 'w19ora19seha3' succeeded
CRS-2673: Attempting to stop 'dbvisit-vip34' on 'w19ora19seha3'
CRS-2677: Stop of 'dbvisit-vip34' on 'w19ora19seha3' succeeded
CRS-2672: Attempting to start 'dbvisit-vip34' on 'w19ora19seha4'
CRS-2676: Start of 'dbvisit-vip34' on 'w19ora19seha4' succeeded
CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha4'
CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha4' succeeded

C:\dbvisit\app\bin>crsctl relocate resource dbvisit-vip34 -f
CRS-2673: Attempting to stop 'dbvagentmanager' on 'w19ora19seha4'
CRS-2677: Stop of 'dbvagentmanager' on 'w19ora19seha4' succeeded
CRS-2673: Attempting to stop 'dbvisit-vip34' on 'w19ora19seha4'
CRS-2677: Stop of 'dbvisit-vip34' on 'w19ora19seha4' succeeded
CRS-2672: Attempting to start 'dbvisit-vip34' on 'w19ora19seha3'
CRS-2676: Start of 'dbvisit-vip34' on 'w19ora19seha3' succeeded
CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha3'
CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha3' succeeded

After each relocation of the VIP address, check that the dbvagentmanager service is running on that respective node and that it’s stopped on the other node. 

This step concludes the installation and setup of Dbvisit on the primary SEHA cluster

3.  Dbvisit Software Setup on Standby Cluster

3.1  Creating Dbvisit Dedicated VIP Address

Same as on the primary SEHA cluster, Before starting with Dbvisit Installation, we need to create a dedicated VIP address mentioned in the "1.3 Prerequisites". Our pre-allocated VIP for our standby SEHA cluster is "172.16.17.254" and we decided to assign DNS name "dbvisit-vip12". To create a new VIP address, you need to execute:

Code Block
languagenone
C:\Users\Administrator>appvipcfg create -network=1 -ip=192.168.18.254 -vipname=dbvisit-vip12 -user=dbvisit\oracle
Using configuration parameter file: C:\app\grid\product\19.3.0.0\gridhome_1\crs\install\crsconfig_params
The log of current session can be found at:
  C:\app\orabase\crsdata\w22ora19seha1\scripts\appvipcfg.log
Note

At this point you should ensure dbvisit-vip12 is correctly resolved by your DNS or create entry in C:\Windows\System32\Drivers\etc\hosts

Verify VIP is correctly created:

Code Block
C:\Users\Administrator>crsctl status resource dbvisit-vip12
NAME=dbvisit-vip12
TYPE=app.appviptypex2.type
TARGET=OFFLINE
STATE=OFFLINE

C:\Users\Administrator>crsctl start resource dbvisit-vip12
CRS-2672: Attempting to start 'dbvisit-vip12' on 'w22ora19seha1'
CRS-2676: Start of 'dbvisit-vip12' on 'w22ora19seha1' succeeded

3.2  Installing Dbvagentmanager on Standby Cluster

Installation of Dbvisit software on standby cluster is completely the same as on primary - the only difference is that we’ll install dbvcontrol component in addition to dbvagentmanager. We need first to create the directory which will contain Dbvisit installation DBVISIT_BASE:

Code Block
C:\Users\Administrator>mkdir C:\dbvisit\app

Continue by starting the dbvagentmanager installer and specifying this directory as DBVISIT_BASE (installation file agent-v11.6.0.msi was downloadded to C:\dbvisit\sw):

Code Block
C:\Users\Administrator>msiexec /i C:\dbvisit\sw\agent-v11.6.0.msi

...

go for next to set passphrase:

...

Use the same passphrase as on the primary cluster, then on the next page make sure to install in C:\dbvisit\app:

...

Once installation is completed, edit the dbvagentmanager configruation file and set FileTransferListenAddress to DBVISIT-VIP12.DBVISIT.CZ and save the file

Code Block
C:\Users\Administrator>notepad C:\dbvisit\app\conf\dbvagentmanager.ini

...

Restart dbvagentmanager service:

Code Block
C:\Users\Administrator>net stop dbvagentmanager && net start dbvagentmanager
The Dbvisit StandbyMP Agent service is stopping.
The Dbvisit StandbyMP Agent service was stopped successfully.

The Dbvisit StandbyMP Agent service is starting.
The Dbvisit StandbyMP Agent service was started successfully.

Set it to manual start mode:

Code Block
C:\Users\Administrator>sc config dbvagentmanager start=demand
[SC] ChangeServiceConfig SUCCESS

Set the permissions to full control on service dbvagentmanager for “Service Logon User” and “Interactively logged-on user”:

Code Block
sc sdset dbvagentmanager "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;IU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)"
[SC] SetServiceObjectSecurity SUCCESS

3.3  Installing Dbvcontrol on Standby Cluster

You can skip this section if you will deploy the controlcenter elsewhere.

...

CRS-2673: Attempting to stop 'dbvisit-vip34' on 'w19ora19seha4'
CRS-2677: Stop of 'dbvisit-vip34' on 'w19ora19seha4' succeeded
CRS-2672: Attempting to start 'dbvisit-vip34' on 'w19ora19seha3'
CRS-2676: Start of 'dbvisit-vip34' on 'w19ora19seha3' succeeded
CRS-2672: Attempting to start 'dbvagentmanager' on 'w19ora19seha3'
CRS-2676: Start of 'dbvagentmanager' on 'w19ora19seha3' succeeded

After each relocation of the VIP address, check that the dbvagentmanager service is running on that respective node and that it’s stopped on the other node. 

This step concludes the installation and setup of Dbvisit on the primary SEHA cluster

3.  Dbvisit Software Setup on Standby Cluster

3.1  Creating Dbvisit Dedicated VIP Address

Same as on the primary SEHA cluster, Before starting with Dbvisit Installation, we need to create a dedicated VIP address mentioned in the "1.3 Prerequisites". Our pre-allocated VIP for our standby SEHA cluster is "172.16.17.254" and we decided to assign DNS name "dbvisit-vip12". To create a new VIP address, you need to execute:

Code Block
languagenone
C:\Users\Administrator>appvipcfg create -network=1 -ip=192.168.18.254 -vipname=dbvisit-vip12 -user=dbvisit\oracle
Using configuration parameter file: C:\app\grid\product\19.3.0.0\gridhome_1\crs\install\crsconfig_params
The log of current session can be found at:
  C:\app\orabase\crsdata\w22ora19seha1\scripts\appvipcfg.log
Note

At this point you should ensure dbvisit-vip12 is correctly resolved by your DNS or create entry in C:\Windows\System32\Drivers\etc\hosts

Verify VIP is correctly created:

Code Block
C:\Users\Administrator>crsctl status resource dbvisit-vip12
NAME=dbvisit-vip12
TYPE=app.appviptypex2.type
TARGET=OFFLINE
STATE=OFFLINE

C:\Users\Administrator>crsctl start resource dbvisit-vip12
CRS-2672: Attempting to start 'dbvisit-vip12' on 'w22ora19seha1'
CRS-2676: Start of 'dbvisit-vip12' on 'w22ora19seha1' succeeded

3.2  Installing Dbvagentmanager on Standby Cluster

Installation of Dbvisit software on standby cluster is completely the same as on primary - the only difference is that we’ll install dbvcontrol component in addition to dbvagentmanager. We need first to create the directory which will contain Dbvisit installation DBVISIT_BASE:

Code Block
C:\Users\Administrator>mkdir C:\dbvisit\app

Continue by starting the dbvagentmanager installer and specifying this directory as DBVISIT_BASE (installation file agent-v11.6.0.msi was downloadded to C:\dbvisit\sw):

Code Block
C:\Users\Administrator>msiexec /i C:\dbvisit\sw\control-centeragent-v11.6.0.msi

There’s nothing to change throughout the whole installer except the passphrase - use the same passphrase as before:

...

...
go for next to set passphrase:
...
Use the same passphrase as on the primary cluster, then on the next page make sure to install it in C:\dbvisit\app:
...
Once installation is completed, edit the dbvagentmanager configruation file and set FileTransferListenAddress to DBVISIT-VIP12.DBVISIT.CZ and save the file
 Code Block
C:\Users\Administrator>notepad C:\dbvisit\app\conf\dbvcontroldbvagentmanager.ini
...
Restart dbvcontrol dbvagentmanager service:
 Code Block
C:\dbvisit\app\bin>sc config dbvcontrol obj="dbvisit\oracle"
[SC] ChangeServiceConfig SUCCESS

C:\Users\Administrator>sc.exe config dbvcontrol password= "mysecret"
[SC] ChangeServiceConfig SUCCESS

C:\Users\Administrator>net stop dbvcontroldbvagentmanager && net start dbvcontroldbvagentmanager
The Dbvisit StandbyMP Control CenterAgent service is stopping.
The Dbvisit StandbyMP Control CenterAgent service was stopped successfully.

The Dbvisit StandbyMP Control CenterAgent service is starting.
The Dbvisit StandbyMP Control CenterAgent service was started successfully.
set Set it to manual start mode:
 Code Block
C:\Users\Administrator>sc config dbvcontroldbvagentmanager start=demand
[SC] ChangeServiceConfig SUCCESS
Set the permissions to full control on service dbvcontrol dbvagentmanager for “Service Logon User” and “Interactively logged-on user”:
 Code Block
sc sdset dbvcontroldbvagentmanager "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;IU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)"
3.4  Creating Cluster Action Script for dbvagentmanager and dbvcontrol
We will use exactly the same action script as on the primary cluster. Download from sectio 2.3  Creating Cluster Action script for dbvagentmanager and copy it into C:\dbvisit\app\bin on standby cluster.
 Code Block
cd C:\Temp
cp dbvcrs.bat C:\dbvisit\app\bin
 Note
Do NOT change the script name nor script location. If you do, you will have to make on your own adjustments in the script and in the cluster commands.
 Note
Action script will be the same regardless whether you installed dbvcontrol or not
You need to check that the script is working properly. For checking, run on 1st SEHA node:
 Code Block
cd C:\dbvisit\app\bin
C:\dbvisit\app\bin>dbvcrs.bat stop dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanager
C:\dbvisit\app\bin>dbvcrs.bat start dbvagentmanager)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)"
[SC] SetServiceObjectSecurity SUCCESS
3.3  Installing Dbvcontrol on Standby Cluster
You can skip this section if you will deploy the controlcenter elsewhere. 
Start dbvcontrol installation:
 Code Block
C:\Users\Administrator>msiexec /i C:\dbvisit\app\bin>dbvcrs.bat check dbvagentmanager
sw\control-center-v11.6.0.msi
There’s nothing to change throughout the whole installer except the passphrase - use the same passphrase as before:
...
And make sure to install it in C:\dbvisit\app
...
:
...
Once installation is completed, edit the dbvagentmanager configruation file and set FileTransferListenAddress to DBVISIT-VIP12.DBVISIT.CZ and save the file
 Code Block
C:\Users\Administrator>notepad C:\dbvisit\app\bin>dbvcrs start dbvagentmanager
Starting service dbvagentmanager
The Dbvisit StandbyMP Agent service is starting.
The Dbvisit StandbyMP Agent service was started successfully.

Checking service dbvagentmanager

SERVICE_NAME: dbvagentmanager
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
You need to receive the correct output for each command (service is stopped, started, etc ..) - do the same for dbvcontrol
...
\conf\dbvcontrol.ini
...
Set all three properties to DBVISIT-VIP12.DBVISIT.CZ
Restart dbvcontrol service:
 Code Block
C:\dbvisit\app\bin>sc config dbvcontrol obj="dbvisit\oracle"
[SC] ChangeServiceConfig SUCCESS

C:\Users\Administrator>sc.exe config dbvcontrol password= "mysecret"
[SC] ChangeServiceConfig SUCCESS

C:\Users\Administrator>net stop dbvcontrol && net start dbvcontrol
The Dbvisit StandbyMP Control Center service is stopping.
The Dbvisit StandbyMP Control Center service was stopped successfully.
The Dbvisit StandbyMP Control Center service is starting.
The Dbvisit StandbyMP Control Center service was started successfully.
set it to manual start mode:
 Code Block
C:\Users\Administrator>sc config dbvcontrol start=demand
[SC] ChangeServiceConfig SUCCESS
Set the permissions to full control on service dbvcontrol for “Service Logon User” and “Interactively logged-on user”:
 Code Block
sc sdset dbvcontrol "D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;IU)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)"
3.4  Creating Cluster Action Script for dbvagentmanager and dbvcontrol
We will use exactly the same action script as on the primary cluster. Download again from GiHub repository:
https://github.com/dbvisitsoftware/standby/blob/main/cluster-action-scripts/dbvcrs.bat
Copy it into C:\dbvisit\app\bin on standby cluster.
 Code Block
cd C:\Temp
cp dbvcrs.bat C:\dbvisit\app\bin
 Note
Do NOT change the script name nor script location. If you do, you will have to make on your own adjustments in the script and in the cluster commands.
3.5  Creating dbvagentmanager and dbvcontrol service on 2nd SEHA node
...