03-11-2020
Quote:
Originally Posted by
stomp
Encryption makes the backup task more difficult.
Unfortunately I need it, I can't avoid it.
Quote:
Originally Posted by
stomp
Since you're a beginner, a CloneZilla can be a fallback solution until you're famillar enough with your linux os. With CloneZilla you can save and restore the os partition without knowing very much about linux.
Okay Clonezilla is not an option for me. Simply because I don't have that much of space to spare. It seems I am not getting the answer that I want because I am not asking the right questions.
So let me apologize for that, and let me ask if the following workflow is possible on Linux.
- I have a single 1 TB SATA hard disk.
- I will be using an encrypted LVM with ext4 formatting.
- Now lets say before an update or a dist-upgrade I take a snapshot of the root partition and store that snapshot in the root partition itself.
- The upgrade or update fails or is causing problems, and the system is no longer bootable to my desktop.
- I boot into a live CD.
- Mount my encrypted partitions, and /proc, /sys and /dev from the live CD.
- Chroot into my system.
- Find the saved snapshot.
- Revert it.
- Exit from Live CD environment and boot back to the reverted system.
Main Challenges:
- Will the backup process work ?
- Will the Live CD of my OS contain CLI tools to decrypt encrypted partitions ?
As you can see, I cannot forego full-disk encryption nor do I have that much space or time for a full cold boot snapshot of a partition.
So is the above workflow possible ?
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
We are looking into buying a new software, billing software that is, and want to know if you can run that on the same UNIX server as another major software?
Is there a limit to the different types of software Unix can run, or is it like windows where you can install as many as you like?
... (2 Replies)
Discussion started by: hoz
2 Replies
2. UNIX for Advanced & Expert Users
Hi there.
I've been tasked with making a new design for our Unix systems :eek:
Now the question I have is;
How many LPARs can a p570 hold WITHOUT using a VIO Server.
Many Thanks
Kees (1 Reply)
Discussion started by: KeesH
1 Replies
3. Red Hat
Hi.
I downloaded a package that could only be installed on RHEL5, and not 4 or 3, so I got the source in order to compile it on RHEL 3 so hopefully it will work on all versions.
So I have the source for a working package, but when I build it in RHEL 3 and then try to install it in RHEL 5, it... (6 Replies)
Discussion started by: Boaz
6 Replies
4. Filesystems, Disks and Memory
I'm looking for a means to ensure that servers in the two or three datacenters, connected in a ring via IP through two ISPs, can distribute load and/or replicate data among at least two SAN-class disk devices.
I want to evaluate several solutions, and I'm open to solutions ranging from free,... (6 Replies)
Discussion started by: otheus
6 Replies
5. Solaris
I've got a Solaris 11 Express installed on my machine. I have created a raidz2 zpool named shares and a simple one-disc zpool named backup. I have made a script that would send a daily snapshot of shares to backup.
I use these commands
zfs snapshot shares@DDMMRRRRHHMM
zfs send -i shares@....... (10 Replies)
Discussion started by: RychnD
10 Replies
6. UNIX for Advanced & Expert Users
I wonder if anyone could assist with some problems I'm having with Linux Capabilities and their use when using the commands "nice" and "schedtool".
I run a couple of PCs, one is an elderly AMD Sempron 2800+ (32-bit, 2GHz clock and 3GB memory) that is used as a family multimedia system running... (3 Replies)
Discussion started by: MikeGM
3 Replies
7. Linux
So I'm having a problem getting a Broadcom BCM4312 wireless controller to work under the broadcom-wl module
$uname
Linux 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
lspci -v
05:00.0 Network controller: Broadcom Corporation BCM4312 802.11b/g... (2 Replies)
Discussion started by: Skrynesaver
2 Replies
8. UNIX for Advanced & Expert Users
Hi
I'm trying to compile my linux kernel with CONFIG_SECURITY_CAPABILITIES=y.
any idea what this thing does ??
Also another question , If I compile the kernel that I'm currently using , what'll happen ?
~cheers (3 Replies)
Discussion started by: leghorn
3 Replies
9. What is on Your Mind?
Hi All,
How worried is everyone about the Dirty Cow Linux exploit? Has anybody experienced attacks yet?
From the research I've done it seems that the exploit is "reliable" (that is it works nearly every time on vulverable systems) which is not good news.
We all believe that Unix/Linux... (3 Replies)
Discussion started by: hicksd8
3 Replies
LEARN ABOUT FREEBSD
gptboot
GPTBOOT(8) BSD System Manager's Manual GPTBOOT(8)
NAME
gptboot -- GPT bootcode for UFS on BIOS-based computers
DESCRIPTION
gptboot is used on BIOS-based computers to boot from a UFS partition on a GPT-partitioned disk. gptboot is installed in a freebsd-boot par-
tition with gpart(8).
IMPLEMENTATION NOTES
The GPT standard allows a variable number of partitions, but gptboot only boots from tables with 128 partitions or less.
PARTITION ATTRIBUTES
gptboot checks and manages several attributes of GPT UFS partitions.
bootme Attempt to boot from this partition. If more than one partition has the bootme attribute set, gptboot will attempt to boot each
one until successful.
bootonce Attempt to boot from this partition only one time. Setting this attribute with gpart(8) automatically also sets the bootme
attribute. Multiple partitions may have the bootonce and bootme attributes set.
bootfailed The bootfailed attribute marks partitions that had the bootonce attribute set, but failed to boot. This attribute is managed by
the system. See BOOTING and POST-BOOT ACTIONS below for details.
USAGE
For normal usage, the user does not have to set or manage any of the partition attributes. gptboot will boot from the first UFS partition
found.
The bootonce attribute can be used for testing an upgraded operating system on an already-working computer. The existing system partition is
left untouched, and the new version of the operating system to be tested is installed on another partition. The bootonce attribute is set on
that new test partition. The next boot is attempted from the test partition. Success or failure will be shown in the system log files.
After a successful boot of the test partition, a user script can check the logs and change the bootme attributes so the test partition
becomes the new system partition. Because the bootonce attribute is cleared after an attempted boot, a failed boot will not leave the system
attempting to boot from a partition that will never succeed. Instead, the system will boot from the older, known-working operating system
that has not been modified. If the bootme attribute is set on any partitions, booting will be attempted from them first. If no partitions
with bootme attributes are found, booting will be attempted from the first UFS partition found.
BOOTING
gptboot first reads the partition table. All freebsd-ufs partitions with only the bootonce attribute set, indicating a failed boot, are set
to bootfailed. gptboot then scans through all of the freebsd-ufs partitions. Boot behavior depends on the combination of bootme and
bootonce attributes set on those partitions.
bootonce + bootme Highest priority: booting is attempted from each of the freebsd-ufs partitions with both of these attributes. On each
partition, the bootme attribute is removed and the boot attempted.
bootme Middle priority: booting is attempted from each of the freebsd-ufs partitions with the bootme attribute.
If neither bootonce nor bootme attributes are found on any partitions, booting is attempted from the first freebsd-ufs partition on the disk.
POST-BOOT ACTIONS
The startup script /etc/rc.d/gptboot checks the attributes of freebsd-ufs partitions on all GPT disks. Partitions with the bootfailed
attribute generate a ``boot from X failed'' system log message. Partitions with only the bootonce attribute, indicating a partition that
successfully booted, generate a ``boot from X succeeded'' system log message. The bootfailed attributes are cleared from all the partitions.
The bootonce attribute is cleared from the partition that successfully booted. There is normally only one of these.
FILES
/boot/gptboot bootcode binary
/boot.config parameters for the boot blocks (optional)
EXAMPLES
gptboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically
installed in combination with gptboot.
Install gptboot on the ada0 drive:
gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
gptboot can also be installed without the PMBR:
gpart bootcode -p /boot/gptboot -i 1 ada0
Set the bootme attribute for partition 2:
gpart set -a bootme -i 2 ada0
Set the bootonce attribute for partition 2, automatically also setting the bootme attribute:
gpart set -a bootonce -i 2 ada0
SEE ALSO
boot.config(5), rc.conf(5), boot(8), gpart(8)
HISTORY
gptboot appeared in FreeBSD 7.1.
AUTHORS
This manual page written by Warren Block <wblock@FreeBSD.org>.
BSD
February 5, 2014 BSD