USB mountpoints jumping around

[Sorin Srbu]

On Tue, 2022-12-13 at 14:05 +0100, Ralf Mardorf via ubuntu-users wrote:
> On Tue, 2022-12-13 at 11:44 +0000, Sorin Srbu via ubuntu-users wrote:
> > I think maybe I should do a mount entry in crontab, to run just before
> > the scheduled veeam backup job starts, just in case I forget to
> > manually mount it.
> 
> Hi,
> 
> better run a script doing a
> 
>  mount [...] && backup_thingy_executable
> 
> The "&&" ensures that the backup only starts if mount finished
> successfully.

That's a good idea, thanks!




> Keep in mind, if you have a mount point directory e.g.
> 
>   /mnt/here
> 
> and the mount command should fail for whatever reason, but the backup
> should start anyway, than all the data that should be written to the
> external drive gets written to /mnt/here on the local drive holding /
> (the partition holding your root directory). If the root directory
> should run out of free space while you run the install, you get a broken
> install with broken data and a broken backup.

I've run into non-mounts situations from time to time. No biggie.
The backup fails, but so far nothing worse than that.


> I've got way more concerns related to your "backup" strategy, but I'm
> ill in bed with a cold, so there's no time for me to explain my
> concerns. Just one hint, making a backup of a running system on a file
> system that doesn't support snapshots, can easily result in a broken
> backup. So if the install and/or data is on a file system that doesn't
> support snapshots, better shutdown the install and run the backup from
> another install or a live media.

I don't follow. Please elaborate on this when you get better!

Veeam backup agent for linux does snapshots of running systems just fine. It
kinda' is its "thing".
Restores work fine. The times I've needed to make a full restore it has just
worked.

We're getting a bit off topic, but here goes anyway!

The whole idea with Veeam's take on backups, is to get around shutting down
the backupee system (and also do volume backups for bare metal restores).
It's a enable and forget solution.

The reason I choose Veeams solution was I wanted to get back up fast in the
event of a catastrophic failure. The data I care for, is all in the cloud
anyway, so it's no bif deal if the local copies get nuked. I just want to
get back working again, and fast.

Last restore I had to do took about 40 minutes from booting the recovery
media to me logging in again on the restored system. This was my WFH-system
that backs up to a NFS share on the 1 Gbps network.
The restored workstation has a 256 GB SSD for the OS, and 3x 1 TB SSDs in a
RAID0 fashion for part of my homefolder. The system disk and raid were about
half-full.

-- 
Sorin Srbu, Serverdrift
Tele: 08-524 84166
Karolinska Institutet Universitetsbibliotek
Avdelningen för Verksamhetsstöd
Enheten för Teknikstöd och Bildproduktion


# They say you can't buy happiness, but you can buy a 
# motorcycle, and that's pretty damn close!

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20221213/5c94f74d/attachment-0001.sig>