Backing up and migrating OpenSimulator databases
Detailed OpenSimulator 0.9.3.1 explanations based on INI templates and source code.
Inventory connections
List ROBUST, simulator, estate and add-on connections. One MySQL instance may contain separate schemas; simulators may point to different database servers. Never include passwords in public documentation.
Cover all data layers
Back up central records, RegionStore, EstateStore, INI files, classic assets or FSAssets files and their SQL metadata. OAR and IAR exports are additional layers, not substitutes for every database.
Coordinate backup points
A consistent SQL dump of one schema does not guarantee matching states across other schemas and FSAssets files. Plan controlled maintenance or coordinated snapshots, followed by a restore test.
Avoid apparent data loss
Simply changing ConnectionString can point a process to an empty schema and cause fresh tables to be initialized. Avoid creating replacement users, estates or regions until the actual database is identified.
Validate restores in isolation
Test avatar login, inventory, objects, terrain, estates, permissions and assets in an isolated environment. SQL row counts alone do not prove successful restoration.
Other guides in this section
- Understanding OpenSimulator databases
- INI files and SQL connections
- Regions.ini and region tables
- OpenSim.ini, Estates.ini and estate storage
- OpenSimulator 0.9.3.1 SQL tables
- Administer MySQL / MariaDB
- Install a ROBUST grid
- Understanding FSAssets