Comments
Sort by recent activity
I understand the reasoning behind your implementation, and I appreciate the added granularity SQL Backup provides with retention measured in hours in addition to days.
However, with all due respect, I find your implementation a bit too esoteric. Since SQL Backup is replacing functionality within EM, it makes sense to me to model the behavior of your application after theirs. I'm all for having improvements, but I don't think changing the fundamental meaning of what a "day" constitutes is valuable or necessary. I think it better to let the DBA figure out what they want to retain and what they want to discard and then give them intuitive tools to get the job done.
Though well-intentioned, I don't think your implementation is the least bit intuitive.
Anyway, I'm using an ERASEFILES value of 23h now instead of 1 day and I'm using a single script for all my databases so everything is working to my satisfaction.
Thanks!
Neil / comments
I understand the reasoning behind your implementation, and I appreciate the added granularity SQL Backup provides with retention measured in hours in addition to days.
However, with all due respect...
Interesting, I'm having the opposite problem. I want only one copy of backups on disk but with ERASEFILES = 1, the previous night's backups are NOT deleted. I could use ERASEFILES = 23h, but I have a lot of Agent jobs to edit... / comments
Interesting, I'm having the opposite problem. I want only one copy of backups on disk but with ERASEFILES = 1, the previous night's backups are NOT deleted. I could use ERASEFILES = 23h, but I ha...
Success. ~thanks! / comments
Success. ~thanks!