Backup - Revision history

Kingu at 16:14, 9 November 2013

2013-11-09T16:14:05Z

← Older revision		Revision as of 16:14, 9 November 2013
Line 1:		Line 1:
	[[File:Lead_Photo_For_Backup0-7256889469980008.png\|thumbnail\|LuckyBackup UI]]		[[File:Lead_Photo_For_Backup0-7256889469980008.png\|thumbnail\|LuckyBackup UI]]

	==~~Backup~~ tools==		==Graphical backup tools==
	Graphical tools <br />		Graphical tools <br />
	[http://repo.openpandora.org/?page=detail&app=markw9 LuckyBackup] MarkW <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		[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.		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.

	== What you need ==		=== 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).		*Time for compressing ( < 1 hour).

	== What to do ==		=== What to do ===

	1) 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).		1) 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).

Kingu: Added photo to page

2013-11-09T16:12:10Z

Added photo to page

← 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 />

Kingu: added Luckybackup App and BGS

2013-11-09T16:11:40Z

added Luckybackup App and BGS

← 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.

Kingu at 02:25, 8 October 2013

2013-10-08T02:25:01Z

← Older revision		Revision as of 02:25, 8 October 2013
Line 4:		Line 4:

	== What you need ==		== 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).		*Time for compressing ( < 1 hour).

Line 12:		Line 12:
	1) 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).		1) 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).

	2) 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.		2) 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.

	3) In the terminal type:		3) In the terminal type:

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

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

Linux-SWAT: /* What to do */

2012-04-08T08:21:14Z

What to do

← Older revision		Revision as of 08:21, 8 April 2012
Line 12:		Line 12:
	1) 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).		1) 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).

	2) 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.		2) 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.

	3) In the terminal type:		3) In the terminal type:

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

← Older revision		Revision as of 19:16, 12 October 2011
Line 18:		Line 18:
	<source lang="bash">sudo tar -cpjvf [chosenFileName].tar.bz2 /media/[label of SD Card B]/ --numeric-owner</source>		<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 for the first mounted SD card mmcblk1p1 for the second mounted card)		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:		Example, for an image named 'myrootfs.tar.bz2', and SD Card B with the default label in slot one:

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

← Older revision		Revision as of 19:16, 12 October 2011
Line 18:		Line 18:
	<source lang="bash">sudo tar -cpjvf [chosenFileName].tar.bz2 /media/[label of SD Card B]/ --numeric-owner</source>		<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:		Example, for an image named 'myrootfs.tar.bz2', and SD Card B with the default label in slot one:

ABC: formating

2011-04-21T05:54:08Z

formating

← Older revision		Revision as of 08:16, 8 April 2012
Line 12:		Line 12:
	1) 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).		1) 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).

	2) Open up SD Card B in [[thunar]], right click and select 'Open Terminal Here'.		2) 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.

	3) In the terminal type:		3) 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)		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:		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:		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:		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':		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.		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.

← Older revision		Revision as of 05:54, 21 April 2011
Line 4:		Line 4:

	== What you need ==		== 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).		*Time for compressing ( < 1 hour).

Line 12:		Line 12:
	1) 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).		1) 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).

	2) Open up SD Card B in thunar, right click and select 'Open Terminal Here'.		2) Open up SD Card B in [[thunar]], right click and select 'Open Terminal Here'.

	3) In the terminal type:		3) In the terminal type:

	sudo tar -cpjvf [chosenFileName].tar.bz2 /media/[label of SD Card B]/ --numeric-owner		<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 if in the left slot or mmcblk1p1 if in right slot)
	Example, for an image named 'myrootfs.tar.bz2', and SD Card B with the default label in slot one:		Example, for an image named 'myrootfs.tar.bz2', and SD Card B with the default label in slot one:

	sudo tar -cpjvf myrootfs.tar.bz2 /media/mmcblk0p1/ --numeric-owner		<source lang="bash">sudo tar -cpjvf myrootfs.tar.bz2 /media/mmcblk0p1/ --numeric-owner</source>

	For those that don't know what this is doing:		For those that don't know what this is doing:
	*sudo (super user do) makes the command run with root privileges. This is important as many of the files in the rootfs will be protected from user access.		*sudo (super user do) makes the command run with root privileges. This is important as many of the files in the [[rootfs]] will be protected from user access.
	*tar is the name of the program we're using to compress/store the rootfs		*tar is the name of the program we're using to compress/store the rootfs
	*c is create a new archive		**c is create a new archive
	*p is to ensure the permissions are kept the same. This is VERY important, some files require specific levels of privileges in order to work correctly. This is probably default when run with sudo, but it doesn't hurt to put it in.		**p is to ensure the permissions are kept the same. This is VERY important, some files require specific levels of privileges in order to work correctly. This is probably default when run with sudo, but it doesn't hurt to put it in.
	*j means use bz2 compression		**j means use bz2 compression
	*v means verbose. This will spit out the file names that it's currently archiving to the terminal.		**v means verbose. This will spit out the file names that it's currently archiving to the terminal.
	*f is for file		**f is for file
	*--numeric-owner will store the owners of the files as numbers. I don't understand this, I read it [http://www.halfgaar.net/backing-up-unix#section-2.1 here]		**--numeric-owner will store the owners of the files as numbers. I don't understand this, I read it [http://www.halfgaar.net/backing-up-unix#section-2.1 here]

	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:		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:

	sudo tar -xpjvf [chosenFileName].tar.bz2 -C [destinationPath] --numeric-owner		<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':		For example, to extract my previous example into an SD Card with label 'devos':

	sudo tar -xpjvf myrootfs.tar.bz2 -C /media/devos/ --numeric-owner		<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.		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.