GSLBermuda
asked on
Exchange 2010 DAG - Database Copy Size
Good day,
I have a server (Exchange 2010 SP1 Rollup 5) with a couple of mailbox databases. I created a 2nd mailbox server and configured a DAG with the two mailbox servers as a member of it. I create a copy of one of the mailbox databases, which seemed to go along, but then its status was failed. I re-ran it from the powershell, with the parameter to delete the exisiting database files and it seemed to do it, but still the copy end up as failed.
Now, without trying to fix the above issue immediately, I first would like to know, the original EDB file and its copy, are they supposed to be exactly the same in size and date/time if the database copy is working correctly? Or can the "target" be smaller in size for whatever reason. Or would a smaller "target" be an indication something went wrong? Or maybe the "seeding" can actually compress the size of the EDB?
Same question for the number and names of logfiles? Are they supposed to be identical all the time?
Thank you
I have a server (Exchange 2010 SP1 Rollup 5) with a couple of mailbox databases. I created a 2nd mailbox server and configured a DAG with the two mailbox servers as a member of it. I create a copy of one of the mailbox databases, which seemed to go along, but then its status was failed. I re-ran it from the powershell, with the parameter to delete the exisiting database files and it seemed to do it, but still the copy end up as failed.
Now, without trying to fix the above issue immediately, I first would like to know, the original EDB file and its copy, are they supposed to be exactly the same in size and date/time if the database copy is working correctly? Or can the "target" be smaller in size for whatever reason. Or would a smaller "target" be an indication something went wrong? Or maybe the "seeding" can actually compress the size of the EDB?
Same question for the number and names of logfiles? Are they supposed to be identical all the time?
Thank you
ASKER
OK, so what could be wrong if there is a huge difference and if the seeding doesn't go well and end up in a failed state? It's all LAN based traffic really. Is there a way to have a closer look at the seeding process?
how big is the database ? and how "huge" is the difference? can you take your db online for sometime ?
ASKER
We are actually talking about a quite small database, on the original side 280 MB, on the copy side little more than half of that (maybe 160MB). In another instance the difference was smaller.
Anybody else out there that can give me some examples of size differences (or not)
Anybody else out there that can give me some examples of size differences (or not)
There is no size difference when you seed size should be the same to the KB level
ASKER
Any idea what could be going wrong or where to check?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Bare in mind that the size if the size of the edb at the time you started the copy so the original one might grow just a bit in the time it is copied but I wouldn't expect huge differences unless the time to copy is very big. also note that the target copy will reserve the space from the start so it won't start small and grow it will start as big as it should be and then copy the content to it
the logs are all the same size 1 meg and the names should be exactly the same