If you don't like UUIDs, maybe...
I assume you have some sort of script to do the backup, which assumes a given disk device.
If your USB device is mounted on, say, /tmp/usb.disk, so your pick0 entry is
tape /tmp/usb.disk 500 f lx # tape 3
You could do the following:
1. label all USB disks you're ever going to use
# e2label /dev/??? "mylabel"
Note - you only need to know the physical mount point once when you label the disks
2. run your backup from a shell script which mounts the device in the correct place.
This needs to run as root or sudo.
-----
#!/bin/bash
umount /tmp/usb.disk
mount -L mylabel /tmp/usb.disk
if grep -qs '/tmp/usb.disk' /proc/mounts; then
#
# USB disk is now mounted on a known mount point
# run a D3 command to do backup
#
d3tcl "some D3 command to run your backup"
else
#
# Oops - some error on mount
#
echo "Could not mount external disk !"
fi
-----
Of course, you could label each day's USB something different and change the script to suite.
Note the d3tcl command requires some environment variables. Check the manual.
------------------------------
Bryan Buchanan
Manager
WebbTide Systems Pty Ltd
Morayfield QLD AU
------------------------------
Original Message:
Sent: 03-04-2024 12:40
From: Richard Ginsburg
Subject: Linux and USB drives - fixing the name
I have quite a few customers running Rocky Linux as their OS for D3. Every single one of them has the same problem. A reboot of Linux, not a total shutdown, changes the designation of the USB drives that they use for nightly on-site backups. What was /dev/sdb might come up as /dev/sdd on a reboot. Since they are designated in the PICK0 file for FILE-SAVES, this creates a major problem.
How can I prevent this problem?
------------------------------
Richard Ginsburg
President
Ginsburg Consulting
Manassas VA US
------------------------------