DB and Trans dump Time Conflict?

  • We dump our Databases to a local folder at 9pm nightly. We also dump trans logs to a local folder hourly (before copying them to a remote share). This means, in particlar, that at 9pm we are dumping both databases and transaction logs. Is there any conflict here?

    TIA,

    Bill

  • Not really. If you are makign a full backup of the databases and did a TL backup right before it then it is just a redundant process.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • I agree that it shouldn't cause any issues but I disagree that it's a redundant process. Running a tranlog backup before your full backup will preserve the tranlog and allow you to do a point in time restore to let's say 8:56PM.

    If I were you I would setup the tranlog backups so they run before the database backups. If you can change the Full backup job so that it runs the tranlog backups on step 1 and database backups on step 2, then it would work better. Then you can change you tranlog backup job so that it doesn't run at 9:00PM.

    I might be jumping the gun a bit... it depends on what you mean by FULL backup? Since you have a seperate job for your tranlog backup I assume you mean Full Database backup as opposed to differential.

    Edited by - danw on 06/11/2002 5:01:07 PM

  • Redundancy means you do more steps than absolutely needed. In this case all that is needed is a Full Backup. However making a TL backup first allows for two recorvery sets (both almost identical) meaning you have a redundant set, but that is great, no harm what so ever. And if something happened to the Full Backup you have another set there for you. I personally make a full backup of my databases to file after my last TL or Differnetial backup so I have a safety net.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • Thanks for the thoughts. But in our case the TL dump doens't happen at 8:56pm and a Full Backup at 9pm. The schedule has both slated for 9pm. That's why I wonder about any conflict or at least the value of that schedule.

    Bill

  • SO are you saying these are 2 different jobs? If so they should not conflict but depending on who gets to a datasource first it may block access from the other until completetion and this means the TL could be from the previous Full backup or the current. I would at minimum start the TL backups before the Full Backup just o ensure consitancy on which came first the FULL or the TL backup. May even want to make a combined job so order is handled.

    "Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)

  • Antares,

    What I was trying to say is in a full recovery model these are not redundent. If you wanted to have redundent data, then you would have to make a copy of both of these files and place them elsewhere (maybe a different planet if your paranoid like me). If you don't follow a full recovery restore model then yes, I agree, this is redundent except for the time between the tranlog backup and completion of the full backup.

    bill,

    There is a neat way to handle combining the jobs if you are using a maintenance plan. Just take the seperate jobs that were created and copy them into one job as two different steps. As long as you don't delete the maintenance plan you can use the plan id (you'll see this in the SQL the job is using) to run jobs against the group of servers in that plan.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply