It is important to ensure that the valuable data stored in your Workgroup databases is regularly backed up. For databases stored in Oracle or SQL Server databases, it is assumed that standard server backup techniques will be in operation. These should address the backup requirements for most of your data.
Some data is stored in the local “.sndb” folder for the database, even when using Oracle or SQL Server type databases. Examples of such data include Attachments, Ground Models and TSDB data objects. As a result, independent backup of the Standard Workgroup Database locations is always required (as described below).
For Standard Workgroup Databases, the following information should be observed:
- A backup procedure should backup all the files such that if a restore is required a consistent snapshot of the whole set can be restored. Backups should be done whilst Workgroup Clients are not in use. To enforce this, the Workgroup Server service can be stopped, a backup that uses Windows Volume Shadow Copy Service started and the service immediately started again. There will only be a very short downtime.
- If you are using the default settings, then it is sufficient to back up all the files and folders in the default storage location: C:\ProgramData\Innovyze\SNumbatData. If you have specified an alternative location for the “DataPath” or the “AttachmentPath” or the “VideoPath”, then you will need to back up all files and folders in these specified locations.
- It is possible to backup an individual database by copying the files within a specific “.sndb” folder.
Note: This will not backup the attachments associated with that database, as attachments are stored in a separate location.
- For modelling applications, you may also wish to back up any results stored in the Remote Results Root at the same time to maintain a completely consistent dataset. This step may be viewed as optional, since the ability to re-run simulations at any time means that data in the Remote Results Root can be recreated from the information in the Workgroup Database (see the IT Architecture Guide for more information on the Remote Results Root).