Backup - Revision history

Kingu at 16:14, 9 November 2013

2013-11-09T16:14:05Z

Kingu: Added photo to page

2013-11-09T16:12:10Z

Added photo to page

Kingu: added Luckybackup App and BGS

2013-11-09T16:11:40Z

added Luckybackup App and BGS

Kingu at 02:25, 8 October 2013

2013-10-08T02:25:01Z

Kingu: Kingu moved page How to back up a Root File System (on an SD Card) to an SD Card to Backup: Long name is long

2013-10-06T00:21:16Z

Kingu moved page How to back up a Root File System (on an SD Card) to an SD Card to Backup: Long name is long

Linux-SWAT: /* What to do */

2012-04-08T08:21:14Z

‎What to do

Linux-SWAT: /* What to do */

2012-04-08T08:16:18Z

‎What to do

Porg: /* What to do */

2011-10-12T19:16:56Z

‎What to do

Porg: /* What to do */ Instruction contained FALSE information regarding device enumeration! That confusion can lead to data loss! See bug #237 http://bugs.openpandora.org/?do=details&task_id=237

2011-10-12T19:16:20Z

‎What to do: Instruction contained FALSE information regarding device enumeration! That confusion can lead to data loss! See bug #237 http://bugs.openpandora.org/?do=details&task_id=237

ABC: formating

2011-04-21T05:54:08Z

formating

@@ Line 1: / Line 1: @@
 [[File:Lead_Photo_For_Backup0-7256889469980008.png|thumbnail|LuckyBackup UI]]
-==Backup tools==
+==Graphical backup tools==
 Graphical tools <br />
 [http://repo.openpandora.org/?page=detail&app=markw9 LuckyBackup] MarkW <br />
@@ Line 7: / Line 7: @@
 [http://repo.openpandora.org/?page=detail&app=bgs BGS] made by eki
-== Make image from working rootfs ==
+==Command line guide to making an image from working rootfs==
 Comes in handy prior to doing something risky, or just if you want a snapshot of your working environment. The result is a tarball much like the one found at [http://www.openpandora.org/firmware], but containing all of the user's libraries/apps/configuration etc.
 Note that this isn't necessarily the best way to do it, but it is confirmed to work. Essentially all we're doing is storing the files of the rootfs in an archive using tar.
-== What you need ==
+=== What you need ===
 *1x SD Card (A) with the file system on it.
 *1x SD Card (B) in which the image will be placed.
 *Time for compressing ( < 1 hour).
-== What to do ==
+=== What to do ===
 ) Boot up into an OS that isn't using the file system you want to back up (the default OS on the NAND works well for this).

← Older revision		Revision as of 16:12, 9 November 2013
Line 1:		Line 1:
		+	[[File:Lead_Photo_For_Backup0-7256889469980008.png\|thumbnail\|LuckyBackup UI]]
		+
	==Backup tools==		==Backup tools==
	Graphical tools <br />		Graphical tools <br />

← Older revision		Revision as of 16:11, 9 November 2013
Line 1:		Line 1:
−	~~This~~ page ~~is a guide for those who have a~~ working rootfs ~~installed on an SD card, and wish~~ to ~~create an image of it (probably before~~ doing something risky). The result is a tarball much like the one found at [http://www.openpandora.org/firmware], but containing all of the user's libraries/apps/configuration etc.	+	==Backup tools==
		+	Graphical tools <br />
		+	[http://repo.openpandora.org/?page=detail&app=markw9 LuckyBackup] MarkW <br />
		+	or, if you just want to backup your gamesaves. <br />
		+	[http://repo.openpandora.org/?page=detail&app=bgs BGS] made by eki
		+
		+	== Make image from working rootfs ==
		+	Comes in handy prior to doing something risky, or just if you want a snapshot of your working environment. The result is a tarball much like the one found at [http://www.openpandora.org/firmware], but containing all of the user's libraries/apps/configuration etc.

	Note that this isn't necessarily the best way to do it, but it is confirmed to work. Essentially all we're doing is storing the files of the rootfs in an archive using tar.		Note that this isn't necessarily the best way to do it, but it is confirmed to work. Essentially all we're doing is storing the files of the rootfs in an archive using tar.

@@ Line 4: / Line 4: @@
 == What you need ==
-*1x [[SD Card]] (A) with the file system on it.
+*1x SD Card (A) with the file system on it.
-*1x [[SD Card]] (B) in which the image will be placed.
+*1x SD Card (B) in which the image will be placed.
 *Time for compressing ( < 1 hour).
@@ Line 12: / Line 12: @@
 ) Boot up into an OS that isn't using the file system you want to back up (the default OS on the NAND works well for this).
-) Open up SD Card A in [[thunar]], right click and select 'Open Terminal Here'. Be sure to be at the root of this filesystem you want to backup, seeing /bin, /dev, /home, /media, etc.
+) Open up SD Card A in thunar, right click and select 'Open Terminal Here'. Be sure to be at the root of this filesystem you want to backup, seeing /bin, /dev, /home, /media, etc.
 ) In the terminal type:

@@ Line 12: / Line 12: @@
 ) Boot up into an OS that isn't using the file system you want to back up (the default OS on the NAND works well for this).
-) Open up SD Card A in [[thunar]], right click and select 'Open Terminal Here'. Be sure to be at the root of this filesystem, seeing /bin, /dev, /home, /media, etc.
+) Open up SD Card A in [[thunar]], right click and select 'Open Terminal Here'. Be sure to be at the root of this filesystem you want to backup, seeing /bin, /dev, /home, /media, etc.
 ) In the terminal type:

