Backups - Revision history

Justincc: /* Autobackup Module */

2014-07-08T16:27:16Z

‎Autobackup Module

Justincc at 16:17, 8 July 2014

2014-07-08T16:17:58Z

Justincc at 19:57, 6 January 2014

2014-01-06T19:57:50Z

Justincc at 19:57, 6 January 2014

2014-01-06T19:57:02Z

Justincc at 19:02, 6 January 2014

2014-01-06T19:02:15Z

Show changes

MakoBot: Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

2012-03-04T06:15:43Z

Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

MakoBot: Robot: Cosmetic changes

2012-03-04T02:02:19Z

Robot: Cosmetic changes

MakoBot: comment: bot test - killing 'Template:' prefix from template includings

2011-06-06T11:56:37Z

comment: bot test - killing 'Template:' prefix from template includings

Makopoppo: /* PostgreSQL */ typo

2011-05-04T10:32:46Z

‎PostgreSQL: typo

Makopoppo at 04:49, 3 January 2011

2011-01-03T04:49:14Z

@@ Line 302: / Line 302: @@
 == Autobackup Module ==
-There is an experimental [[Feature_Proposals/AutoBackup|Autobackup]] region module that will automatically save OARs at specified intervals.  This is not yet well documented and should be considered experimental.
+There is an experimental [[Autobackup]] region module that will automatically save OARs at specified intervals.  This is not yet well documented and should be considered experimental.
 = Other things to backup =

@@ Line 299: / Line 299: @@
 * '''Console Scripts:'''
 * Backup &amp; Restore console scripts
 = Other things to backup =

@@ Line 268: / Line 268: @@
 * Robust.ini if you are running in grid mode OR Robust.HG.ini if you are running in grid mode with Hypergrid enabled.
-= Backup using archive files =
+= Archive approach =
 This approach takes archive files (OARs and IARs) instead of backing up the database directly.

@@ Line 299: / Line 299: @@
 * '''Console Scripts:'''
 * Backup &amp; Restore console scripts
 [[Category:Database]]

@@ Line 7: / Line 7: @@
 If you don't run your own grid, then this is a way to back up your data locally.
-* [[OpenSim Archives|OpenSim Archives (OARs)]]
+* [[OpenSim Archives|OpenSimulator Archives (OARs)]]
 * [[Inventory Archives]]
 * [[Server Commands|save-xml2 and load-xml2]]
@@ Line 42: / Line 42: @@
 = SQLite =
 Since SQLite saves its databases as local files, it's fairly simple to back it up.
