Re: the backups - is that merely for performance reasons?
-Original Message-
From: bounce-9366658-8066...@lyris.sunbelt-software.com
[mailto:bounce-9366658-8066...@lyris.sunbelt-software.com] On Behalf Of
Campbell, Rob
Sent: 01 July 2011 00:19
To: MS-Exchange Admin Issues
Subject: RE: 20
Sorry to hijack the thread but conitnuing on the thread of backup, is it
suicidal to backup the active db?
Problem we run into in our environemtn as we plan out migration to 2010 is
that we have one prod site & one DR site & our backup library & mgmt console
both reside in prod.
So, in other to p
As far as I'm concerned, the only reason to backup the passive copies is to
ensure log truncation happens properly on the active copy when the backup is
finished. Now, this may just be unique to our backup solution (Legato /
Networker) but I'd read the docs for your solution.
Richard
From: bou
With Windows backup I had to backup the Active DB in our CCR cluster. Our 2010
plan is to have 2 DB copies onsite and one in a DR site. All of our Exchange
2010 servers are on VMware and we snapshot them nightly. Also, we use Quest's
Archive Manager so we have a copy of all mail there. That's ou
It's not "suicide" to back up an active db, but you can run into problems
backing up the target db of a mass migration while the migration is going on.
Backup suspends committing log files to the DB while the backup is running.
Exchange has a threshold of the maximum number of uncommitted log f
