March 19, 2009 at 9:30 am
Is there any problem with having two many backup schedules?
On sharepoint environment we currently have 3 nightly backups for all databses (local, share and evault online)
and then 1 backup to deve environment for one of databases
Performance wise, is there anything wrong with this? Would too many backups cause issues for our databases?
Thank you,
Ellie
March 19, 2009 at 9:30 am
Might cause issues for disk space, but it's not like it's going to wear out the databases.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
March 19, 2009 at 10:05 am
There may not be much issue on the backup. If you have enough disk space then no problem.
You might face a bit of slow responce while the backup is going on if your dbs size are big.
The best practice for Backup process is have a Full Backup once a week and then diffrential backup every night and Transaction Log backup every hour based on your data transaction. This will not put too much load on the server and also will take less time to complete with less disk space.
Hope this information will help you. 🙂
March 19, 2009 at 10:28 am
Atul DBA (3/19/2009)
The best practice for Backup process is have a Full Backup once a week and then diffrential backup every night and Transaction Log backup every hour based on your data transaction. space.
Hello Atul,
It would depend on their business requirements and how much data the business can afford to lose.
I would say the best practice is take frequent backups(again depending on your business needs) and verify your backups is a must.
March 19, 2009 at 10:52 am
I agree with Krishna view. The backup strategy depends on the business need and kind of cost and risk the business is ready to take.
Still taking a Full Backup everytime is not a good idea.
March 19, 2009 at 11:49 am
It really depends on whether you need to take distinct backups. If it's feasible to take one backup and then copy it to each location then you save on the following:
1) disk space on the original backup drives
2) network (you may be able to compress the files before copying them)
3) performance - the backup has to read every used page in the database, meaning a lot of disk usage. It also means that you are loading all of that information to the buffer cache which might be forcing other pages out. Obviously there is some additional CPU usage as well.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply