Hello all,
Some time back I asked for opinions on backups. I had a lot of good opinions. I tried to backup some directories with dump. Which seemed to me to be quick and for what I was altogether looking for, for ext 2/3, pretty good. A 16GB filesystem was copied to a level 0 dump at around 1.5 GB. So it seems.
I have several favorites, but in regards to dump, for those that are familiar with it; I did a level 0 dump and before I try restoring an erased partition I though I would clean up a few questions.
As far at the partition's bootsector, would that happen to be in the dump file? And I am pretty sure partition table entries or any of the MBR are not saved. Timestamps and uuid type data of course I would not see to be saved. Although on my fstab, I use simple /dev/sdXX entries (/dev/sda1) not uuids. device.map might have to be regenerated too to get a booting system.
I did not leave out anything system wise specifically by cli options. /var, /sys, /run, /tmp, /proc I am assuming are in the level 0 dump. The switches I used were:
dump -0uv -e {some inode directory entries, not system specific} -f dmp
Any tips on what I should save or expect to need to change when restoring this?
BC
On Fri, 2022-09-16 at 17:07 -0400, Bill Cunningham wrote:
As far at the partition's bootsector, would that happen to be in the dump file? And I am pretty sure partition table entries or any of the MBR are not saved.
dump operates on filesystems, not disks, so it knows nothing about partition tables, boot sectors etc.
poc
On 9/16/2022 5:40 PM, Patrick O'Callaghan wrote:
On Fri, 2022-09-16 at 17:07 -0400, Bill Cunningham wrote:
As far at the partition's bootsector, would that happen to be in the dump file? And I am pretty sure partition table entries or any of the MBR are not saved.
dump operates on filesystems, not disks, so it knows nothing about partition tables, boot sectors etc.
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
On 9/16/22 14:07, Bill Cunningham wrote:
Some time back I asked for opinions on backups. I had a lot of good opinions. I tried to backup some directories with dump. Which seemed to me to be quick and for what I was altogether looking for, for ext 2/3, pretty good. A 16GB filesystem was copied to a level 0 dump at around 1.5 GB. So it seems.
I have several favorites, but in regards to dump, for those that are familiar with it; I did a level 0 dump and before I try restoring an erased partition I though I would clean up a few questions.
As far at the partition's bootsector, would that happen to be in the dump file? And I am pretty sure partition table entries or any of the MBR are not saved. Timestamps and uuid type data of course I would not see to be saved. Although on my fstab, I use simple /dev/sdXX entries (/dev/sda1) not uuids. device.map might have to be regenerated too to get a booting system.
You must have a system that has been updated for a long time or manually configured. /dev entries haven't been used for a long time, only UUIDs now. "dump" works primarily at the file level, not the filesystem level, so it doesn't backup the filesystem metadata. If you do a restore, you will have to create the filesystem first, where you can specify the UUID if you know what it is.
I did not leave out anything system wise specifically by cli options. /var, /sys, /run, /tmp, /proc I am assuming are in the level 0 dump. The switches I used were:
/sys, /run, /tmp, and /proc are virtual filesystems and not part of /, so you will get the directory entries themselves, but no content, which is what you want anyway.
-
Bill Cunningham -
Patrick O'Callaghan -
Samuel Sieb