-* Stop OpenSim
+* Stop OpenSimulator
 * Copy all of the *.db files out of the /bin directory (assuming that you haven't changed this in the OpenSim.ini file) to wherever you want them saved.
@@ Line 103: / Line 103: @@
 === Windows ===
-The same as above can be done in Windows, but rotating the date can't be done in batch scripting afaik. I&nbsp;do however have a script for Windows I&nbsp;wrote for my OpenSim.
+The same as above can be done in Windows, but rotating the date can't be done in batch scripting afaik. I&nbsp;do however have a script for Windows I&nbsp;wrote for my OpenSimulator.
 This is a script for taking a full MySQL backup on Windows (all databases). It required ActiveState Perl and 7zip command line to work. ''It works equally well for Linux, but a few adjustments to paths in header needs to be made.''
@@ Line 260: / Line 260: @@
 = PostgreSQL =
 I recently had to do a backup and restore of my PostgreSQL database. Here, for the benefit of the other PostgreSQL user are my notes. I did my backup and restore because I was updating the database software.
-* Shutdown OpenSim
+* Shutdown OpenSimulator
 * Use the pg_dump command to backup the database.
-** In my case, I did this as the postgres user. It should work as the OpenSim (or whatever user owns the OpenSim database) user.
+** In my case, I did this as the postgres user. It should work as the OpenSimulator (or whatever user owns the OpenSimulator database) user.
 ** pg_dump -b -Fc -C -f opensim.db.backup opensim
 ** The -b option requests that large objects are included in the dump. This would be things like textures and sounds.

@@ Line 3: / Line 3: @@
-=Backup Using Tools=
+= Backup Using Tools =
 If you don't run your own grid, then this is a way to back up your data locally.
-* [[OpenSim_Archives|OpenSim Archives (OARs)]]
+* [[OpenSim Archives|OpenSim Archives (OARs)]]
-* [[Inventory_Archives|Inventory Archives]]
+* [[Inventory Archives]]
 * [[Server Commands|save-xml2 and load-xml2]]
@@ Line 16: / Line 16: @@
 [[Backing Up WIN]]
-*'''Console Scripts:'''
+* '''Console Scripts:'''
-*Backup &amp; Restore console scripts
+* Backup &amp; Restore console scripts
-*'''Batch File:'''
+* '''Batch File:'''
-*Full Backup Archiving for use with Scheduler or Manually initiated
+* Full Backup Archiving for use with Scheduler or Manually initiated
 [[Backing Up LINUX]]
-*'''Console Scripts:'''
+* '''Console Scripts:'''
-*Backup &amp; Restore console scripts
+* Backup &amp; Restore console scripts
-=Local Files=
+= Local Files =
 The following files need to be saved:
 * Configuration files
@@ Line 48: / Line 48: @@
 = MySQL =
-==Making A Backup of your MYSQL Database==
+== Making A Backup of your MYSQL Database ==
 You can, and should backup the MySQL database to a set of SQL commands, which can use used to restore the database, if needed, with the following command:
@@ Line 67: / Line 67: @@
 You will '''not''' be prompted for your password, this makes this command suitable to be used for unattended backups.
-==Timestamped Backups==
+== Timestamped Backups ==
 Making a single backup is good. Making daily backups is even better!
 However, using the command above, it will keep reusing that one file, making it impossible to go back to an earlier date, if needed.
@@ Line 73: / Line 73: @@
 So what we want, is to give the backup a unique, and meaningful name. Here is how:
-===Linux===
+=== Linux ===
   mv /home/Johnny/OpenSimBackups/OpensimBackup.sql /home/Johnny/OpenSimBackups/OpensimBackup_$(date +%Y-%m-%d-%H.%M.%S).sql
@@ Line 79: / Line 79: @@
 Instead of issuing this command after the backup has been made, you can append it to the backup command by adding a pipe symbol ('''|''') to the first command. This will let you use the entire line in a cron job.
-===Windows===
+=== Windows ===
 ''<THIS SECTION NEEDS TO BE TESTED!!!>''
@@ Line 85: / Line 85: @@
-==Automatic Daily Backups==
+== Automatic Daily Backups ==
 === Linux ===
@@ Line 98: / Line 98: @@
 Instead of using crontab, you can use some graphical tools.
-*In GNOME, use ''gnome-schedule'' to set a scheduled job.
+* In GNOME, use ''gnome-schedule'' to set a scheduled job.
-*In KDE, use the Task Scheduler from your ''System Settings'' panel.
+* In KDE, use the Task Scheduler from your ''System Settings'' panel.
-===Windows===
+=== Windows ===
 The same as above can be done in Windows, but rotating the date can't be done in batch scripting afaik. I&nbsp;do however have a script for Windows I&nbsp;wrote for my OpenSim.
 This is a script for taking a full MySQL backup on Windows (all databases). It required ActiveState Perl and 7zip command line to work. ''It works equally well for Linux, but a few adjustments to paths in header needs to be made.''
-ActiveState Perl:&nbsp;[http://www.activestate.com/activeperl/ http://www.activestate.com/activeperl/]<br>7-Zip Command line: [http://www.7-zip.org/download.html http://www.7-zip.org/download.html]
+ActiveState Perl:&nbsp;[http://www.activestate.com/activeperl/ http://www.activestate.com/activeperl/]<br />7-Zip Command line: [http://www.7-zip.org/download.html http://www.7-zip.org/download.html]
 <pre>use strict;
 use locale;
@@ Line 258: / Line 258: @@
-=PostgreSQL=
+= PostgreSQL =
-I recently had to do a backup and restore of my PostgreSQL database.  Here, for the benefit of the other PostgreSQL user are my notes.  I did my backup and restore because I was updating the database software.
+I recently had to do a backup and restore of my PostgreSQL database. Here, for the benefit of the other PostgreSQL user are my notes. I did my backup and restore because I was updating the database software.
 * Shutdown OpenSim
 * Use the pg_dump command to backup the database.
-** In my case, I did this as the postgres user.  It should work as the OpenSim (or whatever user owns the OpenSim database) user.
+** In my case, I did this as the postgres user. It should work as the OpenSim (or whatever user owns the OpenSim database) user.
 ** pg_dump -b -Fc -C -f opensim.db.backup opensim
-** The -b option requests that large objects are included in the dump.  This would be things like textures and sounds.
+** The -b option requests that large objects are included in the dump. This would be things like textures and sounds.
 ** The -Fc option creates the backup file as a gzipped tar file
 ** The -C option includes commands to create the database when restoring
-** The -f option specifies the name of the output file.  In this case opensim.db.backup
+** The -f option specifies the name of the output file. In this case opensim.db.backup
-** There are a number of other options that can be used.  For example, if you're doing the backup on a different machine, the -h option allows you to specify the machine that the database is running on.
+** There are a number of other options that can be used. For example, if you're doing the backup on a different machine, the -h option allows you to specify the machine that the database is running on.
 * Copy the opensim.db.backup file to a CD-ROM or wherever you want it saved.
-* Do what you need to do.  In my case, it was upgrading the PostgreSQL software
+* Do what you need to do. In my case, it was upgrading the PostgreSQL software
 * While PostgreSQL was shutdown, I saved a tar of its /data directory to make it easier to recover if the upgrade went bad.
 * I also took copies of the configuration files in the /data directory so that I didn't have to recreate them.
@@ Line 281: / Line 281: @@
 ** pg_restore -C -d template1 opensim.db.backup
 ** Read the PostgreSQL documentation for more information.
-In my case, it seemed to work fine.  After I started up OpenSim, I logged in and found everything as it should be.  I would really recommend trying this first on a test Sim that you didn't care about.  Also study the documentation before trying this.  Your setup may be different than mine.
+In my case, it seemed to work fine. After I started up OpenSim, I logged in and found everything as it should be. I would really recommend trying this first on a test Sim that you didn't care about. Also study the documentation before trying this. Your setup may be different than mine.
-=MS SQL=
+= MS SQL =
 <unknown>
 [[Category:Database]]

← Older revision		Revision as of 11:56, 6 June 2011
Line 1:		Line 1:
−	{{~~Template:~~Quicklinks}}	+	{{Quicklinks}}
	Making backups of your configuration files and data is essential.		Making backups of your configuration files and data is essential.

← Older revision		Revision as of 04:49, 3 January 2011
Line 1:		Line 1:
	{{Template:Quicklinks}}		{{Template:Quicklinks}}
	Making backups of your configuration files and data is essential.		Making backups of your configuration files and data is essential.
−
−	If necessary, you can also back up regions by using [[OpenSim_Archives\|OpenSim Archives (OARs)]] and inventory using [[Inventory_Archives\|Inventory Archives]]. If you don't run your own grid, then this is a way to back up your data locally.
−