This commit is contained in:
2019-01-13 23:18:07 -08:00
parent 55478f81a9
commit f81da7821c

View File

@@ -70,12 +70,12 @@ Usage
The most frequently-used scripts are invoked as follows:
update-index.sh
* update-index.sh
Check the configured directories for added/deleted/changed files and
update the database.
prepare-disc.sh -br
* prepare-disc.sh -br
Select files for backup and create an ISO image. The options shown in the
example create a single-layer BD-R image with 20% of the available space
@@ -86,12 +86,12 @@ prepare-disc.sh -br
A copy of the database is included on every disc; the database is needed
for file recovery, as it tells us which files are on which discs.
burn-disc.sh backup_1.iso
* burn-disc.sh backup_1.iso
Burn an image to disc, and then read it back in to check that it was
burned without error.
progress.sh
* progress.sh
Estimate the number of discs needed to complete archiving. (It's hard-
coded to assume you're backing up to single-layer BD-R with 20% error
@@ -100,21 +100,21 @@ progress.sh
Some less-frequently-used scripts:
backup-schema.sh
* backup-schema.sh
Back up the database schema to a local file. This is mostly for
development use, if the schema changes.
backup-database.sh
* backup-database.sh
Back up the database schema and contents to a file, and use that to
replicate the database on another (presumably remote) MySQL server.
Before I started writing the database to each disc, this was how I made
sure I had an offsite backup of the database.
rebuild.sh
restore.sh
wait-on-drive.sh
* rebuild.sh
* restore.sh
* wait-on-drive.sh
These are mainly of use when restoring files from the archive. You could
just copy all files from all discs in sequence, but that would end up