Ggthjy

How to call a function with default parameter through a pointer to function that is the return of another function?

How does debian/ubuntu knows a package has a updated version

Why do people hide their license plates in the EU?

The logistics of corpse disposal

Book where humans were engineered with genes from animal species to survive hostile planets

What does an IRS interview request entail when called in to verify expenses for a sole proprietor small business?

Coloring maths inside a tcolorbox

How does the particle を relate to the verb 行く in the structure「A を + B に行く」?

String `!23` is replaced with `docker` in command line

Why didn't this character "real die" when they blew their stack out in Altered Carbon?

Is there a (better) way to access $wpdb results?

Resolving to minmaj7

Sci-Fi book where patients in a coma ward all live in a subconscious world linked together

What does the "x" in "x86" represent?

Why am I getting the error "non-boolean type specified in a context where a condition is expected" for this request?

What does this icon in iOS Stardew Valley mean?

What's the meaning of 間時肆拾貳 at a car parking sign

porting install scripts : can rpm replace apt?

Error "illegal generic type for instanceof" when using local classes

Why are Kinder Surprise Eggs illegal in the USA?

Short Story with Cinderella as a Voo-doo Witch

Withdrew £2800, but only £2000 shows as withdrawn on online banking; what are my obligations?

How to align text above triangle figure

Check which numbers satisfy the condition [A*B*C = A! + B! + C!]

Is there a problem creating Diff Backups every hour instead of Logs and DIffs?

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}

2

So I have some databases ( 3 ) and they're not big. every Differential backup has like 50mb and then we have a full at midnight.

Is there a problem doing this?

I could make the full backup then logs, then diffs like 4 or 5 times a day, but storage is not a problem with this instance.

sql-server-2008-r2

share|improve this question

asked 5 hours ago

Racer SQLRacer SQL

3,12142566

add a comment | 

2

So I have some databases ( 3 ) and they're not big. every Differential backup has like 50mb and then we have a full at midnight.

Is there a problem doing this?

I could make the full backup then logs, then diffs like 4 or 5 times a day, but storage is not a problem with this instance.

sql-server-2008-r2

share|improve this question

asked 5 hours ago

Racer SQLRacer SQL

3,12142566

add a comment | 

So I have some databases ( 3 ) and they're not big. every Differential backup has like 50mb and then we have a full at midnight.

Is there a problem doing this?

I could make the full backup then logs, then diffs like 4 or 5 times a day, but storage is not a problem with this instance.

sql-server-2008-r2

share|improve this question

asked 5 hours ago

Racer SQLRacer SQL

3,12142566

share|improve this question

asked 5 hours ago

Racer SQLRacer SQL

3,12142566

share|improve this question

asked 5 hours ago

Racer SQLRacer SQL

3,12142566

asked 5 hours ago

Racer SQLRacer SQL

3,12142566

asked 5 hours ago

Racer SQLRacer SQL

3,12142566

1 Answer
1

active

oldest

votes

3

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:

1. What is my recovery point objective?


2. 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.

share|improve this answer

answered 5 hours ago

Max VernonMax Vernon

52.4k13115232

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hey thanks Max. But that's my question. I can lost 1 hr of data. thats no problem, that's why I'm creating all of them diffs ( I'm using full recovery mode ). Then I can restore only the ful + diff , instead of full + log + log + log + log + log + log + log + diff..
  
  – Racer SQL
  4 hours ago
  

  
  
  
  

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
});


}
});

draft saved

draft discarded

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

Name

Email

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-diff-backups-every-hour-instead-of-logs-and-diffs%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

3

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:

1. What is my recovery point objective?


2. 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.

share|improve this answer

answered 5 hours ago

Max VernonMax Vernon

52.4k13115232

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hey thanks Max. But that's my question. I can lost 1 hr of data. thats no problem, that's why I'm creating all of them diffs ( I'm using full recovery mode ). Then I can restore only the ful + diff , instead of full + log + log + log + log + log + log + log + diff..
  
  – Racer SQL
  4 hours ago
  

  
  
  
  

add a comment | 

3

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:

1. What is my recovery point objective?


2. 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.

share|improve this answer

answered 5 hours ago

Max VernonMax Vernon

52.4k13115232

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hey thanks Max. But that's my question. I can lost 1 hr of data. thats no problem, that's why I'm creating all of them diffs ( I'm using full recovery mode ). Then I can restore only the ful + diff , instead of full + log + log + log + log + log + log + log + diff..
  
  – Racer SQL
  4 hours ago
  

  
  
  
  

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:

1. What is my recovery point objective?


2. 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.

share|improve this answer

answered 5 hours ago

Max VernonMax Vernon

52.4k13115232

share|improve this answer

answered 5 hours ago

Max VernonMax Vernon

52.4k13115232

answered 5 hours ago

Max VernonMax Vernon

52.4k13115232

answered 5 hours ago

Max VernonMax Vernon

52.4k13115232