Circular Logging..?

At present we don't have circular logging switched on, in our exchange 2007, if I turn it on and do a VSS backup every night (does not truncate), will this be acceptable solution to keep the logs in check and be safe 'Exchange' wise..?

I am assuming that if the db ever corrupted, I could stop exchange, replace all files with the latest backup files and remount with no problems apart from the missing emails (we use an email archiving system as well so could bring back the missing emails easily)

Any thoughts/comments on my setup would be appreciated..?

Forgot to mention we also use Perfect Disc Exchange once a week on the db which 'automates the compaction and defragmentation of Exchange data stores'....
ServTechAsked:
Who is Participating?
 
netballiCommented:
0
 
Julian123Commented:
I am assuming that if the db ever corrupted, I could stop exchange, replace all files with the latest backup files and remount with no problems apart from the missing emails (we use an email archiving system as well so could bring back the missing emails easily)
>>Yes, that's correct. Essentially, your most recent back has a copy of your database made at the time of the backup. The log files have a copy of all writes (new messages, mails deleted, etc.) since that last backup. The main use of the logs is if your database gets corrupted and you need to restore it from backup. The restore will give you a copy of your database as it was last night and the logs will replay and update it with any changes made between that backup and the time of the corruption. If you have no log files, the restored copy will still work, it just will be current only up to the last backup. If you are OK with that, circular logging is a fine option.



0
 
Julian123Commented:
And if you're using a backup that doesn't truncate logs, circular logging will keep the disk from filling up. If logs aren't truncated by backups, they will accumulate forever until the disk is filled. To prevent that from causing an outage (the database will dismount), circular logging is a good option.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
ServTechAuthor Commented:
Thanks everyone for the info...

@ Julian123

>>Yes, that's correct. Essentially, your most recent back has a copy of your database made at the time of the backup. The log files have a copy of all writes (new messages, mails deleted, etc.) since that last backup.

So, there is no need to backup the log files each night, just the edb..? I was thinking that I would backup and reinstate all files following a problem, then bring back the missing emails (if any) from the archive library..? What happens if the log files are corrupted in some way, then I would have to 'replace all'..??
0
 
netballiCommented:
Hello,

in a real world scenario, if the log files corrupted then there would be loss of email that not been committed to edb database. Which would point a much more serious issue with OS or storage then just Log files.
0
 
ServTechAuthor Commented:
@ netballi

Yes, point taken...

One thing I could do is wait to see how much space is taken up by the end of the week, before the Perfect Disk Exchange is run (which will truncate and defrag), if this is acceptable space wise I could simply backup just the edb each night by VSS and truncate each Sunday by PD exchange (and not switch on circular logging)...? Sound about right..?

One thought, if for instance the drive completely died and the exchange folder could not be accessed, can you simply mount the edb in a new build, without having any log files to go with it..? I realise that you would only have the emails contained within it, but can you do that with exchange or would the mount fail..? That's always my fear...
0
 
Julian123Commented:
If you have a sudden server failure, the DB can be in a "dirty shutdown" state. You can run ESEutil to get it in a clean shutdown state where you can mount it even if there are no log files available.  You can also do a DB restore.

Either way, you can get working copy of the DB on the original server or a new server. Note that if you use a new server, it must be the same version and patch level as the current server.
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.

All Courses

From novice to tech pro — start learning today.