On 2021-01-15 18:22, Linux-Fan wrote:
I back up with
cd / && find home -xdev -print0 | cpio -o0 -H crc | gzip | openssl
enc -md sha256 -salt -pass file:passwordfile -aes-128-cbc
>backup.cpio.gz.aes
Thank you for the `openssl` commandline.
However, since I upgraded to buster, that
Jesper Dybdal writes:
On 2021-01-14 23:21, Linux-Fan wrote:
Finally out of curiosity: You mention using CPIO archives. Do you have any
input files above 8 GiB for your backup processes? I always thought that to
be the limit of CPIO?
My backups do not contain large files within the cpio
On 2021-01-14 23:21, Linux-Fan wrote:
Finally out of curiosity: You mention using CPIO archives. Do you have
any input files above 8 GiB for your backup processes? I always
thought that to be the limit of CPIO?
My backups do not contain large files within the cpio archives, so I
don't know
On Thu, 2021-01-14 at 13:45 -0500, The Wanderer wrote:
> On 2021-01-14 at 12:58, Tixy wrote:
>
> > On Thu, 2021-01-14 at 11:15 -0500, The Wanderer wrote:
>
> > > Newer-model Intel chipsets specifically prohibit booting to
> > > internal hard drives in "legacy boot" mode.
> >
> > Surely it isn't
On 2021-01-14 07:41, Jesper Dybdal wrote:
I backup my Buster server simply as a (compressed, encrypted) cpio archive.
Restoring it to a BIOS-based machine is simple: boot a rescue cd,
partition the disk, restore all files, fix fstab if necessary, run
update-grub and grub-install in a chroot
Alain D D Williams writes:
On Thu, Jan 14, 2021 at 04:41:50PM +0100, Jesper Dybdal wrote:
> I backup my Buster server simply as a (compressed, encrypted) cpio archive.
>
> Restoring it to a BIOS-based machine is simple: boot a rescue cd, partition
> the disk, restore all files, fix fstab if
Jesper Dybdal wrote:
...
> (My knowledge of UEFI is almost non-existent, and my knowledge of grub
> is very limited.)
if you are not mixing Debian with any other system and
installing from scratch all you have to make sure of is
that the system is detected as an UEFI system to begin
with and
On 2021-01-14 at 12:58, Tixy wrote:
> On Thu, 2021-01-14 at 11:15 -0500, The Wanderer wrote:
>> Newer-model Intel chipsets specifically prohibit booting to
>> internal hard drives in "legacy boot" mode.
>
> Surely it isn't the chipset which determines what disk format you can
> boot from, it's
On Thu, 2021-01-14 at 11:15 -0500, The Wanderer wrote:
[...]
> Newer-model Intel chipsets specifically prohibit booting to internal
> hard drives in "legacy boot" mode.
Surely it isn't the chipset which determines what disk format you can
boot from, it's the firmware. I know the BIOS on my new
On Thu, 14 Jan 2021 16:26:26 +
Alain D D Williams wrote:
> On Thu, Jan 14, 2021 at 04:41:50PM +0100, Jesper Dybdal wrote:
> > I backup my Buster server simply as a (compressed, encrypted) cpio
> > archive.
> >
> > Restoring it to a BIOS-based machine is simple: boot a rescue cd,
> >
On Thu, Jan 14, 2021 at 04:41:50PM +0100, Jesper Dybdal wrote:
> I backup my Buster server simply as a (compressed, encrypted) cpio archive.
>
> Restoring it to a BIOS-based machine is simple: boot a rescue cd, partition
> the disk, restore all files, fix fstab if necessary, run update-grub and
>
On 2021-01-14 17:05 +0100, Sven Joachim wrote:
> I don't think so, the only important thing is that on the restore
> machine you need to set up an EFI system partition[1] from which the
> system boots. It has to be formatted as FAT32 and mounted under
> /boot/efi when you install grub-efi-amd64.
On 2021-01-14 at 10:41, Jesper Dybdal wrote:
> I backup my Buster server simply as a (compressed, encrypted) cpio
> archive.
>
> Restoring it to a BIOS-based machine is simple: boot a rescue cd,
> partition the disk, restore all files, fix fstab if necessary, run
> update-grub and
On 2021-01-14 16:41 +0100, Jesper Dybdal wrote:
> I backup my Buster server simply as a (compressed, encrypted) cpio archive.
>
> Restoring it to a BIOS-based machine is simple: boot a rescue cd,
> partition the disk, restore all files, fix fstab if necessary, run
> update-grub and grub-install
I backup my Buster server simply as a (compressed, encrypted) cpio archive.
Restoring it to a BIOS-based machine is simple: boot a rescue cd,
partition the disk, restore all files, fix fstab if necessary, run
update-grub and grub-install in a chroot environment. That works.
But if the
15 matches
Mail list logo
