#2
|
||||
|
||||
The space in the container is shared, so the size can grow and shrink as needed. You can, of course, set a quota or minimum.
As I indicated in the blog post about the new snapshot capabilities, we can't control the number of snapshots that are retained, nor their overall lifespan. So, no: continue to use Time Machine as well. It's important, in my opinion, to use both different backup destinations (separate drives, online, etc) as well as different programs (e.g. us, Time Machine, Backblaze, etc). That way, you protect yourself against hardware issues, corruption, and even mistakes that one application might make. After all everything has bugs - but by having some redundancy in application, you can help to protect yourself against that too. I certainly practice what I preach here, and use all three across a lot of media.
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
dest volume not mounting for sched | Dewdman42 | General | 1 | 10-20-2015 12:06 PM |
Cloning an entire disk as opposed to a volume? | peychaud | General | 3 | 06-13-2012 11:05 AM |
Back up gone wrong. SD writes files to Start Volume??? | MasterDomino | General | 7 | 05-02-2011 10:50 AM |
Ownership & Read-only Volume - Help! :) | binaryeric | General | 1 | 01-30-2010 06:03 PM |
SD V2 not being able to save settings | bammi | General | 1 | 12-01-2005 10:35 AM |