Defining Spaces

Cross-site replication works across all spaces in a metaspace. If data is written to a space on the primary site, that same space must already be created on the DR site for cross-site replication to succeed.

If your current design has clients or seeders dynamically creating spaces, you have to revisit your strategy to ensure all spaces are created on the DR site before cross-site replication is enabled. It is not necessary that the space definitions on the DR site must exactly match the space definitions on the primary site. What is important is that the spaces have the same name and can hold the same data. In the space definition on the DR site, you can vary other space definition settings to suit your needs such as: min seeder count, replication count, and so on.

Admin Command Scripts

If you are not already familiar with Admin script files, see the Using a Script File to Pass Arguments section in the TIBCO ActiveSpaces Administration guide. as-admin, as-agent, and as-router can all be used to run Admin script files using the following command line argument: 
–input  <filename>
When deploying cross-site replication, Admin command scripts can be useful for:
  1. Defining all of the spaces of your metaspace
  2. Creating your remote site definition
For example, a file containing the following as-admin commands can be used on your DR site to create a remote site definition for a site named 'primarySite' and create the space used by the ASOperations example. 
create site 'primarySite'

create space name 'myspace' ( field name 'key' type 'integer' nullable false, field name 'value' type 'string' nullable true, field name 'time' type 'datetime' nullable true) key (type 'hash' fields ('key'))
Notice that router_discovery is not specified as a part of the create site command on the DR site.