Yeah I don’t know any backup system that works the way you laid it out here.
All I know of have to eventually roll up the backups into a consolidated
version. This is done two ways.
1. Periodic Full backup (Classic method, pulling a full new copy of the data
from the backup target, does not
Thanks a lot, Brock, for your comprehensive post and also to the others. I
haven't fully worked through your example cases yet, but it will certainly
help me to get my head around it all. Maybe it helps if I provide a few
more details about how the data/images are organized:
I run a Linux bas
As I wrote earlier, this looks more like archiving plan, not a backup
one (or a combination of backup and archiving). But more to the point -
in case of backups you have to have a verification plan and periodical
restore tests. In case of archiving you need to have a verification plan
(i.e. eve
Thanks a lot, Brock, for your comprehensive post and also to the others. I
haven't fully worked through your example cases yet, but it will certainly
help me to get my head around it all. Maybe it helps if I provide a few
more details about how the data/images are organized:
I run a Linux base
You will have some complexity with the size of your data and the size of your
loader. Unless your data compresses really well.
Does it have more than one tape drive? Your total loader capacity is 48 TBytes
raw, and you need 2x your full size to do Consolidations or new Fulls or you
have gaps i
Hello everybody,
I'm in the process of developing a regular backup-strategy and found that I
need some assistance. Here are the parameters in short:
- 35TB of medical imaging data
- daily increment of 50-60GB
- one site, 10Gb/s Backbone
- Overland NEOs LTO7 Storageloader, 8-bay.
attached to
- d
