Hello Stan,
Any successful "Full" backup will have all of the log files it needs,
self-contained in that saveset.
Only backups at levels "Incremental" or "Differential" will have
dependency upon logfiles from previous savesets.
Thanks,
_Scott
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Stan Horwitz
Sent: Friday, February 20, 2009 6:57 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Problem backing up Exchange 2003
Last week, our Exchange 2003 server choked due to a problem with the
transaction logs for the first storage group. It has two storage groups,
the
second one of which was fine. Users who's email is stored in that group
couldn't access our Exchange server, but users in the second storage
group
could get to their email.
The problem was caused when our Exchange server hit its maximum number
of
1,048,560 log files for the first storage group. Exchange created
E00ffff0.log and then stopped for the first storage group. The problem
went
away when our Exchange guru wiped out the transaction logs in order to
reset
the transaction log numbering back to E0000001.log.
Prior to this event, I was able to do IS back ups of both storage groups
concurrently by explicitly putting the storage groups into the save set
field in its client resource. Now, I can only get the entire IS back up
to
run. Resulting mminfo reports show only the second storage group in an
mminfo report. I will provide an mminfo report at the end of this msg.
How do I reset NetWorker to allow IS backups to handle both storage
groups
again? This is on a dual node (active-passive) Windows 2003 cluster, and
the
clients currently run the 7.4.4 version of NetWorker and the latest
Exchange
module. This Exchange 2003 server is backed up to tape on a Linux server
with NetWorker 7.4.2. Until yesterday, the physical nodes both the 7.4
version of the NetWorker client and the 5.1 version of the Exchange
module,
so I removed them and I also deleted the Legato folder on both cluster
nodes, then I installed the current version of the base client and the
Exchange module.
This did not help. I have a feeling that the Exchange backups prior to
when
this outage occurred are not recoverable because they reference
transaction
logs that don't exist now. Does that make sense? I suspect that the only
way
to resolve this issue is to delete all the CFI info for this client. But
does anyone else have a better way?
The total amount of Exchange data appears to be captured in the backups
now,
but there is no reference to the first storage group in the mminfo
report.
Here is a portion of the latest mminfo report:
N00054L3 exc1vs1 02/19/2009 10:53:41 AM 62 GB 10321476 tb
full MSEXCH:IS
Q00110L3 exc1vs1 02/19/2009 10:53:41 AM 449 GB 10321476 hb
full MSEXCH:IS
Q00177L3 exc1vs1 02/19/2009 10:53:41 AM 321 GB 10321476 mb
full MSEXCH:IS
Q00110L3 exc1vs1 02/19/2009 11:02:37 AM 138 GB 3919413268 cb
full MSEXCH:IS
N00054L3 exc1vs1 02/19/2009 07:22:20 PM 139 GB 2828924207 cb
full MSEXCH:IS/Second Storage Group
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
