Skip to content

Implementation Prep

Components

SyncSafe Replication consists of four main components:

  1. Management Console - A system, preferably a Virtual Machine in your environment, that will manage licenses, replication jobs, and failover tasks for all of the protected workloads in your organization.
  2. Source - Any system from which you are replicating data or the system state.
  3. Production Target - The Virtual Machine to which you are replicating data.
  4. Test Target - For system state replication testing only. This Virtual Machine is separate from the Production Target and is used specifically to test the failover of your production system state without disrupting replication to the production target.

Preparation

Design

Before deploying components, you will need to determine what your layout should look like. The following considerations should be reviewed as part of your design plan:

  1. Location of components.
    1. The Management Console system should reside in a location that is accessible at all times, but segregated from the production network to minimize the potential for compromise in the event of a network infiltration or malware attack.
    2. It is recommended that this Console live on a management network that utilizes NAT rules to restrict traffic to only necessary ports for operation and functional requirements, whether between existing production networks or between the server and external services such as system updates, NTP servers, etc. Access to the Management Console should be achieved through a "jump box" that allows access to the protected management network, and ideally require 2-factor authentication.
    3. Depending on type of scenarios SyncSafe Replication is being implemented to protect against, Replication Targets should be located on a protected subnet with similar NAT rules and restrictions as the Management Console in order to prevent corruption, infiltration, or compromise.
  2. Type of replication being implemented.
    1. File and Folder replication to alternate, fully configured servers may require additional setup, vendor-provided scripts, or other special considerations.
    2. System State replication may include additional tasks to be completed on failover related to application licensing, updates, or other potential system configuration changes that should be documented prior to implementation.
  3. Resource Consumption and Availability - Source Workloads
    1. SyncSafe Replication will require varying amounts of CPU and Memory for replication tasks. Source workloads should be evaluated for average resource utilization and adjusted to accommodate the additional workload prior to implementation. Further adjustments may be required based on specific server types and workload replication requirements.
    2. Dedicated Disks for Source replication queue files are highly recommended in order to avoid excessive Disk IO load to main system disks containing production data. This prevents negative performance impacts on server functionality as well as protecting server functions from potential failure due to full disks.
  4. Resource Consumption and Availability - Target Workloads.
    1. Target Virtual Machines need not be initially provisioned with full CPU and Memory allocation to match their sources, but should be given sufficient CPU and memory to process incoming data, as well as allow for protective functionality such as the use of Antivirus or other tools to ensure data and system integrity.
    2. Target Virtual Machines will require storage allocation equal to the original server or data set plus a minimum of 10% additional space to accommodate system operations.
    3. If VSS-based snapshots are utilized to provide a recovery checkpoint history on the target, the additional space required beyond the initial data set size will be necessary based on amount of changed data and frequency of checkpoint creation.
  5. Target Maintenance.
    1. Plans for ensuring replication targets are patched and up to date should be developed.
    2. What if any additional protection tools are to be used should be considered, and those tools should be tested with a non-production workload before implementation to ensure compatibility.
    3. Checkpoint snapshots, if needed and implemented, should be maintained either through a scripted process or by setting VSS Snapshot limitations on the target system to prevent filling up the replication target disk.

Many of the resource consumption considerations can be managed through configuration on a per-server basis in the SyncSafe Replication server options available after a server has been added to the console/system. See the SyncSafe Replication Configuration Editing Server Properties - Section Details page for configuration specifics.

Environment Preparation

Once a planned architecture has been developed, ensure that the following tasks are completed:

  • Additional networks have been built as needed.
  • NAT rules and other special network-related tuning should be completed during implementation, although additional work may be required post-implementation.
  • Virtual Machines to be included have been documented, including resource allocation (CPU, Memory, Number and Sizes of Disks).
  • Management Console Virtual Machine has been created and all security measures are functioning normally.
  • Target Virtual Machines, including secondary Virtual Machines to be used for System Replication testing, have been created with appropriate resources assigned.
  • Any special configuration requirements have been documented, vendor-specific requirements, scripts, or best practices have been documented, prepared and made available.
  • Contacts for any specialized software or services to be included in replication have been documented and support requests prepared to ensure appropriate vendor support resources are available for implementation.