Is there a problem creating only differential backups every hour? Announcing the arrival of...
What is the meaning of the new sigil in Game of Thrones Season 8 intro?
Significance of Cersei's obsession with elephants?
If my PI received research grants from a company to be able to pay my postdoc salary, did I have a potential conflict interest too?
When a candle burns, why does the top of wick glow if bottom of flame is hottest?
What would be the ideal power source for a cybernetic eye?
What does "lightly crushed" mean for cardamon pods?
Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?
Is "Reachable Object" really an NP-complete problem?
Do I really need recursive chmod to restrict access to a folder?
Is the Standard Deduction better than Itemized when both are the same amount?
Is it common practice to audition new musicians one-on-one before rehearsing with the entire band?
First console to have temporary backward compatibility
Is it cost-effective to upgrade an old-ish Giant Escape R3 commuter bike with entry-level branded parts (wheels, drivetrain)?
Using audio cues to encourage good posture
Fundamental Solution of the Pell Equation
Amount of permutations on an NxNxN Rubik's Cube
Why didn't Eitri join the fight?
How does the math work when buying airline miles?
How to write this math term? with cases it isn't working
What does the "x" in "x86" represent?
What causes the direction of lightning flashes?
What is homebrew?
If u is orthogonal to both v and w, and u not equal to 0, argue that u is not in the span of v and w. (
Denied boarding although I have proper visa and documentation. To whom should I make a complaint?
Is there a problem creating only differential backups every hour?
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)SQL Server restore sequence from multiple full, diff and log backupsWhat's a good SQL Server backup schedule?FULL recovery and differential backupsHow to group SQL Server files for restoring databaseSQL Server Differential Backup BloatErrors restoring a differential backupRestoring Database, creating new copy and use existing transaction logs for the original backup database to restore the NEW database to be current?Should I create multiple maintenance plans to backup more than 200 User databasesCannot find reason why differential backups size reducedHow to choose which backup files to restore when identical timestamps exist for diff and log backups
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have three databases which are not big. Every differential backup is roughly 50MB, then we have a full backup at midnight.
Is there any problem doing this?
I could take the full backup then logs, then diffs like 4 or 5 times a day, but storage is not a problem with this instance. I can afford to lose 1 hour of data, that's no problem, that's why I'm creating all of the diffs (I'm using full recovery mode). Then I can restore only the full + diff , instead of full + log + log + log + log + log + log + log + diff.
sql-server sql-server-2008-r2 recovery
add a comment |
I have three databases which are not big. Every differential backup is roughly 50MB, then we have a full backup at midnight.
Is there any problem doing this?
I could take the full backup then logs, then diffs like 4 or 5 times a day, but storage is not a problem with this instance. I can afford to lose 1 hour of data, that's no problem, that's why I'm creating all of the diffs (I'm using full recovery mode). Then I can restore only the full + diff , instead of full + log + log + log + log + log + log + log + diff.
sql-server sql-server-2008-r2 recovery
add a comment |
I have three databases which are not big. Every differential backup is roughly 50MB, then we have a full backup at midnight.
Is there any problem doing this?
I could take the full backup then logs, then diffs like 4 or 5 times a day, but storage is not a problem with this instance. I can afford to lose 1 hour of data, that's no problem, that's why I'm creating all of the diffs (I'm using full recovery mode). Then I can restore only the full + diff , instead of full + log + log + log + log + log + log + log + diff.
sql-server sql-server-2008-r2 recovery
I have three databases which are not big. Every differential backup is roughly 50MB, then we have a full backup at midnight.
Is there any problem doing this?
I could take the full backup then logs, then diffs like 4 or 5 times a day, but storage is not a problem with this instance. I can afford to lose 1 hour of data, that's no problem, that's why I'm creating all of the diffs (I'm using full recovery mode). Then I can restore only the full + diff , instead of full + log + log + log + log + log + log + log + diff.
sql-server sql-server-2008-r2 recovery
sql-server sql-server-2008-r2 recovery
edited 8 mins ago
Paul White♦
54.2k14288461
54.2k14288461
asked yesterday
Racer SQLRacer SQL
3,12342566
3,12342566
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Storage is not why you take log backups. You take log backups when the database is in full recovery model, and you need point-in-time recovery between full or incremental backups.
If your business can afford only 1 hour of lost data, then I'd typically setup nightly full backups for smaller databases, with log backups every 30 minutes during business hours (or even 24-hours per day).
If you have the database in simple recovery model, and each database is only a couple of hundred megabytes, you could simple take full backups every hour, or half hour.
Essentially, the decision comes down to answering these questions:
- What is my recovery point objective?
- What is my recovery time objective?
See Wikipedia for great details about what those two things actually mean.
If you're storing high-value, business-critical data in those databases, you should understand log backups, and the transaction log and recovery in general, to avoid being in a situation where you're unexpectedly missing data, or down for an extended period of time.
add a comment |
Log backups some times act as an escape hatch. Suppose your diff backup is 100 GB and your log backup is only 1 GB and you are having space issues and the diff failed. Now if a disaster happens at least you can recover from your log backups. This not applicable for your scenario but, this does happen. - Biju jose
Also bear in mind, with differential backups you can't restore to a point between them. Let's say you create full backup at 8 AM, differential at 12 PM and t-log at 1 PM. If a user made a mistake at 11 AM, you can only go either 8 AM or 12 PM, nothing between.
If you have a full backup 8 AM, t-log every hour, and differential at 12 PM, the user made a mistake 11:30 AM you can easily recover the DB until 11:30 AM (assuming you have all your t-log chain at least until 12 PM). - dbamex
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f234972%2fis-there-a-problem-creating-only-differential-backups-every-hour%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Storage is not why you take log backups. You take log backups when the database is in full recovery model, and you need point-in-time recovery between full or incremental backups.
If your business can afford only 1 hour of lost data, then I'd typically setup nightly full backups for smaller databases, with log backups every 30 minutes during business hours (or even 24-hours per day).
If you have the database in simple recovery model, and each database is only a couple of hundred megabytes, you could simple take full backups every hour, or half hour.
Essentially, the decision comes down to answering these questions:
- What is my recovery point objective?
- What is my recovery time objective?
See Wikipedia for great details about what those two things actually mean.
If you're storing high-value, business-critical data in those databases, you should understand log backups, and the transaction log and recovery in general, to avoid being in a situation where you're unexpectedly missing data, or down for an extended period of time.
add a comment |
Storage is not why you take log backups. You take log backups when the database is in full recovery model, and you need point-in-time recovery between full or incremental backups.
If your business can afford only 1 hour of lost data, then I'd typically setup nightly full backups for smaller databases, with log backups every 30 minutes during business hours (or even 24-hours per day).
If you have the database in simple recovery model, and each database is only a couple of hundred megabytes, you could simple take full backups every hour, or half hour.
Essentially, the decision comes down to answering these questions:
- What is my recovery point objective?
- What is my recovery time objective?
See Wikipedia for great details about what those two things actually mean.
If you're storing high-value, business-critical data in those databases, you should understand log backups, and the transaction log and recovery in general, to avoid being in a situation where you're unexpectedly missing data, or down for an extended period of time.
add a comment |
Storage is not why you take log backups. You take log backups when the database is in full recovery model, and you need point-in-time recovery between full or incremental backups.
If your business can afford only 1 hour of lost data, then I'd typically setup nightly full backups for smaller databases, with log backups every 30 minutes during business hours (or even 24-hours per day).
If you have the database in simple recovery model, and each database is only a couple of hundred megabytes, you could simple take full backups every hour, or half hour.
Essentially, the decision comes down to answering these questions:
- What is my recovery point objective?
- What is my recovery time objective?
See Wikipedia for great details about what those two things actually mean.
If you're storing high-value, business-critical data in those databases, you should understand log backups, and the transaction log and recovery in general, to avoid being in a situation where you're unexpectedly missing data, or down for an extended period of time.
Storage is not why you take log backups. You take log backups when the database is in full recovery model, and you need point-in-time recovery between full or incremental backups.
If your business can afford only 1 hour of lost data, then I'd typically setup nightly full backups for smaller databases, with log backups every 30 minutes during business hours (or even 24-hours per day).
If you have the database in simple recovery model, and each database is only a couple of hundred megabytes, you could simple take full backups every hour, or half hour.
Essentially, the decision comes down to answering these questions:
- What is my recovery point objective?
- What is my recovery time objective?
See Wikipedia for great details about what those two things actually mean.
If you're storing high-value, business-critical data in those databases, you should understand log backups, and the transaction log and recovery in general, to avoid being in a situation where you're unexpectedly missing data, or down for an extended period of time.
answered yesterday
Max VernonMax Vernon
52.5k13115232
52.5k13115232
add a comment |
add a comment |
Log backups some times act as an escape hatch. Suppose your diff backup is 100 GB and your log backup is only 1 GB and you are having space issues and the diff failed. Now if a disaster happens at least you can recover from your log backups. This not applicable for your scenario but, this does happen. - Biju jose
Also bear in mind, with differential backups you can't restore to a point between them. Let's say you create full backup at 8 AM, differential at 12 PM and t-log at 1 PM. If a user made a mistake at 11 AM, you can only go either 8 AM or 12 PM, nothing between.
If you have a full backup 8 AM, t-log every hour, and differential at 12 PM, the user made a mistake 11:30 AM you can easily recover the DB until 11:30 AM (assuming you have all your t-log chain at least until 12 PM). - dbamex
add a comment |
Log backups some times act as an escape hatch. Suppose your diff backup is 100 GB and your log backup is only 1 GB and you are having space issues and the diff failed. Now if a disaster happens at least you can recover from your log backups. This not applicable for your scenario but, this does happen. - Biju jose
Also bear in mind, with differential backups you can't restore to a point between them. Let's say you create full backup at 8 AM, differential at 12 PM and t-log at 1 PM. If a user made a mistake at 11 AM, you can only go either 8 AM or 12 PM, nothing between.
If you have a full backup 8 AM, t-log every hour, and differential at 12 PM, the user made a mistake 11:30 AM you can easily recover the DB until 11:30 AM (assuming you have all your t-log chain at least until 12 PM). - dbamex
add a comment |
Log backups some times act as an escape hatch. Suppose your diff backup is 100 GB and your log backup is only 1 GB and you are having space issues and the diff failed. Now if a disaster happens at least you can recover from your log backups. This not applicable for your scenario but, this does happen. - Biju jose
Also bear in mind, with differential backups you can't restore to a point between them. Let's say you create full backup at 8 AM, differential at 12 PM and t-log at 1 PM. If a user made a mistake at 11 AM, you can only go either 8 AM or 12 PM, nothing between.
If you have a full backup 8 AM, t-log every hour, and differential at 12 PM, the user made a mistake 11:30 AM you can easily recover the DB until 11:30 AM (assuming you have all your t-log chain at least until 12 PM). - dbamex
Log backups some times act as an escape hatch. Suppose your diff backup is 100 GB and your log backup is only 1 GB and you are having space issues and the diff failed. Now if a disaster happens at least you can recover from your log backups. This not applicable for your scenario but, this does happen. - Biju jose
Also bear in mind, with differential backups you can't restore to a point between them. Let's say you create full backup at 8 AM, differential at 12 PM and t-log at 1 PM. If a user made a mistake at 11 AM, you can only go either 8 AM or 12 PM, nothing between.
If you have a full backup 8 AM, t-log every hour, and differential at 12 PM, the user made a mistake 11:30 AM you can easily recover the DB until 11:30 AM (assuming you have all your t-log chain at least until 12 PM). - dbamex
answered 2 mins ago
community wiki
Comment Converter
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f234972%2fis-there-a-problem-creating-only-differential-backups-every-hour%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown