SQL Server >
SQL Server Forums
>
SQL Server Disaster Recovery and Availability
>
Maintence Plan SQL Server 2005
Maintence Plan SQL Server 2005
- Hi all,
I'm a newbie on SQL Server and its planning and administration.
For backup purpose, I've created a Maintenance Plan designed with 2 tasks:
1- Backup Database Task, in full mode, scheduled every day at 11.00 PM on a dedicated volume (with option to create directory for every database)
2- I've attached in design panel, a Maintenance Cleanup Task, which it's delete .bak files older than 2 Days on dedicated backup volume;
It's a goog idea? any purpose about it?
Thanks a lot for support
Daniele- Changed TyperichbrownesqModeratorFriday, October 23, 2009 12:50 PM
All Replies
Well, lets think what does that give you:
1) If your database is lost or gets corrupted then you have a point to restore from.
2) You have a maximum exposure of 1 day of lost data as you don't (appear to) have any transaction log backups.
3) You are keeping 2 days worth of backups. This will help save on space.
Now, what you need to ask yourself is - is that enough?
Can you afford to lose a whole days data?
Would you ever need to restore a database over 2 days old?
Depending on the answers to those questions would define whether you need a more robust approach (eg transaction logs/differential backups)
I certainly think you've on the right track though.
HTH!
every day is a school day- Proposed As Answer byJoukoK Friday, October 23, 2009 7:23 PM
- Thanks for support,
For now it's required a basic database maintenance plan and for now I'll keep this settings.
Thank you very much and nice weekend
Bye! - If your database's recovery model is "full," you really need to backup your transaction logs. If you don't, your .ldf will continue to grow and consume more and more disk space. The space cannot be reused and a shrink cannot occur until a log transfer has occured. A full backup does not accomplish this.
