Backup Folders:
I have multiple machines that I keep backed up, including Linux, MacOS, Win.
All install CD's are also backed up (hate looking for those).
To save space on my laptops, I often delete stuff that I know is backed up.
So who's backing up the backup? Lose that backup drive, and potentially
some deleted files from laptops are lost.
Answer: 4-TB of NAS storage, which I keep synchronized with BC3.
Multiple machines produces lots of duplicate files and software,
so I try to keep that stuff organized in my backup drive by merging
duplicate software, pictures, music, etc.
Complications creep in ... if I merge a couple of huge directories on
the backup drive, some folders disappear .... others get organized in
a different high level structure (Win, Linux, MacOS, Music, Install, etc)
So how do I prevent lots of duplicate effort and keep the two mirrors in sync?
Couple of ways of looking at a solution:
1. Journalled activity.
Perform the merge/rearrangement on one disk and create a journal
of the actions performed.
Replay that journal on the mirrored drive.
2. Mirrored BC3 sessions.
Again, perform the logical rearrangement on one drive,
and mimic the same activities on a second BC3 session
on the second drive.
3. Write a script that performs the logical functions, and send
the commands through a BC3 interface to both sessions simultaneously.
4. Ignore BC3 as the driving interface, write some scripts that
logically do what I need:
* Detect the duplication
* Create an organizational structure
* run the script on both drives
* use BC3 to verify the drives are in sync.
Any thoughts? It's become a big problem.
Moving terabytes of data across a Gb network to synchronize isn't a great plan.
I have multiple machines that I keep backed up, including Linux, MacOS, Win.
All install CD's are also backed up (hate looking for those).
To save space on my laptops, I often delete stuff that I know is backed up.
So who's backing up the backup? Lose that backup drive, and potentially
some deleted files from laptops are lost.
Answer: 4-TB of NAS storage, which I keep synchronized with BC3.
Multiple machines produces lots of duplicate files and software,
so I try to keep that stuff organized in my backup drive by merging
duplicate software, pictures, music, etc.
Complications creep in ... if I merge a couple of huge directories on
the backup drive, some folders disappear .... others get organized in
a different high level structure (Win, Linux, MacOS, Music, Install, etc)
So how do I prevent lots of duplicate effort and keep the two mirrors in sync?
Couple of ways of looking at a solution:
1. Journalled activity.
Perform the merge/rearrangement on one disk and create a journal
of the actions performed.
Replay that journal on the mirrored drive.
2. Mirrored BC3 sessions.
Again, perform the logical rearrangement on one drive,
and mimic the same activities on a second BC3 session
on the second drive.
3. Write a script that performs the logical functions, and send
the commands through a BC3 interface to both sessions simultaneously.
4. Ignore BC3 as the driving interface, write some scripts that
logically do what I need:
* Detect the duplication
* Create an organizational structure
* run the script on both drives
* use BC3 to verify the drives are in sync.
Any thoughts? It's become a big problem.
Moving terabytes of data across a Gb network to synchronize isn't a great plan.
Comment