Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 723
  • Last Modified:

Backups purging logs

Scenario:

Exchange 2007 SP2 server, SCC cluster (Active/Passive). All SG's have an SCR target at SCR1 server. Full backup every night.

I understand that a Full backup will purge commited logs. Questions:

1. At what point are the commited logs, purged? After the backup has fully completed?

2. What actually purges the commited logs? The backup software or Exchange?

3. How does purging the logs work in relation to SCR?

4. How does Exchange/ backup software know when to purge the logs? Is there some flag set on the store saying that a full/inc has been completed succesfully?

5. Is it both the database AND the transaction logs that need to undergo a full/inc backup for the committed logs to be purged?
0
Joe_Budden
Asked:
Joe_Budden
  • 3
  • 2
1 Solution
 
rjpilcherCommented:
1. After it has completed a full backup

2. What software/method are you using?  Do you have a full/incremental backup schedule going?

3. Not sure - I would imagine that the changes would replicate

4. An archive bit is used to mark when full and differential backups were run.  A successful full backup will reset the archive bit and report to the database that it has been backed up.

5. What are you using for Backup software?  Or rather, how are you backing these up?
0
 
Joe_BuddenAuthor Commented:
Hello

1. Thanks

2.We are using Netbackup, we have fulls every night

3. Not sure what you mean? Does the SCR copy of logs have to be succesful for the commited logs to purge too?

4. Thanks

6. Netbackup
0
 
rjpilcherCommented:
The software should purge your logs - if it's not, then you may want to look at this:

http://www.symantec.com/business/support/index?page=content&id=TECH34676

As far as SCR:

http://technet.microsoft.com/en-us/library/bb676465(EXCHG.80).aspx

If you're just running full backups, why not just turn on circular logging and do a copy only backup instead of using an archive bit?  

0
 
Joe_BuddenAuthor Commented:
To confirm - it's the backup software that purges the logs after a full backup, not Exchange itself?
0
 
rjpilcherCommented:
The 3rd party software will do it in your case.

Additional Information:

Normal (or Full)   The normal backup process backs up the directory or Exchange store in its entirety, as well as the log files. To restore from a normal backup, only one normal backup is needed. A normal backup marks the objects it has backed up so that incremental and differential backups have context. This is accomplished by backing up the entire database and all the log files, and then purging the log files.

Copy   The copy backup is the same as a normal backup except no marking takes place to give incremental and differential context. This means that performing an incremental backup after a copy backup is equivalent to performing it before a copy backup. Use a copy backup to get a full backup of the directory or Exchange store without disturbing the state of ongoing incremental or differential backups.

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now