Spawning a New Site Database

This article is part of a series on down site recovery. You can view the related articles here...

• Switching a Site to an EMEROP

• Restoring a Spawned Database

There are a couple situations where spawning a new database may be applicable.

• Opening a new site (normally started and tested by DRB)

• Site database corruption or loss

While this process can be started from any site, ideally you'll want to spawn a DB from the Replication Server so that all data will be immediately available. Keep in mind that while the database spawns, replication will be down for the whole organization so doing this during off hours is preferred, but not required.

• Fastest Spawn Time Possible: ~2 hours

• Spawn run times:

• 05-24-22 - C18 DB Spawn

• ~Copying:~1.5 hours

• ~Wrap Up:~0.5 hours

• ~ Backing up: ~ 1.5 hours

• ~ Wrap Up: ~0.5 hour

• 08-24-20

• ~ Total Time: ~1 hour

Shut down SPM services on the Replication Server

• 1) Shut down Transaction Manager (probably won't be running)

• 2) Shut down XCC Manager

• 3) Catch up replication

• A) Replication -> Replicate Now

• 4) Shut down replication once caught up

• 5) Shut down transporter

• 6) Suspend scheduler

• 7) Check CMS (snowflake in the system tray) to make sure there are no Site Manager instances that are running. If there are restart the Replication Server to disconnect them.

Start the Spawn

• 1) In SPM go to File -> Database -> Spawn New Site Database

• 2) Read the message and acknowledge

• 3) Set the New Database site identity to the site you're spawning the database for

• 4) it should automatically set the "make this database similar to" to the site you selected in the previous step

• 5) Optional Steps

• A) Set back up the database after its created

• B) Set compress the backup for transport

• C) Consider how the DB will be deployed to configure these options

• ~IF you need to transfer it over the network, set the compress option (adds ~30-60 min to spawn time.

• ~ If you need it fast and are transferring on physical media, don't set these options as it will double the spawn time.

• 6) Set the database name/ location to where you want the spawn files to drop

• A) Keep available drive space in mind

• B) IMPORTANT: make sure the path here ends in DB_NAME.FDB

• C) Click next

• 7) Don't change anything on Data Groups to Replicate

• A) Click next

• 8) Verify the options you've set

• 9) The spawn starts

• 10) When the spawn is finished, re-enable AutoStart options and reboot the rep_server

Identifying Spawn Files

• Once the spawn is complete, there will be a bunch of Bles in the directory you set the spawn to. Here's the breakdown...

• 1) FDB File: The uncompressed dB

• A) If you are transferring the dB physically using a drive, use this

• 2) FBK File: Compressed file that needs restored before it can be used

• A) Use this if file transfer time is long or if transferring over the web to a site with highly stables internet (SDWAN)

• 3) DZ Files: Distributed compressed backup files

• A) Use this when transferring over the web on a less stable internet connection