Hi, http://www.sysresccd.org/Download With the SystemRescueCd I backed up the /dev/sda6 partition in /mnt/backup/ naming "diskimage"
After backing up operation the file has the automatic extension like "diskimage.000". Is this file ok to restore? If I name it "diskimage.gz" then it is automatically renamed with this extension "diskimage.gz.000"
But here below http://www.sysresccd.org/Screenshots the file is name like this: "diskimage.pimg"
Do I have to name with the .pimg extension during backup to restore correctly?
And how can I restore it?
Hope this isn't to Off-Topic... but related info.
Been watching this thread, and want to mention the methods that I have used. G4L and G4U can both do disk and partition images. I must point out that I am the current maintainer of the Free G4L.
I develop the system on my Fedora machines, but it uses the kernel.org kernels. The program can be booted from the cd, or it can be added to a system by adding options to the grub menu, or even from windows using grub4dos.
It is basically using the dd command to copy the sectors, and uses lzop, gzip, bzip2 or no compression on the image. It can backup to an ftp server, or to another disk or partition, or make a clone of a disk. It is not a file level backup, up disk or partition.
I use it in my computer lab to backup the 80GB disk with 98, XP, and Fedora 10 in about 50 minutes making a 12GB image file on a 250GB disk on my AMD64 Fedora machine.
It does work best if you clear unused space before doing an image to reduce space since the null filled sectors compress to almost nothing.
The program is available on sourceforge and freshmeat.
+----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS SETI 7,566,804.7045 | EINSTEIN 2,416,953.8009 | ROSETTA 838,646.7327
Bill Crawford wrote:
On Friday 27 March 2009 09:01:30 Michael D. Setzer II wrote:
It does work best if you clear unused space before doing an image to reduce space since the null filled sectors compress to almost nothing.
How do you do that?
head -c 100000000 /dev/zero >100mega
will create a file with 100 million zeros. You create as many files as your free space requires, until the disk is almost full.
Then you delete them all. The disk blocks will keep their values (zeros) and most of your free space will now be clean.
Slow if you have a lot of free space, but the trick works with any kind of filesystem (if it is not compressing or encrypting, that is).
Best regards.
On 27 Mar 2009 at 12:42, Bill Crawford wrote:
From: Bill Crawford billcrawford1970@gmail.com Organization: None To: fedora-list@redhat.com Subject: Re: Backing up system Date sent: Fri, 27 Mar 2009 12:42:56 +0000 Copies to: "Michael D. Setzer II" mikes@kuentos.guam.net
On Friday 27 March 2009 09:01:30 Michael D. Setzer II wrote:
It does work best if you clear unused space before doing an image to reduce space since the null filled sectors compress to almost nothing.
How do you do that?
The cd has various scripts and programs on it to help. cleandrive is the simplest script that free space for linux/unix.
dd if=/dev/zero of=/0bits bs=20M rm /0bits
That script does it, but no feedback on process. cleandrive5 and cleandrive6 do the same but use Dialog or Xdialog to provide a progress bar. The require the appropriate dialog program be installed and the jetcat-mod program copied to the / directory.
For fat32 and ntfs partitions blank6.exe can be used to clear free space for Windows. The is a lblank6 linux program that does a similar task from linux on the mounted fat32 or ntfs partition.
Additionally, there are other programs on the web that do this.
Long ago, I had done a Fedora 3 full install on a 80GB disk, and did an image. Produced a 12GB compressed image file. Then cleared unused space, and redid image. Only a 2.5GB image file. So, the random information from the drive took 9.5GB of space.
+----------------------------------------------------------+ Michael D. Setzer II - Computer Science Instructor Guam Community College Computer Center mailto:mikes@kuentos.guam.net mailto:msetzerii@gmail.com http://www.guam.net/home/mikes Guam - Where America's Day Begins +----------------------------------------------------------+
http://setiathome.berkeley.edu (Original) Number of Seti Units Returned: 19,471 Processing time: 32 years, 290 days, 12 hours, 58 minutes (Total Hours: 287,489)
BOINC@HOME CREDITS SETI 7,566,804.7045 | EINSTEIN 2,416,953.8009 | ROSETTA 838,646.7327
On 27 Mar 2009 at 12:42, Bill Crawford wrote:
From: Bill Crawford <billcrawford1970(a)gmail.com> Organization: None To: fedora-list(a)redhat.com Subject: Re: Backing up system Date sent: Fri, 27 Mar 2009 12:42:56 +0000 Copies to: "Michael D. Setzer II" <mikes(a)kuentos.guam.net>
The cd has various scripts and programs on it to help.
unfortunately I can't read the whole thread, but what I get so far (and maybe OT): isn't fsarchiver on the sysrescueCD the tool to backup and restore only disk content:
On Tue, Feb 2, 2021, at 7:21 AM, elder sixpack13 wrote:
On 27 Mar 2009 at 12:42, Bill Crawford wrote:
From: Bill Crawford <billcrawford1970(a)gmail.com> Organization: None To: fedora-list(a)redhat.com Subject: Re: Backing up system Date sent: Fri, 27 Mar 2009 12:42:56 +0000 Copies to: "Michael D. Setzer II" <mikes(a)kuentos.guam.net>
The cd has various scripts and programs on it to help.
unfortunately I can't read the whole thread, [snip]
I was going to say that I can't read the whole thing either since I joined in 2015, but I just checked the archive and you still can read the full thread from March of 2009.
On Fri, Mar 27, 2009 at 5:29 AM, GMS S gmspro@yahoo.com wrote:
Hi, http://www.sysresccd.org/Download With the SystemRescueCd I backed up the /dev/sda6 partition in /mnt/backup/ naming "diskimage"
After backing up operation the file has the automatic extension like "diskimage.000". Is this file ok to restore? If I name it "diskimage.gz" then it is automatically renamed with this extension "diskimage.gz.000"
The name is correct. It always use .000, .001, .002 .... because the image can be broken into several pieces, in some cases.
But here below http://www.sysresccd.org/Screenshots the file is name like this: "diskimage.pimg"
Do I have to name with the .pimg extension during backup to restore correctly?
No.
And how can I restore it?
You will use the file you created:
diskimage.000
(do not forget of typing the extension .000), check the restore box, and point to the partition (its size has to be greater than or equal to the size of the original partition) in the new disk that will receive the backup:
http://orion.lcg.ufrj.br/roma/LCG_partimage.html