Re: Flushing Exchange Logs
- From: "Kevin Weilbacher [SBS-MVP]" <kweilbacMVP@xxxxxxx>
- Date: Fri, 22 Jun 2007 22:50:30 -0400
Are you going to use Jeff's SwingMigration for this? If so, perhaps you can
contact Jeff for some assistance.
As far as theVSS corruption, what are the exact error messages you are
getting?
--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"
"SVCTech" <SVCTech@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A08BB7C7-D44B-45CC-AC21-1389B5B4BA83@xxxxxxxxxxxxxxxx
Hello everyone,
I will be taking a client from an SBS 2003 Standard network to a 2003
Enterprise server with Exchange Standard Edition. My original plan
involved
me installing Exchange 2003 in the same Exchange organization and moving
mailboxes, I've tested it and it works. However, I've had a new
requirement(s) placed on me. They want to keep the same server name and
"forklift" the Exchange database to the new server, which means I'm going
to
have to swing this. I understand most of what I have to do.
My problem is the following:
We cannot get a good backup of Exchange due to corruption in VSS on the
existing server and we are rapidly running out of disk space so there is
no
room for the VSS copy of the database even if it wasn't corrupt. Is there
a
way by which I can commit the data in the transaction logs to the Exchange
Database before I copy it to my intermediate server without taking an
online
backup of the database and without losing the data that has not yet been
committed to the database?
Thanks in advance.
--
Lincoln Spencer
SVC
SBS MCP
.
- Prev by Date: Re: Moving mailboxes to another partition
- Next by Date: Re: SBS 2003 and the outside world
- Previous by thread: Re: Flushing Exchange Logs
- Next by thread: Re: Do I need multiple public IP's
- Index(es):
Relevant Pages
|
Loading
