Configure ExodusConfig.xml - Soverance/Exodus GitHub Wiki

Configure ExodusConfig.xml

Before you can build this project yourself, you must first make a copy of the "ExodusConfigSample.xml" file located in the root directory, and rename it to "ExodusConfig.xml" In the new ExodusConfig.xml file, modify the entries to reflect the configuration for your specific environment.

When building this project in Visual Studio, know that the "ExodusConfig.xml" file must be present within the build directory before this service will run. You must ensure that this file is copied during every build process. In the Solution Explorer, right-click the "ExodusConfig.xml" file and select "Properties", then set the value of the "Copy to Output Directory" attribute to "Copy Always".

Exodus Config

Files

This feature simply mirrors a file share, from one disk to another. Here at Soverance, we use this feature to create a mirror of our asset repository, which includes all of the raw assets we use to make our games.

  • Enable Mirror - Whether or not to enable the RoboCopy File Mirror feature; file share mirror is disabled when set to false
  • Source - The UNC path of the original source file share you wish to replicate
  • Destination - The UNC path of the destination file share you wish to replicate to

Exodus does not currently support mirroring more than one file share

Hyper-V

This feature creates a full backup of every virtual machine in a Hyper-V cluster. Our Hyper-V cluster at Soverance contains all the VMs that support our company, such as domain controllers, database servers, and various internal applications.

  • Export All - Whether or not to enable the Hyper-V cluster export feature; Hyper-V export feature is disabled when set to false
  • Host To Query - The Hyper-V host for which you wish to export all virtual machines
  • Backup Destination - The UNC path of the destination file share where you wish to store virtual machine images
  • Backups to Retain - The maximum number of virtual machine images you wish to retain in the Backup Destination; if more backups exist than the number specified here, they are deleted.
  • Admin User - A user with administrative rights
  • Admin Pass - The administrator's password
  • Domain - The name of the Active Directory domain for which the Hyper-V host is a member

Exodus does not currently support exporting more than one Hyper-V cluster.

IIS

This feature enables a web interface with which to control and monitor the Exodus service. This feature is currently incomplete.

  • Site Name - The name of the Exodus website served by IIS
  • Site Address - The URL you wish to bind to this website; note that you will need to manually configure the DNS records for this address wherever your domain's DNS zone is resolved. Soverance recommends hosting this application within your intranet (i.e., with an address that is resolved locally on your LAN). For example, if your Active Directory domain is contoso.com, you might host this app at exodus.contoso.com, and simply create a new CNAME record for that name that points to your Exodus server.
  • Local Path - The local file path of the Exodus installation on the server