I want to test backup and restore and write a process and test it so that we’re not running into new problems if we have a disaster. I need to ensure we can recover in a DR but also I know how I can set up a Sandbox from a backup of a pre configured instance of eramba so all my authentication and groups etc are set up.
As there is already a community install on this docker instance what changes do I have to make to the docker files prior to running the install to make it easy to identify which containers relate to my live and which relate to the backup test?
I’ve not been able to find anything on the forum about this already.
This isn’t so much an application issue, but a docker thing. You can’t run two docker containers with the same name and you’ll need the volume names to be different as well so they don’t use each others data, but it should be all defined in the docker yaml file(s).
High level overview - copy/paste the current yaml text so you have it twice in the file, update the container names, dependencies and volume names (the names will have to be consistently renamed) in a way that they resolve. You’ll also need to rename some environment variables. External networking ports will probably also need to be adjusted.
It might be faster/less pain free to spin up a short lived VM for testing 
Thanks @david.schroth , I had thought exactly the same about using a separate computer. Then I realised that the Virtual desktop that I would use for that sort of testing currently has internet access issues… I do think that is the right way to do it though just for consistency.
Everything that @david.schroth mentions is spot on! You will need to make sure the volume names are different, so each instance has its own volumes.
You will also need different ports since they will be on the same machine (same IP), so make sure to update the port in the compose yml file and in the public IP environment variable.
If you only want the instance to test the restore procedure, you should be fine without internet access on Community once it is installed, though you will need it to obtain the activation token. For Enterprise, the restoration should work without internet, since the eramba settings are accessible without a license but the rest of the software will be in “read only” mode.