← Older revision	Revision as of 00:21, 6 October 2013
(No difference)

@@ Line 12: / Line 12: @@
 ) Boot up into an OS that isn't using the file system you want to back up (the default OS on the NAND works well for this).
-) Open up SD Card B in [[thunar]], right click and select 'Open Terminal Here'.
+) Open up SD Card A in [[thunar]], right click and select 'Open Terminal Here'. Be sure to be at the root of this filesystem, seeing /bin, /dev, /home, /media, etc.
 ) In the terminal type:
-<source lang="bash">sudo tar -cpjvf [chosenFileName].tar.bz2 /media/[label of SD Card B]/ --numeric-owner</source>
+<source lang="bash">sudo tar -cpjvf /media/[label of SD Card B]/[chosenFileName].tar.bz2 . --numeric-owner</source>
 Where the chosen file name can be anything you like and the label of SD Card B is (funnily enough) the label of SD Card B (default is mmcblk0p1 for the first mounted SD card, mmcblk1p1 for the second mounted card)
 Example, for an image named 'myrootfs.tar.bz2', and SD Card B with the default label in slot one:
-<source lang="bash">sudo tar -cpjvf myrootfs.tar.bz2 /media/mmcblk0p1/ --numeric-owner</source>
+<source lang="bash">sudo tar -cpjvf /media/mmcblk0p1/myrootfs.tar.bz2 . --numeric-owner</source>
 For those that don't know what this is doing:
@@ Line 35: / Line 35: @@
 That's it! The pandora will happily chip away at the file system for the next 45 minutes or so (I didn't stick around, but it was finished when I came back an hour late). To extract it the command is:
-<source lang="bash">sudo tar -xpjvf [chosenFileName].tar.bz2 -C [destinationPath] --numeric-owner</source>
+<source lang="bash">sudo tar xpjvf [chosenFileName].tar.bz2 -C [destinationPath] --numeric-owner</source>
 For example, to extract my previous example into an SD Card with label 'devos':
-<source lang="bash">sudo tar -xpjvf myrootfs.tar.bz2 -C /media/devos/ --numeric-owner</source>
+<source lang="bash">sudo tar xpjvf myrootfs.tar.bz2 -C /media/devos/ --numeric-owner</source>
 You can now go '''crazy''' with your opkg, safe in the knowledge a working copy is waiting for you when you inevitably type upgrade instead of update. Sigh.

@@ Line 18: / Line 18: @@
 <source lang="bash">sudo tar -cpjvf [chosenFileName].tar.bz2 /media/[label of SD Card B]/ --numeric-owner</source>
-Where the chosen file name can be anything you like and the label of SD Card B is (funnily enough) the label of SD Card B (default is mmcblk0p1 if in the left slot or mmcblk1p1 if in right slot)
+Where the chosen file name can be anything you like and the label of SD Card B is (funnily enough) the label of SD Card B (default is mmcblk0p1 for the first mounted SD card mmcblk1p1 for the second mounted card)
 Example, for an image named 'myrootfs.tar.bz2', and SD Card B with the default label in slot one: