Restoring database with persistent properties

In the jiveProperty table, there are several properties that may need to be changed when restoring data in a Disaster Recovery (DR) situation.

For more information, see Failover and data recovery in Core database.

Table 1. Properties that may need to be changed on failover0. This table provides a list of properties that may need to be changed when restoring your Core Application database.
Property	Definition and notes
`cache.clustering.enabled`	Enables caching in a clustered environment. Possible values are either `true` or `false`. This should be set to `true` unless the new instance (disaster recovery instance) does not have clustering (more than one web application node) enabled, in which case this value should be set to `false`.
`jive.storageprovider.FileStorageProvider.rootDirectory`	Specifies the path to the mount point for binary storage if you configured your system to store binary content on the file system versus the database, which is the default. This should be the same across data centers, but it can change if the mount points are different.
`jive.storageprovider.cache.enabled`	If you use NFS for your binstore file system, then you should set this property to `false` to prevent excessive traffic on the network from caching the NFS mounts.
`jive.auth.forceSecure`	Possible values are either `true` or `false`. Set this value to `true` as part of forcing all traffic to the instance over SSL. You only need to change this value if the failover data center has a different HTTP configuration, for example, if SSL is not enabled.
`jive.master.encryption.key.node`	This property represents one of the `node.id` files in the cluster. Remove the value in the event of a failover. Upon restart, the web applications populates it automatically with the correct value.
`antivirus.virusScannerUri`	Determines the URI of the virus scan server. This may change if you failover to a new data center. The URI must be in one of the following formats: ClamAV: `tcp://hostname/clamav` McAfee: `icap://hostname:port/RESPMOD`

Table 2. Wildcards that extract additional properties. This table shows wildcards that extract additional properties. Each wildcard includes an example of properties that were extracted and may change during a failover. Your actual results will vary depending on how your system is set up.
Wildcard	Notes
`jive.cluster.jgroup.servers.address%`	Remove all values in the event of a failover. Upon restart, the web application populates this table automatically. For example, remove the values in the following property: `jive.cluster.jgroup.servers.address.8aa5ce1c-f15b-4d2e-ba90-f9cf424af3b2`
`jive.cache.voldemort.servers.address%`	If you use a DNS name or a virtual IP, then the values of extracted properties do not need to change. However, if the IP address of the cache server in the new data center is different than the IP address of the cache server in the failed data center, then this property and any of its children should be updated with the valid IP address or DNS name. For example, you may need to update the value in `jive.cache.voldemort.servers.address.1`
`__jive.analytics.%`	If you use a DNS name or a virtual IP, then the values of extracted properties do not need to change. However, if the IP address of the cache server in the new data center is different than the IP address of the cache server in the failed data center, then the `__jive.analytics.database.serverURL` property should be updated with the valid IP address or DNS name. In addition, you may need to update `__jive.analytics.database.username` and `__jive.analytics.database.password` if they change, but generally they don't. Extracted properties that might change: `__jive.analytics.database.serverURL` `__jive.analytics.database.username` `__jive.analytics.database.password`
`jive.dv.%`	The `jive.dv.service.hosts` may need to change if the IP address or domain name changes for the new data center, making it different from the failed data center. Extracted properties that might change: `jive.dv.service.hosts`
`%smtp%`	The `mail.smtp.host` or `mail.smtp.port` may need to change if the host or port changes for the new data center making it different from the failed data center. Extracted properties that might change: `mail.smtp.host` `mail.smtp.port`
`%ldap%`	The `ldap.host`, `ldap.port`, and `ldap.sslEnabled` may need to change if the values change for the new data center, making them different from the failed data center. Extracted properties that might change: `ldap.host` `ldap.port` `ldap.sslEnabled`
`%checkmail%`	The `checkmail.host`, `checkmail.port` or `checkmail.protocol` may need to change if the values change for the new data center, making them different from the failed data center. Extracted properties that might change: `checkmail.host` `checkmail.port` `checkmail.protocol`
`%activity%`	The `jive.activitymanager.endpoints` may need to change if the value changes for the new data center, making it different from the failed data center. Extracted properties that might change: `jive.activitymanager.endpoints`