Step 6: Testing Dbvnet Communication

Once you have Dbvisit Standby installed on all the servers, it is important to make sure that the communication between the primary and standby servers are working. This can be done by making use of the Dbvnet Test utility provided with the Dbvisit Standby installation - dbvnet-test, which is located under the dbvnet sub directory. When using the default path, this utility will be in:

/usr/dbvisit/dbvnet/dbvnet-test

To test communication between the primary and standby servers you can run the following recommended test commands:

To perform a basic status check which confirms that the primary and standby server can communicate using Dbvnet:
```
dbvnet-test [-s|--status] SERVER[:PORT]
```

To perform a more detailed check, testing network connectivity, you can run the following:
```
dbvnet-test [-f|--fulltest] SERVER:PORT
```

In the example below, dbvlin101 is the primary server and dbvlin102 is the standby server. Dbvisit Standby was installed using default values and no additional configuration has been performed at this stage. Dbvnet and Dbvserver is running on both nodes, but only Dbvnet is required and used for these tests:

Test 1: Basic Status Check

oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnet-test -s dbvlin102:7890
 
>>> Determining Dbvnet status on server dbvlin102:7890...
  
    Dbvnet on server dbvlin102:7890 is running.

Test 2: Full Test - 10MB file is copied (and verified) between primary and standby

oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnet-test -f dbvlin102:7890
 
>>> Determining Dbvnet status on server dbvlin102:7890...
    Dbvnet on server dbvlin102:7890 is running.
 
>>> Running file transfer round trip on server dbvlin102:7890...
    Creating file '/tmp/dbvnet-test.tmp' containing 10 MB of data... - done.
 
  > Transferring 'dbvnet-test.tmp' to server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [2609 KB/s] - done.
 
  > Retrieving file "dbvnet-test.tmp" from server dbvlin102:7890
    Progress: 0%...20%...40%...60%...80%...100% [4599 KB/s] - done.
 
    Comparing checksums: all three checksums (local/remote/local) are identical. File
    transfer round trip finished successfully.

Stop and Start Dbvnet

Dbvnet can be stopped and started using the dbvnetd executable located in the dbvnet sub directory (example - /usr/dbvisit/dbvnet). Below is an example of stopping and starting the Dbvnet background processes:

oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnetd stop
oracle@dbvlin101[/usr/dbvisit/dbvnet]: ps -ef|grep dbvnet
oracle   12641 12446  0 09:20 pts/1    00:00:00 grep dbvnet
oracle@dbvlin101[/usr/dbvisit/dbvnet]: ./dbvnetd start
oracle@dbvlin101[/usr/dbvisit/dbvnet]: ps -ef|grep dbvnet 
oracle   12643     1  0 09:20 pts/1    00:00:00 ./dbvnetd start
oracle   12644 12643  0 09:20 pts/1    00:00:00 ./dbvnetd start
oracle   12645 12643  0 09:20 pts/1    00:00:00 ./dbvnetd start
oracle   12646 12643  0 09:20 pts/1    00:00:00 ./dbvnetd start
oracle   12647 12643  0 09:20 pts/1    00:00:00 ./dbvnetd start