bare_metal_linux_backups_with_rdx
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
bare_metal_linux_backups_with_rdx [2019/02/15 16:09] – [Using Dump for Backups] sgriggs | bare_metal_linux_backups_with_rdx [2019/02/15 16:15] – [Using Dump for Backups] sgriggs | ||
---|---|---|---|
Line 36: | Line 36: | ||
So, how does one use dump? Well, for starters the [[https:// | So, how does one use dump? Well, for starters the [[https:// | ||
- | - Dump straight to your RDX as if it was a tape drive. | + | - Dump straight to your RDX as if it was a tape drive. |
- Create a filesystem on your RDX, mount it, and then dump to a file on the RDX. | - Create a filesystem on your RDX, mount it, and then dump to a file on the RDX. | ||
- | The first method is more simple and mimics how tape drives work for those really used to tape. The second is more friendly to someone who might come along later and wonder what is on that drive. The second method also gives you the option to compress the dump before writing it to the filesystem. That's more complicated and makes things that much more opaque if you use compression with a direct-to-device dump. So, for most folks, I'd recommend going ahead with using a filesystem as it provides better clarity and usability with compression. | + | The first method is more simple and mimics how tape drives work for those really used to tape. The second is more friendly to someone who might come along later and wonder what is on that drive. The second method also gives you the option to compress the dump before writing it to the filesystem. That's more complicated and makes things that much more opaque if you use compression with a direct-to-device dump. So, for most folks, I'd recommend going ahead with using a filesystem as it provides better clarity and usability with compression. Another big drawback is that you'd need to use some kind of tape marker to separate backups if you wanted to take more than one using the no-filesystem method. |
=== Dump Prerequisites === | === Dump Prerequisites === | ||
Line 60: | Line 60: | ||
devpts on /dev/pts type devpts (rw, | devpts on /dev/pts type devpts (rw, | ||
tmpfs on /run type tmpfs (rw, | tmpfs on /run type tmpfs (rw, | ||
- | / | + | / |
tmpfs on /run/lock type tmpfs (rw, | tmpfs on /run/lock type tmpfs (rw, | ||
tmpfs on /run/shm type tmpfs (rw, | tmpfs on /run/shm type tmpfs (rw, | ||
fusectl on / | fusectl on / | ||
- | / | + | / |
/dev/sda2 on /boot type ext3 (rw, | /dev/sda2 on /boot type ext3 (rw, | ||
rpc_pipefs on / | rpc_pipefs on / | ||
Line 106: | Line 106: | ||
</ | </ | ||
+ | |||
+ | === Dump Straight to RDX === | ||
+ | |||
+ | This is a similar process as using a filesystem without the partitioning and mounting step. So, having gone over some of the process, I'll condense this example somewhat. | ||
+ | |||
+ | < | ||
+ | ## Double check my filesystems so I know what I'm dumping | ||
+ | $ mount | ||
+ | |||
+ | ## Find my RDX Drive by exploring the drives on the system | ||
+ | fdisk -l | ||
+ | ls / | ||
+ | |||
+ | ## Perform the dump straight to the RDX without mounting it. | ||
+ | ## in this case, my RDX was found to be /dev/sdb and I ignore | ||
+ | ## any partitions on it, going straight to the raw device | ||
+ | dump -0f /dev/sdb / | ||
+ | |||
+ | ## Remember we can only dump one filesystem unless we use tape marks. | ||
+ | ## so don't use this method unless really know what you are doing. | ||
+ | </ | ||
bare_metal_linux_backups_with_rdx.txt · Last modified: 2019/02/15 16:30 by sgriggs