Is there a problem creating Diff Backups every hour instead of Logs and DIffs? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Restore all applicable files in a backup device in T-SQLRe-Run Backup Job in SQL AgentErrors restoring a differential backuponsite and offsite backup questionSQL Server Database Migration - Backup/Restore while Original DB still in ProductionSQL Server 2008 R2 differential backups much larger than expectedShould I create multiple maintenance plans to backup more than 200 User databasesCannot find reason why differential backups size reducedSQL Server Mirroring SetupWhat does WITH FORMAT do on a DIFFERENTIAL backup?

In predicate logic, does existential quantification (∃) include universal quantification (∀), i.e. can 'some' imply 'all'?

Is it fair for a professor to grade us on the possession of past papers?

Apollo command module space walk?

What is the meaning of the new sigil in Game of Thrones Season 8 intro?

Is it true that "carbohydrates are of no use for the basal metabolic need"?

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

3 doors, three guards, one stone

How widely used is the term Treppenwitz? Is it something that most Germans know?

How do I stop a creek from eroding my steep embankment?

Extract all GPU name, model and GPU ram

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

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

What is a non-alternating simple group with big order, but relatively few conjugacy classes?

When do you get frequent flier miles - when you buy, or when you fly?

Is it ethical to give a final exam after the professor has quit before teaching the remaining chapters of the course?

porting install scripts : can rpm replace apt?

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

How to run gsettings for another user Ubuntu 18.04.2 LTS

How come Sam didn't become Lord of Horn Hill?

Single word antonym of "flightless"

Why are Kinder Surprise Eggs illegal in the USA?

51k Euros annually for a family of 4 in Berlin: Is it enough?

Using audio cues to encourage good posture

When a candle burns, why does the top of wick glow if bottom of flame is hottest?



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



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Restore all applicable files in a backup device in T-SQLRe-Run Backup Job in SQL AgentErrors restoring a differential backuponsite and offsite backup questionSQL Server Database Migration - Backup/Restore while Original DB still in ProductionSQL Server 2008 R2 differential backups much larger than expectedShould I create multiple maintenance plans to backup more than 200 User databasesCannot find reason why differential backups size reducedSQL Server Mirroring SetupWhat does WITH FORMAT do on a DIFFERENTIAL backup?



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










share|improve this question




























    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.










    share|improve this question
























      2












      2








      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.










      share|improve this question














      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













      share|improve this question











      share|improve this question




      share|improve this question










      asked 6 hours ago









      Racer SQLRacer SQL

      3,12142566




      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























          • 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
            5 hours ago











          • You can certainly do that, if it fits your RPO/RTO objectives. I'd do a log backup after every diff backup just to ensure the log doesn't grow out of control.

            – Max Vernon
            16 mins ago











          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


















          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















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          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























          • 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
            5 hours ago











          • You can certainly do that, if it fits your RPO/RTO objectives. I'd do a log backup after every diff backup just to ensure the log doesn't grow out of control.

            – Max Vernon
            16 mins ago















          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























          • 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
            5 hours ago











          • You can certainly do that, if it fits your RPO/RTO objectives. I'd do a log backup after every diff backup just to ensure the log doesn't grow out of control.

            – Max Vernon
            16 mins ago













          3












          3








          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













          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












          share|improve this answer



          share|improve this answer










          answered 6 hours ago









          Max VernonMax Vernon

          52.4k13115232




          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
            5 hours ago











          • You can certainly do that, if it fits your RPO/RTO objectives. I'd do a log backup after every diff backup just to ensure the log doesn't grow out of control.

            – Max Vernon
            16 mins ago

















          • 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
            5 hours ago











          • You can certainly do that, if it fits your RPO/RTO objectives. I'd do a log backup after every diff backup just to ensure the log doesn't grow out of control.

            – Max Vernon
            16 mins ago
















          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
          5 hours ago





          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
          5 hours ago













          You can certainly do that, if it fits your RPO/RTO objectives. I'd do a log backup after every diff backup just to ensure the log doesn't grow out of control.

          – Max Vernon
          16 mins ago





          You can certainly do that, if it fits your RPO/RTO objectives. I'd do a log backup after every diff backup just to ensure the log doesn't grow out of control.

          – Max Vernon
          16 mins ago

















          draft saved

          draft discarded
















































          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.




          draft saved


          draft discarded














          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















          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







          Popular posts from this blog

          Möglingen Índice Localización Historia Demografía Referencias Enlaces externos Menú de navegación48°53′18″N 9°07′45″E / 48.888333333333, 9.129166666666748°53′18″N 9°07′45″E / 48.888333333333, 9.1291666666667Sitio web oficial Mapa de Möglingen«Gemeinden in Deutschland nach Fläche, Bevölkerung und Postleitzahl am 30.09.2016»Möglingen

          Virtualbox - Configuration error: Querying “UUID” failed (VERR_CFGM_VALUE_NOT_FOUND)“VERR_SUPLIB_WORLD_WRITABLE” error when trying to installing OS in virtualboxVirtual Box Kernel errorFailed to open a seesion for the virtual machineFailed to open a session for the virtual machineUbuntu 14.04 LTS Virtualbox errorcan't use VM VirtualBoxusing virtualboxI can't run Linux-64 Bit on VirtualBoxUnable to insert the virtual optical disk (VBoxguestaddition) in virtual machine for ubuntu server in win 10VirtuaBox in Ubuntu 18.04 Issues with Win10.ISO Installation

          Torre de la Isleta Índice Véase también Referencias Bibliografía Enlaces externos Menú de navegación38°25′58″N 0°23′02″O / 38.43277778, -0.3838888938°25′58″N 0°23′02″O / 38.43277778, -0.38388889Torre de la Illeta de l’Horta o Torre Saleta. Base de datos de bienes inmuebles. Patrimonio Cultural. Secretaría de Estado de CulturaFicha BIC Torre de la Illeta de l’Horta. Dirección General de Patrimonio Cultural. Generalitat ValencianaLugares de interés. Ayuntamiento del CampelloTorre de la Isleta en CastillosNet.org