Upgrading
From OpenSimulator
(→Update your existing data) |
(→Updating your config files) |
||
| Line 31: | Line 31: | ||
This step is a little more involved. We don't recommend that you simply copy over your existing config files to the new OpenSimulator installation. Although this will often work, sometimes it's quite possible to miss new configuration settings which end up causing subtle and unexplained problems. | This step is a little more involved. We don't recommend that you simply copy over your existing config files to the new OpenSimulator installation. Although this will often work, sometimes it's quite possible to miss new configuration settings which end up causing subtle and unexplained problems. | ||
| − | Instead, we strongly recommend that you | + | Instead, we strongly recommend that you copy the new example config files and change them to your case, using the old ones only as reference |
| + | copy bin/OpenSim.ini.example to OpenSim.ini and edit. | ||
| + | copy bin/Regions/Regions.ini.example to bin/Regions/Regions.ini | ||
| + | copy bin/config-include/FlotsamCache.ini.example to bin/config-include/FlotsamCache.ini and edit (should not need) | ||
| + | copy bin/config-include/osslEnable.ini.example to bin/config-include/osslEnable.ini and edit | ||
| + | for standalones | ||
| + | copy bin/config-include/StandaloneCommon.ini.example to bin/config-include/StandaloneCommon and edit | ||
| + | for grid regions | ||
| + | copy bin/config-include/GridCommon.ini.example to bin/config-include/GridCommon.ini and edit | ||
| + | |||
| + | if updating region side with HG support | ||
| + | copy bin/Robust.HG.ini.example to bin Robust.HG.ini and edit | ||
| + | if without HG | ||
| + | copy bin/Robust.ini.example to bin Robust.ini and edit | ||
| + | |||
| + | if have splited services, do this per each instance. | ||
| − | |||
SEE Discussion at [[Talk:Upgrading]] for examples of How-To Back Up & Restore your system PRIOR to ANY Migration or Upgrade! | SEE Discussion at [[Talk:Upgrading]] for examples of How-To Back Up & Restore your system PRIOR to ANY Migration or Upgrade! | ||
Revision as of 09:57, 15 February 2022
Contents |
Updating your version of OpenSimulator
Always read the release notes of the new version. It may include more information for the update process
Upgrading your version of OpenSimulator involves 4 major steps
1. Backup current instalation, including databases.
2. Update the code
3. Update your existing data for the new version of OpenSimulator.
4. Update the configuration files.
If you have a old version, you may need to install and run intermediate versions, so that your data is automatically converted. For example to upgrade from a version prior to 0.8.2.1, then you MUST first upgrade to 0.8.2.1 and only then upgrade that to 0.9.0.0. Details for this case found at: http://opensimulator.org/wiki/0.9.0.0_Release#Pivot_Release:_0.8.2.1
Update your existing data
If you use SQLite, copy *.db files of previous version bin folder to the new version bin folder. The old bin folder is the natural backup.
In the case of the other database engines, the update of the data will happen automatically when running the new version, replacing the old data.
It is so important to backup the databases, so you can revert in case something goes wrong
Updating your config files
This step is a little more involved. We don't recommend that you simply copy over your existing config files to the new OpenSimulator installation. Although this will often work, sometimes it's quite possible to miss new configuration settings which end up causing subtle and unexplained problems.
Instead, we strongly recommend that you copy the new example config files and change them to your case, using the old ones only as reference
copy bin/OpenSim.ini.example to OpenSim.ini and edit. copy bin/Regions/Regions.ini.example to bin/Regions/Regions.ini copy bin/config-include/FlotsamCache.ini.example to bin/config-include/FlotsamCache.ini and edit (should not need) copy bin/config-include/osslEnable.ini.example to bin/config-include/osslEnable.ini and edit
for standalones
copy bin/config-include/StandaloneCommon.ini.example to bin/config-include/StandaloneCommon and edit
for grid regions
copy bin/config-include/GridCommon.ini.example to bin/config-include/GridCommon.ini and edit
if updating region side with HG support
copy bin/Robust.HG.ini.example to bin Robust.HG.ini and edit
if without HG
copy bin/Robust.ini.example to bin Robust.ini and edit
if have splited services, do this per each instance.
SEE Discussion at Talk:Upgrading for examples of How-To Back Up & Restore your system PRIOR to ANY Migration or Upgrade!
Changing the database used by OpenSimulator
Since SQLite is our default database, there often comes a time when people outgrow it and want to move on to another database backend (usually MySQL).
An alternative method is to change to each region (change-region) before backing up their contents to a separate OpenSimulator Region Archive (OAR) for each region. Then change the database backend and then reload the OARs in each region separately. The disadvantage of this is that it's a little laborious if you have many regions.
You can use the "command-script" feature of OpenSim.exe to semi-automate this. E.g., create a file in your "bin" directory, called something like "dobackup", which contains the necessary commands, for example:
change-region My Island 1 save-oar MI1 change-region My Island 2 save-oar MI2 change-region Another Region save-oar AR change-region root
This can be run from OpenSim.exe by typing "command-script" followed by the name you gave the script (eg "dobackup"). Note that this will overwrite the previous backup of the same name.
Note that using a save and reload via the OAR mechanism would not normally migrate your avatar inventories (you would need to rez everything out to the region, convert the data base, and then derez them again to your inventory).
Related
Upgrade_Ubuntu_Standalone - OpenSimulator Upgrade notes for Ubuntu 8.10
