Default Schedules Confusion


Author
Message
Don Herberts
Don Herberts
New Member
New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)
Group: Forum Members
Posts: 7, Visits: 46
My predecessor was setting clients up with all 4 of the default templates?    In my scnario the client managed to fill up a 5TB in about 1 year.
It seem like only 1 schedule should be setup for each workstation.   Please correct me if I am wrong.


jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 84K
If all of those schedules are on the same job sending backups to the same destination, then that doesn't make sense at all.  Running all of those schedules on the same job would likely make a mess in terms of the retention policy too, since you'd have multiple schedules all contributing to the same backup sets, but the retention policy would evaluate the "aggregate" backups available at the destination rather than operating on a per-schedule basis.  If you need a complex schedule, then you should just create one from scratch rather than relying on a template.  But I can't think of any good use case for using multiple templates like that.

Don Herberts
Don Herberts
New Member
New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)New Member (17 reputation)
Group: Forum Members
Posts: 7, Visits: 46
Thanks for the response.   it looks like the client is only using the Increments Forever schedule based on the logs.   I guess my next question is why didn't subsequent backups deduplicate the data rather than filling up a 5TB external drive?

jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 84K
It would depend on what the retention policy is configured to do.  If you have access to the logs, they should include the retention policy that was in effect at the time that job ran, as well as how many of each type of existing backup that Reflect saw at the destination.  That should give an indication as to why Reflect did or didn't do something.

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search