Announcement

Collapse
No announcement yet.

backup API and t_logs

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • backup API and t_logs

    so normally when i do i full backup, the t_logs get zeroed out.. but the last 2 times i have tried to do a backup it says it completes sucessfully, but the t_logs are full.
    what would you check first?

    if i have performed a full backup that says it has completed sucessfully, can i delete the t_logs?

    i have a 30 gig t_log store, and it currently has 7 gigs free...
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

  • #2
    Re: backup API and t_logs

    A situation when backing up a DB and the log files are still there can cause if you have for example 2 DB in the same Storage group (SG) and one of the followings is taking place:
    1. You backup the DB's one after another in 2 different backup jobs.
    2. You backup only one DB.

    Because the t_logs are shared between all the DBs in thew same SG - backing up only one (or not all the DBs in the same SG), will not delete the t_logs:
    http://www.msexchange.org/articles/MF020.html
    http://www.msexchange.org/articles/U...ion-Store.html
    CNE 5, CCA, MCSE NT4.0-2003, MCSE 2003 messaging, Exchange Server MVP.
    Tzahi Kolber - IT Supervisor
    Polycom Israel.

    Comment


    • #3
      Re: backup API and t_logs

      What are you using to do the backup?
      If it is a third party tool, often doing a backup using ntbackup will get everything working again for your third party tool.

      Simon.
      --
      Simon Butler
      Exchange MVP

      Blog: http://blog.sembee.co.uk/
      More Exchange Content: http://exchange.sembee.info/
      Exchange Resources List: http://exbpa.com/
      In the UK? Hire me: http://www.sembee.co.uk/

      Sembee is a registered trademark, used here with permission.

      Comment


      • #4
        Re: backup API and t_logs

        tkolber, thank you. this is partially related to one issue...

        Because the t_logs are shared between all the DBs in thew same SG - backing up only one (or not all the DBs in the same SG), will not delete the t_logs:
        so if one didnt have a public folder, would that create a problem? right now, we have a webdev that has made an application that replaces the public folders all together, so they arent mounted.... not only that, the person that did the initial install screwed the public folders up. i am going to have to recreate them... although this has never caused my back up to fail.

        im just using NTbackup right now. i have the veritas package, but not for exchange. i want some feed back before i purchase a lack luster b\u software...
        its easier to beg forgiveness than ask permission.
        Give karma where karma is due...

        Comment


        • #5
          Re: backup API and t_logs

          If you backup the entire information store - ie you select the entire information store, then everything is backed up. The information store consists of both the mailbox store and public folder store.

          Simon.
          --
          Simon Butler
          Exchange MVP

          Blog: http://blog.sembee.co.uk/
          More Exchange Content: http://exchange.sembee.info/
          Exchange Resources List: http://exbpa.com/
          In the UK? Hire me: http://www.sembee.co.uk/

          Sembee is a registered trademark, used here with permission.

          Comment


          • #6
            Re: backup API and t_logs

            ok, so not to sound less intelligent than i am (heehe) but if the back-up is complete, then why didnt the logs truncate?

            and im sorry, but i wanna beat this horse a little bit.. so what happens if i just delete the oldest t-logs leaving only the uncommited logs? i dont want to enable circular logging, but the SMTP t_logs are getting full...

            thanks for your patience simon... im slightly exchange challanged.
            its easier to beg forgiveness than ask permission.
            Give karma where karma is due...

            Comment


            • #7
              Re: backup API and t_logs

              The main reason that the t_logs exist - is for DRP, when you have a backup of the DB from 2 days ago for example (with t_logs from then), but the DB is crashed.

              In order to get the "up to the minute" data - until the DB was crashed. You should have the last DB + the t_logs from then up to the crash time.

              In case of dismounting and remounting the DB - all the t_logs data is written to the DB, so in general you can then delete the t_logs, because all the data is there (but do it only if you are in catastrophic status).
              The thing is that if you need to restore the DB and you will not have the t_logs - you will be able to restore the DB (from 2 days ago for example) - and all the data that was created since WILL BE LOST !!!!!

              Hope was cleared enough
              CNE 5, CCA, MCSE NT4.0-2003, MCSE 2003 messaging, Exchange Server MVP.
              Tzahi Kolber - IT Supervisor
              Polycom Israel.

              Comment


              • #8
                Re: backup API and t_logs

                thank you.. that answers what i was wondering. in addition, i found this article that answers all the questions a had:
                http://support.microsoft.com/default.aspx/kb/924635

                i really dont know what was happening, but i had tried a full backup three times and it would not zero out the t_logs... so after getting frustrated a went thru some trivial troubleshooting steps and everything looked normal...

                the only thing i questioned was an RDP session thru term serv manager. i disconnected the RDP session and then tried the full back up again...

                low and behold, it worked that time.
                its easier to beg forgiveness than ask permission.
                Give karma where karma is due...

                Comment

                Working...
                X