Joe_Budden
asked on
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?
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?
ASKER
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
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
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?
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?
ASKER
To confirm - it's the backup software that purges the logs after a full backup, not Exchange itself?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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?