SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Want some help in Recovery


Want some help in Recovery

Author
Message
vinnnu88
vinnnu88
SSC-Enthusiastic
SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)

Group: General Forum Members
Points: 197 Visits: 18
Hi Team,

There are two scenarios :

Scenario 1: I have a huge database which works on Mon-Sat 9 AM to 7 Pm .. can you help me how processed with the back up plan.

Do i need to take full backup daily? or diff backup ..

Scenario 2: Same Database for 24x7 days ..

NOTE : we are not using any high availability technique or third party tools.

Please help me over this.
Igor Micev
Igor Micev
One Orange Chip
One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)

Group: General Forum Members
Points: 25370 Visits: 5230
No, you don't need a Full backup every day.

Example:
Full backup once per week
Diff backup: once per day (or more times, it's up to you)
Log backup: every hour (or every half an hour, it's again up to you)

Igor Micev,
My blog: www.igormicev.com
vinnnu88
vinnnu88
SSC-Enthusiastic
SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)

Group: General Forum Members
Points: 197 Visits: 18
Thank you for your quick response..

You are right we have one full backup for a week and diff backup daily..

Now assume that we are taking log backup for every 30 min.. and the database crashed at 10:25 AM..

we will be having the latest log upto 10:00 AM.. then how about remaining 25 min data?
avi7070
avi7070
SSC-Addicted
SSC-Addicted (414 reputation)SSC-Addicted (414 reputation)SSC-Addicted (414 reputation)SSC-Addicted (414 reputation)SSC-Addicted (414 reputation)SSC-Addicted (414 reputation)SSC-Addicted (414 reputation)SSC-Addicted (414 reputation)

Group: General Forum Members
Points: 414 Visits: 1746
Hi,
It would be better to schedule FULL, DIFF, and TLog backups for production server databases. As you are not using any not using any high availability technique.
For Point in Time Recovery you will need TLog backups.

I will suggest below Backup Strategy:
FULL – Weekly
DIFF – Daily
TLog – Daily – 1 hour

You can use any suitable backup plan for your server databases, because Any Recovery from backups you need ‘FULL Backup’ or ‘FULL +DIFF’ or ‘FULL Backup – DIFF backup and Tail Log backup’
Eirikur Eiriksson
Eirikur Eiriksson
SSC Guru
SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)

Group: General Forum Members
Points: 124565 Visits: 21762
Strongly suggest that you use Ola Hallengren's SQL Server Maintenance Solution
Cool
vinnnu88
vinnnu88
SSC-Enthusiastic
SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)SSC-Enthusiastic (197 reputation)

Group: General Forum Members
Points: 197 Visits: 18
Perfect! thank you .. I think the tail log backup would help me the remaining 25 min data.

Now can you help me for second scenario where performance matters a lot. Again I think diff backup daily would be a performance issue.
Eirikur Eiriksson
Eirikur Eiriksson
SSC Guru
SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)SSC Guru (124K reputation)

Group: General Forum Members
Points: 124565 Visits: 21762
avi7070 (12/9/2016)
Hi,
It would be better to schedule FULL, DIFF, and TLog backups for production server databases. As you are not using any not using any high availability technique.
For Point in Time Recovery you will need TLog backups.

I will suggest below Backup Strategy:
FULL – Weekly
DIFF – Daily
TLog – Daily – 1 hour

You can use any suitable backup plan for your server databases, because Any Recovery from backups you need ‘FULL Backup’ or ‘FULL +DIFF’ or ‘FULL Backup – DIFF backup and Tail Log backup’



You must take into the account the activities in the databases, if you have lot of activity then you may have to increase the frequency of the backups, the differentials by the end of the week may come very large and an hour could be a too long interval for the Log backups.
Cool
Igor Micev
Igor Micev
One Orange Chip
One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)One Orange Chip (25K reputation)

Group: General Forum Members
Points: 25370 Visits: 5230
vinnnu88 (12/9/2016)
Thank you for your quick response..

You are right we have one full backup for a week and diff backup daily..

Now assume that we are taking log backup for every 30 min.. and the database crashed at 10:25 AM..

we will be having the latest log upto 10:00 AM.. then how about remaining 25 min data?

You can do a recovery for the remaining 25 minutes of data, but there is no guaranty.
You need a tail log backup.
Read this https://msdn.microsoft.com/en-us/library/ms179314.aspx
and this http://www.sqlskills.com/blogs/paul/disaster-recovery-101-backing-up-the-tail-of-the-log/
and then maybe you'll manage to return it.

Igor Micev,
My blog: www.igormicev.com
HanShi
HanShi
SSC-Insane
SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)SSC-Insane (24K reputation)

Group: General Forum Members
Points: 24128 Visits: 4060
Determine your backup strategy by the requirement for the restore (RPO and RTO). How much data is allowed to be lost (= RPO) and how long is data to be allowed unavailable (= RTO). Brent Ozar has some nice articles about it, like The 9 Letters That Get DBAs Fired.
If your RPO is like 15 minutes, you'll need to schedule your LOG backups at least every 15 minutes. If your RTO is 30 minutes, you'll need to be able to restore the FULL, DIFF and all LOGs within that 30 minutes.

Edit: fixed the link

** Don't mistake the ‘stupidity of the crowd’ for the ‘wisdom of the group’! **
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum








































































































































































SQLServerCentral


Search