Replicating Data Stores

CiscoSecure Global Roaming Server (GRS) uses either a flatfile or database to configure domain and network access server (NAS) related information. An important feature that CiscoSecure GRS provides is the ability to replicate these data stores among one or more CiscoSecure GRSes.

Creating replicate data stores and keeping them current is a simple matter. When logged in to a CiscoSecure GRS, a script is run that defines a primary CiscoSecure GRS (source) and a secondary CiscoSecure GRS (destination). The secondary CiscoSecure GRS is where the replicate data store is to be created and maintained. To update the replicate, the script is repeated. If the data store is replicated among many CiscoSecure GRSes, the update is performed asynchronously, meaning the data stores are rapidly updated one at a time, not simultaneously.

Replication Relationships

A primary-to-secondary or primary-to-primary relationship is used to create and maintain the replicate data stores. The primary-to-secondary relationship involves a single CiscoSecure GRS updating one or more CiscoSecure GRSes. The primary-to-primary relationship involves each CiscoSecure GRS updating all the others.

Replication Solutions

This section describes two replication solutions: primary-to-secondary and primary-to-primary. If an Oracle 7.3.4 or higher database is used, either of the two solutions can be implemented. If a flatfile is used, only the primary-to-secondary solution can be implemented.

Primary-to-Secondary Solution

The primary-to-secondary solution meets the needs for organizations that must use a single CiscoSecure GRS (the primary) to replicate its data store among one or more CiscoSecure GRSes (the secondaries). When an update is performed, the data stores located on the secondaries are deleted, then replaced with a copy of the primary data store.

Primary-to-Primary Solution

The primary-to-primary solution meets the needs for organizations that must use a single CiscoSecure GRS to replicate its data store among one or more CiscoSecure GRSes, however, only the data that is common among the CiscoSecure GRSes will be updated. Therefore, data that is unique to a specific CiscoSecure GRS will remain unchanged, but data that is common among the CiscoSecure GRSes will be updated. This solution can only be implemented with an Oracle 7.3.4 or higher database.

Replicating a Data Store

Note A CiscoSecure GRS host that interfaces 2 or more networks, (has 2 or more network interface cards installed), can replicate a data store across only 1 of the networks. Furthermore, in these cases you must use the actual local host name, not its alias, in the following procedures.

Note Before replicating a data store, make sure that you can perform a Network File Sharing (NFS) mount from the source host to the destination host that contains the CiscoSecure GRS directory. This requires that NFS and its associated software is installed, and that all the NFS daemons are running on both hosts. If an NFS mount cannot be completed, replication will not work and Solaris will generate the following messages:

nfs mount: grout:/opt/CSCOgrs: server not responding : RPC: Timed out
nfs mount: retrying: /opt/CSCOgrs/tmp/.dstDir

To replicate a CiscoSecure GRS data store:

Step 1 Log in to a CiscoSecure GRS as root.

If creating a primary-to-secondary relationship, log in to the primary CiscoSecure GRS. Log in to any CiscoSecure GRS if creating a primary-to-primary relationship.

Note

Step 2 Move to the TNS_ADMIN directory.

Step 3 In the TNS_ADMIN directory, find the tnsname.ora file. View this file to assure that it contains the host name for each CiscoSecure GRS that will maintain a replicated data store. Add their names if necessary.

Step 4 Move to the $GRSHOME/bin directory.

Step 5 Enter the following command to replicate a data store:

grsdbreplicate {-m|-p} -s source -d destination [destination1 ...]

This command will replicate the source data store defined by -s, and propagate it to the CiscoSecure GRSes defined by -d. Although this command appears to only create primary-to-secondary relationships, it will create primary-to-primary relationships. Therefore, you do not have to repeat the command for each primary CiscoSecure GRS.

-m

Creates a primary-to-secondary relationship.

-p

Creates a primary-to-primary relationship.

source

If replicating a flatfile, type the CiscoSecure GRS host name. If replicating an Oracle database, type username/passwd@dbserver where username is your Oracle username, passwd is your Oracle password, and dbServer is the name of the Oracle database.

destination

If replicating a flatfile, type the CiscoSecure GRS host name. If replicating an Oracle database, type username/passwd@dbserver where username is your Oracle username, passwd is your Oracle password, and dbServer is the name of the Oracle database.

-m	Creates a primary-to-secondary relationship.
-p	Creates a primary-to-primary relationship.
source	If replicating a flatfile, type the CiscoSecure GRS host name. If replicating an Oracle database, type username/passwd@dbserver where username is your Oracle username, passwd is your Oracle password, and dbServer is the name of the Oracle database.
destination	If replicating a flatfile, type the CiscoSecure GRS host name. If replicating an Oracle database, type username/passwd@dbserver where username is your Oracle username, passwd is your Oracle password, and dbServer is the name of the Oracle database.

Updating the Replicate Data Stores

To update a CiscoSecure GRS data store:

Step 1 Log in to a CiscoSecure GRS as root.

If updating a primary-to-secondary relationship, log in to the primary CiscoSecure GRS. Log in to any CiscoSecure GRS if updating a primary-to-primary relationship.

Step 2 Move to the $GRSHOME/bin directory.

Step 3 Type the following command to update the replicate data stores:

grsdbreplicate {-m|-p} -s source -d destination [destination1 ...]

This command will use the data store defined by -s to update the data stores in CiscoSecure GRS hosts defined by -d. Although this command appears to update only primary-to-secondary relationships, it will update primary-to-primary relationships. Therefore, you do not have to repeat the command for each CiscoSecure GRS.

-m	Creates a primary-to-secondary relationship.
-p	Creates a primary-to-primary relationship.
source	If replicating a flatfile, type the CiscoSecure GRS host name. If replicating an Oracle database, type username/passwd@dbserver where username is your Oracle username, passwd is your Oracle password, and dbServer is the name of the Oracle database.
destination	If replicating a flatfile, type the CiscoSecure GRS host name. If replicating an Oracle database, type username/passwd@dbserver where username is your Oracle username, passwd is your Oracle password, and dbServer is the name of the Oracle database.

C onfiguring a GRS for Backup Duties

If communications are interrupted between a NAS and a specific CiscoSecure GRS, the NAS must know which backup CiscoSecure GRS to use. Simply log in to a CiscoSecure GRS that is configured as the backup, then add the NAS to its configuration as described in the "Adding a NAS" section. When the General tab is open, make sure the Default NAS Profile check box is clear.

Table of Contents

Replicating Data Stores