Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Cloning provides a quick and efficient method of replicating an existing Synergetic server environment for testing purposes. There are however risks involved that will need to be mitigated in order to prevent accidental access to the source environment. This document describes the recommended method of cloning servers together with highlighting possible configurations that will need to be addressed prior to bringing the cloned server into a live network environment.


Recommended method of cloning servers for use with Synergetic

Overview

  • Clone production server using the appropriate hypervisor tools for the virtualised host environment.
  • Keep the cloned server turned off and move to a an isolated network environment.
  • Turn on cloned server and perform clean & rename.
  • Move into production live network environment
  • Perform full system test

...

Clean and rename

Windows Server

  1. In System Properties, change 'Full computer name' to the new server name and change 'Workgroup' from the domain to a local workgroup (temporarily).

...

  1. In SQL Server Management Studio, use Synergetic database restore script 'Syn Database Refresh from Production.sql' to load / rename the database from 'PRD' to 'TST' and update script to use new URLs for test websites. Run script to recreate database specific SQL Agent jobs.
  2. Configure Synergetic to use MailHog as outbound email server - using script 'Update all Synergetic email settings.sql' - make sure to change the default values before executing.
  3. Configure Synergetic applications to connect to new server name and new database name.
    1. Synergetic Windows Application & Service Suite
    2. Synergetic web portals - SynWeb, Community Portal, CoreAPI, Web Services, SynAPI
    3. Update Synergetic CoreAPI web applications - Application Dashboard & Form Builder to point to the new CoreAPI URL.

...

  • Search entire registry for references to source server name and update
  • Move server to production live network environment and join to domain

...