Compare commits

..

No commits in common. "master" and "chunking" have entirely different histories.

View file

@ -1,12 +1,5 @@
# backup2mdisc
**Now you can enjoy a _self-contained_ backup on each disc without chain-dependency across your entire multi TB backup set!**:
- **Independently decryptable** (and restorable) archives on each M-Disc.
- Automatic ISO creation and optional disc burning in the same script.
- **Fast compression via lz4**.
---
## Purpose:
1. Scans all files in a source directory.
2. Groups them into "chunks" so that each chunk is <= a specified size (default 100GB).
@ -52,17 +45,11 @@
---
## Usage:
```
./backup2mdisc.sh /path/to/source /path/to/destination [CHUNK_SIZE] [--create-iso] [--burn]
```
`./backup_in_individual_chunks.sh /path/to/source /path/to/destination [CHUNK_SIZE] [--create-iso] [--burn]`
## Examples:
```bash
./backup2mdisc.sh /home/user/data /mnt/backup 100G --create-iso
```
```bash
./backup2mdisc.sh /data /backup 50G --burn
```
`./backup_in_individual_chunks.sh /home/user/data /mnt/backup 100G --create-iso`
`./backup_in_individual_chunks.sh /data /backup 50G --burn`
## Dependencies:
- `bash`
@ -110,4 +97,13 @@
4. **Cross-Platform**
- On FreeBSD or macOS, you might need to tweak the commands for hashing (`sha256sum` vs. `shasum -a 256`) or ISO creation (`mkisofs` vs. `genisoimage`).
- For burning, Linux uses `growisofs`, macOS uses `hdiutil`, and FreeBSD may require `cdrecord` or another tool.
- For burning, Linux uses `growisofs`, macOS uses `hdiutil`, and FreeBSD may require `cdrecord` or another tool.
---
**Now you can enjoy the best of both worlds**:
- **Independently decryptable** (and restorable) archives on each M-Disc.
- Automatic ISO creation and optional disc burning in the same script.
- Fast compression via lz4.
This gives you a **self-contained** backup on each disc without chain-dependency across your entire 2TB backup set!