August 7, 2014 at 1:16 pm
i'm taking a full DB backup it is very huge and it is takes around 24 hrs. after taking the 23 hrs suddenly my system shut down. so in that case again i have to take backup and wait for 24 hrs or Is there any alternative ???
August 7, 2014 at 1:22 pm
How big is the backup?
Are you backing up locally or across the network?
Are you compressing the backup?
Are you striping the backup?
All of these things can affect the speed of the backup.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 7, 2014 at 1:26 pm
hi
i am not taking this in real time, just i raised a question in this situation what we will do, will u plzz suggest me
August 7, 2014 at 1:41 pm
Take the backup and let it complete.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 7, 2014 at 2:13 pm
24 hours? Your database must be well over 1 TB or your hardware is very outdated.
If you compress backup, try to estimate its size + 20%, make sure that you have enough space to hold backup file. This is most likely the reason why your backup failed at the end.
Monitor backup progress from sys.dm_exec_requests view.
For future: partition your database, set old partitions to read-only, make one full backup, and then do partial backups on read-write filegroups. This will drastically reduce your backup space, time, resources.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply