2010 server in Dag config. need to move logs

I have 2 EX 2010 servers in a dag. 1 of the servers needs a bigger drive for the logs
Can anyone comment on my plan to move these logs
currently the logs for both servers are sitting on the I drive on each
I was hoping I could
1) stop mail services on both servers
2) manually copy the contents of the I drive on server 1 to the new drive (J:)
3) Via disk management reassign the current I: drive a new drive letter and reassign the J: drive to now be I:
4) start all mail services
Will this plan work or is there something I may be missing
TIA
WP

The Exchange 2010 forum is
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvravailabilityandisasterrecoverylegacy
If you dismount the database server 2 won't take over.
If I were to do what you are doing I would add the new disk to Server 2 as J:. Then I would suspend the database copy on Server 2. I would then do a normal file copy to the J: drive, leaving the directory structure in tact. I would then make the
old disk the K: drive, and new disk the I: drive, and then Resume the mailbox database copy on Server 2. Once the copy on Server 2 has caught up and no longer has a Copy Queue or Replay Queue, I would move the active mailbox database copy to Server 2, and
then repeat on Server 1.

Similar Messages

2 servers can do "Mirroring" are there 3 servers in Sharepoint 2010 Server mirroring?

Hello Community
    In providing availability using Sharepoint 2010 Server using "Mirroring"
you need a "Principal, Mirror and a Witness".
    Logically speaking the principal and mirror I would say are the two servers
that are involved in Sharepoint 2010 Server availability.
    The question is in a 2 server farm what is the "Witness" in availability,is it a Sharepoint
2010 Server, is it the Domain Controller or is it a separate server and do you have
to purchase a copy of Sharepoint 2010 Server to run it on?
    Thank you
    Shabeaut

For SharePoint web front end servers you use multiple web servers and a load balancing service or device. SharePoint application server will auto load balance. For database servers you can use database mirroring. The running SQL server is the Primary,
the backup SQL server is the Mirror and the Witness is any other SQL server.
Be aware that SQL mirroring is going away in the future:
http://msdn.microsoft.com/en-us/library/ms190202.aspx
More on mirroring:
http://msdn.microsoft.com/en-us/library/ms189852.aspx (click the dropdown on the page for each SQL version.
Mike Smith TechTrainingNotes.blogspot.com
Books:
SharePoint 2007 2010 Customization for the Site Owner,
SharePoint 2010 Security for the Site Owner

Best Way to move MB database from single XCH 2010 to 2013 DAG

Hi,
We are migrating from a Single Exchange 2010 sp3 server to a 2-node exchange 2013 DAG cluster, located in another AD site.
I can move a mailbox from 2010 to 2013 without issue, but the WAN link between 2010 and 2013 is very small.
It will take us too long to move all mailboxes with move-mailbox over the line.
Is there another way to move the mailboxes or Databases more quickly?
I was thinking about copying the DB's to a physical disk from 2010 and then move and mount it on 2013. Is that even possible? I explored the possibility to seed the DB to 2013, but don't have the option to do so. 2010 is installed on 2008R2 standard.
We prefer a short downtime and move over everthing in one go as opposed to having coeexistance for longer period of time to allow the move mailbox over the WAN to complete.
Thanks for any suggestions.

You can't move the databases from Exchange 2010 to Exchange 2013.
I can think of three options.
1. Move the Exchange 2013 server to the same LAN as the Exchange 2010 server, move the mailboxes, then move the server back.
2. Move the Exchange 2010 server to the same LAN as the Exchange 2013 server and move the mailboxes.
3. Install a new Exchange 2010 server on the same LAN as the current Exchange 2010 server, create a DAG, add mailbox database copies on the new Exchange 2010 server, move that server to the same LAN as the Exchange 2013 server, activate the databases
on that LAN, and then move the mailboxes.
3a. A variation of #3 is to build the Exchange 2010 server on the same LAN as the Exchange 2013 server and perform a manual seed of the database copies. This is more trouble than option 3.
Moving Exchange servers between sites is possible but there are other issues you would need to solve. You might be best off just getting a temporary increase in your WAN link capacity for the period of the mailbox move.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

MS Project 2010 Server - How to move a single MS Project plan and SharePoint Project site from a PWA server to another PWA server (one at a time)

MS Project 2010 Server
How to move a single MS Project plan and it's SharePoint project site from a PWA server to another PWA server (one at a time)
I have 2 Project PWA servers, i know how to copy all the databases (Publishing, Draft, Reporting, archive, content) from one SQL server and copy it to the other PWA server so both server can be identical.
I need to only move a single project from a PWA server to another,
Moving the Project plan, actual time data, SharePoint site with all it's content
Is there a 3rd party tool that can be added on to the server to help me move single project plans? to different PWA servers?
-Isaack

Visit my friends at FluentPro and try FluentBooks
http://www.fluentpro.com/productsfluentbooks2013.html
they have a 2010 version also.
Hope that helps,
Thanks, Eric S. Pcubed

SP 2010 upgrade fails Error C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\config\WEBCONFIG.ACCSRV.XML, does not have element "configuration/configSections/sectionGroup[@name='SharePoint']"

I was upgrading my SP 2010 server to SP1 but at step 8 i get this error. I cleared configuration cache, moved the file out of the folder, got the same file from other farm where upgrade went smooth, but no success yet. I am at loss.
So i have another farm in SP1. As a fall back option i was thinking to move content database on that server and start hosting site there but now i find out pre sp1 content databse cannot be moved to sp1 farm just through content database migration.
Do only choice i have is to build dummy sp 2010 environment, move content database there and do upgrade there and move it to final production environment?
Is there anything else i can do for either upgradeing the current sp 2010 or moving it to new 2010 already on SP1?
Can pre sp1 2010 content db be moved to sp2013 sp1 directly?
Adit

Hi ,
How many SharePoint servers do you have? If you have more than one SharePoint server, you need to install SP1 on all servers in the farm.
Make sure you run SharePoint 2010 configuration wizard using “Run As administrator”.
Please check the log to find more information about this issue.
In addition, here is a similar post, please take a look at:
http://sharepointnomad.wordpress.com/2014/02/23/fixing-sharepoint-2010-configuration-wizard-error-webconfig-accsrv-xml-does-not-have-element-configurationconfigsectionssectiongroupnamesharepoint-or-it-is-invalid/
Best Regards,
Wendy
Wendy Li
TechNet Community Support

Exchange 2010 server with 2 DAG servers - DAG1 and DAG2 - backup with 2 DPM servers one for each DAG server

Hello,
Please advice, i have an Exchange 2010 server with 2 DAG servers - DAG1 and DAG2 - backup with 2 DPM servers, one for DAG1 and one for DAG2 is it possible ?

Hi,
I confirmed with Exchange support team that DAGs could be backed up separately.
Meanwhile backup database is important if you need to recover both Exchange server settings and database. See:
Recover a database availability group member server
http://technet.microsoft.com/en-us/library/dd638206.aspx
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

What needs to be done to rebuild a current Sharepoint 2010 Server farm to work as a Sharepoint 2013 Server farm?

Hello Community
    Currently I have a Sharepoint 2010 Server farm.
    One server contains the database and DNS server
because it is the the domain controller.
    The other server Contains the Sharepoint 2010 Server software
and is the the application server where applications such as Metadata,
UPs, etc, reside (including web applications with sites built with the UI).
    Now I am going to change to Sharepoint 2013 Server because currently
there is no newer version of Sharepoint available.
    I am ready to rebuild the current Sharepoint 2010 farm configuration into
a Sharepoint 2013 Server farm from scratch.
    The question is what do needs to be added and\or changed to make the current
Sharepoint 2010 Server farm configuration work as a Sharepoint 2013 Server farm?
    Thank you
    Shabeaut

There is no direct in-place uprade method for SharePoint 2010 to 2013. You need to create a new SharePoint 2013 farm from scratch and attach service and content databases to upgrade them. Check out Upgrade
to SharePoint 2013 for more information about the process.
If you have another server, you would install SharePoint 2013 on this. If you don't, you'll need to remove SharePoint 2010 from your existing server and then install SharePoint 2013. Check out Hardware
and software requirements for SharePoint 2013 before starting to make sure your server meets the minimum requirements for SharePoint 2013:
Web server or application server in a three-tier farm
Pilot, user acceptance test, or production deployment of SharePoint Server 2013 or SharePoint Foundation 2013.
12 GB memory
64-bit, 4 processor cores
80 GB for system drive
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Exchange 2013 ECP shows no databases. User moves fail referencing an old database of a crashed 2010 server

Our old 2010 server was migrated to 2013 but before removal, the 2010 server failed. Now when I go to my ECP > Servers > Databases, the list is empty. I can't move any users either as the list population fails because it can't find the
old database from the 2010 server. I thought I removed it all from ASDIEdit but something is lingering. Mail is flowing fine at the moment.

Server has been rebooted several times with no success. These are production mailboxes.
Log Name: Application
Source: MSExchangeTransportDelivery
Date: 4/14/2014 5:53:45 AM
Event ID: 5006
Task Category: Routing
Level: Warning
Keywords: Classic
User: N/A
Computer: MAIL1.onshoreit.local
Description:
Cannot find information about owning Mailbox Server CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local
for database CN=DFMCO_PUB_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local in routing tables with timestamp 4/14/2014 10:53:45
AM. Recipients will not be routed to this database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeTransportDelivery" />
<EventID Qualifiers="32772">5006</EventID>
<Level>3</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-14T10:53:45.000000000Z" />
<EventRecordID>663745</EventRecordID>
<Channel>Application</Channel>
<Computer>MAIL1.onshoreit.local</Computer>
<Security />
</System>
<EventData>
<Data>CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>CN=DFMCO_PUB_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>4/14/2014 10:53:45 AM</Data>
</EventData>
</Event>
Log Name: Application
Source: MSExchangeTransportDelivery
Date: 4/14/2014 5:53:45 AM
Event ID: 5006
Task Category: Routing
Level: Warning
Keywords: Classic
User: N/A
Computer: MAIL1.onshoreit.local
Description:
Cannot find information about owning Mailbox Server CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local
for database CN=DFMCO_MAIL_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local in routing tables with timestamp 4/14/2014 10:53:45
AM. Recipients will not be routed to this database.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeTransportDelivery" />
<EventID Qualifiers="32772">5006</EventID>
<Level>3</Level>
<Task>4</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-04-14T10:53:45.000000000Z" />
<EventRecordID>663744</EventRecordID>
<Channel>Application</Channel>
<Computer>MAIL1.onshoreit.local</Computer>
<Security />
</System>
<EventData>
<Data>CN=MAIL\0ADEL:437877b5-6216-44ea-a145-997cba794f45,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>CN=DFMCO_MAIL_DB,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=OnshoreIT,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=onshoreit,DC=local</Data>
<Data>4/14/2014 10:53:45 AM</Data>
</EventData>
</Event>
The 2010 box is dead and unable to be restored.

How to Remove a bad mailbox server and add new mailbox server to DAG and copy mailboxes over

DAG
2- cas - VM
2- mbx- physical blade (mbx1, mbx2)
5- mailbox databases
OS: Win 2008 SP2
Exchange 2010SP3
Storage: Tegile Disk jbod Luns
We have bad disks on mbx1. our plan is to get a new blade to replace the bad one named mbx3. we need to do this asap since we are running on 1 server without failover capability
How can I safely:
1. Add a new mailbox server to the DAG
2. Copy\Move the databases from the old (passive) server to the new server
3. Remove the bad mailbox server from DAG

You'll want to make sure that the new server is on all the same networks that the server you are removing is on, specifically networks that are DAG networks. Also, you'll want to avoid using Windows Network Load Balancing on the new mailbox server
since it will be part of the DAG. Also, just as you did with the current DAG members, ensure that the disk drive letters match the existing disks that hold databases & logs. Other than that, it's as simple as you have stated.
1.) Once you have the new mbx server built & configured with the mailbox role, you can use:
Get-DatabaseAvailabilityGroup "Name of DAG" | Add-DatabaseAvailabilityGroupServer "Name of New MBX Server"
2.) Add the databases to the new DAG member:
Add-MailboxDatabaseCopy "name of database" -MailboxServer "name of new DAG member" -ActivationPreference "[you decide based on the server replacing mbx1]"
3.) Once your databases are Mounted and/or Healthy on the new DAG member, you'll want to remove the databases from the "bad" server (make sure they are all passive on the server first):
Get-MailboxDatabaseCopy "SERVER\Database" | Remove-MailboxDatabaseCopy
4.) Once all of the databases are removed from the "bad" DAG member, remove him from the DAG:
Get-DatabaseAvailabilityGroup "Name of DAG" | Remove-DatabaseAvailabilityGroupServer "Name of old MBX Server"
Before you pull the blade, uninstall Exchange Server gracefully, as this will save you AD & Exchange headaches later on.
Petri has a pretty good GUI walk-through for some of the above steps here:
How to Configure Database Availability Group for Exchange Server 2010
Woody Colling, MCITP Exchange 2010
--The incentive for the experts to answer posts is to get their replies marked as helpful, or as the answer to our questions, help them help us, mark posts accordingly--

Need to "move" failover to different interface/port

Sorry if this is the wrong area, we have so seldom had questions that were not otherwise handled I don't frequent this area.
How difficult is it to change the interface used for active/standby failover? It's a working, already configured pair with standby, but I need to move the crossover cable and tell them to use a different interface.
ASA 5510 pair, already set up and working with failover that was originally configured on Ethernet port 0/3 by the senior network admin. It appears that from his use of interfaces or ports he used things straight out of examples on the web, including the interfaces used.
The senior network admin retired last spring and left me "in charge", gee, thanks.
I need to make some changes and need an Ethernet port for a new important project.
The Management 0/0 interface is unused and shutdown. We manage via inside interface from a specific subnet inside so don't need the dedicated management interface.
I want to move failover FROM Ethernet 0/3 TO Management 0/0
*This is the current setup:
Result of the command: "sh run failover"
failover
failover lan unit primary
failover lan interface failover Ethernet0/3
failover link failover Ethernet0/3
failover interface ip failover 169.254.255.1 255.255.255.252 standby 169.254.255.2
*And this is the current interface configuration for 0/3 and Management:
interface Ethernet0/3
description LAN/STATE Failover Interface
interface Management0/0
speed 100
duplex full
shutdown
nameif management
security-level 0
no ip address
ospf cost 10
I know it can run on the Management 0/0 interface because I see a lot of "how to configure" as if the ASA is brand new and several examples out there indeed show it being setup on Management.
I'm looking for how to take an ASA pair that is currently configured and has a working functional failover configuration and simply "move failover" to a different hole or change the interfaces used for the "heartbeat" as it were.
I assume it's not hard - but I also assume there's a specific sequence of events that must take place to prevent the pair from going into failover and switching lead roles...........
For example - would I shut off or turn off failover, and if so how, and on which ASA (frankly, I'm not sure how to access the secondary or standby if this must be done from or on the standby unit as I've never done that "deep" a config before)
CLI is fine - I'd be just as comfortable in either ASDM or cli.
I sure hope this makes sense - I'm more of a troubleshooter and fixer than a designer or network engineer....
And many many thanks - getting this moved will free up the interface I need and can really make a big dent in my project list while the supervisor is on vacation this week! I'd love to have this done and working before his return.
Oh, in case it does matter as I've been told, this is the Currently running license and versions shown here:
Cisco Adaptive Security Appliance Software Version 8.4(4)1
Device Manager Version 6.4(7)
Compiled on Thu 14-Jun-12 11:20 by builders
System image file is "disk0:/asa844-1-k8.bin"
Config file at boot was "startup-config"
VRDSMFW1 up 141 days 4 hours
failover cluster up 141 days 4 hours
Hardware: ASA5510, 1024 MB RAM, CPU Pentium 4 Celeron 1600 MHz
Internal ATA Compact Flash, 256MB
BIOS Flash M50FW080 @ 0xfff00000, 1024KB
Encryption hardware device : Cisco ASA-55x0 on-board accelerator (revision 0x0)
Boot microcode : CN1000-MC-BOOT-2.00
SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03
IPSec microcode : CNlite-MC-IPSECm-MAIN-2.06
Number of accelerators: 1
0: Ext: Ethernet0/0 : address is 0024.972b.e020, irq 9
1: Ext: Ethernet0/1 : address is 0024.972b.e021, irq 9
2: Ext: Ethernet0/2 : address is 0024.972b.e022, irq 9
3: Ext: Ethernet0/3 : address is 0024.972b.e023, irq 9
4: Ext: Management0/0 : address is 0024.972b.e01f, irq 11
5: Int: Not used : irq 11
6: Int: Not used : irq 5
Licensed features for this platform:
Maximum Physical Interfaces : Unlimited perpetual
Maximum VLANs : 100 perpetual
Inside Hosts : Unlimited perpetual
Failover : Active/Active perpetual
VPN-DES : Enabled perpetual
VPN-3DES-AES : Enabled perpetual
Security Contexts : 2 perpetual
GTP/GPRS : Disabled perpetual
AnyConnect Premium Peers : 2 perpetual
AnyConnect Essentials : 250 perpetual
Other VPN Peers : 250 perpetual
Total VPN Peers : 250 perpetual
Shared License : Disabled perpetual
AnyConnect for Mobile : Disabled perpetual
AnyConnect for Cisco VPN Phone : Disabled perpetual
Advanced Endpoint Assessment : Disabled perpetual
UC Phone Proxy Sessions : 2 perpetual
Total UC Proxy Sessions : 2 perpetual
Botnet Traffic Filter : Disabled perpetual
Intercompany Media Engine : Disabled perpetual
This platform has an ASA 5510 Security Plus license.
Failover cluster licensed features for this platform:
Maximum Physical Interfaces : Unlimited perpetual
Maximum VLANs : 100 perpetual
Inside Hosts : Unlimited perpetual
Failover : Active/Active perpetual
VPN-DES : Enabled perpetual
VPN-3DES-AES : Enabled perpetual
Security Contexts : 4 perpetual
GTP/GPRS : Disabled perpetual
AnyConnect Premium Peers : 4 perpetual
AnyConnect Essentials : 250 perpetual
Other VPN Peers : 250 perpetual
Total VPN Peers : 250 perpetual
Shared License : Disabled perpetual
AnyConnect for Mobile : Disabled perpetual
AnyConnect for Cisco VPN Phone : Disabled perpetual
Advanced Endpoint Assessment : Disabled perpetual
UC Phone Proxy Sessions : 4 perpetual
Total UC Proxy Sessions : 4 perpetual
Botnet Traffic Filter : Disabled perpetual
Intercompany Media Engine : Disabled perpetual
This platform has an ASA 5510 Security Plus license.
Serial Number: ABC12345678
Running Permanent Activation Key: eieioandapartridgeinapeartree
Configuration register is 0x1
Configuration last modified by me at 15:03:07.132 CDT Mon Sep 15 2014

If there was a "smack-self-on-forehead" icon here I'd use it now.
Of course, totally logical - if you disconnect a monitored connection on the standby it's not about to take over as primary because it's had a failure and can't do the job, forcing the primary or active to remain that way. There's the key that would allow all other changes.
Since the settings or config lines are in place already, then if I'm correct it's a matter of then just modifying what's there, and of course removing the name of the Management interface (no nameif) and making sure it's not shut down (no shutdown), etc.
You are a handy person to have around. Thanks.
By the way, *thanks to prior answers received here* and reading responses to others who had questions I can say I've set a record for this agency and done what no one else had been able to do - I've taken a troublesome LAN-to-LAN connection and made it trouble-free with a solid connection that is just 7.5 hours away from being up 90 days with no interruption, no collapse of any SA and improved performance. I have 2 others out of our 34 that aren't too far behind that. The boss has recognized this after seeing his monthly up-time reports.
Once I get this done failover change made I will be setting up a "DMZ" of sorts and trying out my hand at telling the 5510s to forward specific traffic aimed at a specific public IP address to a specific server. (But that's another topic............)

Exchange 2010 - Moving mailbox database from exchange 2010 server to another exchange 2010 server

Hi,
I have a current existing exchange server running on 2008 R2. apparently the partition that holds the mailbox database is getting full and i need to move some user mailboxes to another environment ( exchange 2010 running on 2008 R2). i transferred some users
successfully to the new location, but am not able to transfer the rest. I am getting the errors:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
Erastus XXXXX
Failed
Error:
The queue in 'MBX2010_STAFF' database already contains a move request for 'Erastus XXXXX', while AD reports the mailbox as not being moved. It is possible that someone created this move request recently, while targeting a different domain controller, and AD
replication did not yet occur. You can examine this move request by running 'Get-MoveRequestStatistics -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5 -IncludeReport | fl'. If you believe this to be an abandoned move request,
you can remove it by running 'Remove-MoveRequest -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5'.
Exchange Management Shell command attempted:
'xxxxxxxx.co.ke/Training Department/XXXXXXX/XXXXXXX/Erastus XXXXX' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
Elapsed Time: 00:00:00
AND
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01
George XXXXX
Failed
Error:
Service 'net.tcp://win-u5bjh2oamaa.xxxxxxxxx.co.ke/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=207]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
    Lid: 32881   StoreEc: 0x80070005
    Lid: 50035
    Lid: 64625   StoreEc: 0x80070005
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 56503
    Lid: 12716   StoreEc: 0x80070005
    Lid: 20794
    Lid: 28474   StoreEc: 0x80070005
    Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
    Lid: 1750    ---- Remote Context End ----
    Lid: 23354   StoreEc: 0x80070005
    Lid: 25913
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 26297
    Lid: 16585   StoreEc: 0x80070005
    Lid: 32441
    Lid: 1706    StoreEc: 0x80070005
    Lid: 24761
    Lid: 20665   StoreEc: 0x80070005
    Lid: 25785
    Lid: 29881   StoreEc: 0x80070005
Exception details: MapiExceptionNoAccess (80070005): MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=207]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
    Lid: 32881   StoreEc: 0x80070005
    Lid: 50035
    Lid: 64625   StoreEc: 0x80070005
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 56503
    Lid: 12716   StoreEc: 0x80070005
    Lid: 20794
    Lid: 28474   StoreEc: 0x80070005
    Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
    Lid: 1750    ---- Remote Context End ----
    Lid: 23354   StoreEc: 0x80070005
    Lid: 25913
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 26297
    Lid: 16585   StoreEc: 0x80070005
    Lid: 32441
    Lid: 1706    StoreEc: 0x80070005
    Lid: 24761
    Lid: 20665   StoreEc: 0x80070005
    Lid: 25785
    Lid: 29881   StoreEc: 0x80070005
Exchange Management Shell command attempted:
'xxxxxxxxxx.co.ke/Training Department/xxxxxx/xxxxxxx/George xxxxxxx' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
Elapsed Time: 00:00:01
I have all the proper rights.
YOUR ASSISTANCE WILL BE HIGHLY APPRECIATED. THANX :)

0x80070005 is pretty standard access denied entries. I would start digging into ACLs on a handful
of mailboxes.
Is there another Admin that can give it a shot to test their permissions vs yours?
- If you find my post to be helpful, or the answer, please mark it appropriately. Thank you.
Chris Ream

Exchange 2010 Decommisioning a DAG member from a 3 node Dag

Hi Guys,
What the safest way to remove one server from a 3 Node Dag.
Currently I am planning the following steps:-
Remove Exchange server MAIL03 from DAG
1.Start up Exchange Management Console
2.Go to Organization Configuration > Mailbox > Database Management;
3.if mail boxes are mounted on MAIL03, Select the database where ” Mounted on Server” reads the MAIL03;
3.1.Select Move Active Mailbox Database;
3.2.Select the Mailbox server i.e. MAIL01\MAIL02 to host the mailbox database copy and select Move;
5.When the move has finished, select the database copy hosted on the MAIL03 in the lower pane. There, select Remove.
6.Remove the MAIL03 server from the DAG. Select tab Database Availability Groups;
7.Select the DAG the MAL03 server is a member of and select Manage Database Availability Group Membership;
8.Select the server and click the red cross to remove it from the list. Click Manage to proceed with the actual removal;
9.When finished the mailbox server is no longer member of the DAG.
10.Rebalance Mailbox Databases in DAG.
What do you guys recommend?
Also after the removal of the DAG node, what the best way to reduce the Passive Database/Transaction logs? our current setup is as follows:-
I want to remove the drives L,M,N,O
Thanks
Jitinder

Hello,
Based on your description.
If you want to remove drives only from that server and leave databases working on the rest of nodes:
1. Remove database copy on that server.
2. Remove drives.
It is not required to move mailboxes from these databases. In this scenario you will not be able to re-add copy of these databases because all nodes need to have the same drive
letters.
If you want to remove L, M, N, O from all servers:
1. Move mailboxes from these databases.
2. Remove them (copies and empty dabatabes).
3. Remove drives.
There is no need to remove server from DAG if you just want to remove database copy from one node.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Rename existing Exchange 2010 database in DAG

Hello,
I want to rename one existing database on our exchange 2010 server. This database is in DAG and hosting around 1000 users. So not possible to create a new mailbox database and move.
How can I rename the database?
After renaming it, what will happen to the Copy database on another server as it is in DAG.
Thanks,
Mihir

Appreciate your response, Andy.
To clear my doubt,
If I am ok to reseed the passive copy, then I can follow below steps, Correct?
--> Remove Passive copy
--> Remove Database files and Log files on this passive server manually
And
"1. Then will a New database with this new name be created?"
--> On Move database, I will mention same location, but just
rename .edb file. So a exact copy of new database with this new name will be created. Correct?
--> And then I can delete the old named .edb, Correct?
Thanks.

Remove inaccessible/inactive exchange 2010 server

I had a second exchange 2010 server with a DAG setup between the primary production exchange 2010 server and the secondary one which was at our DR site. I did a DR test and ended up having to break the DAG and mount the DB manually for the DR test. AS a
result this second exchange server has been switched off and I have removed the DAG from the production side and all is ok with that. I am planning to move to a netapp exchange replication solution instead of dag for DR. As the DAG does not work well as a
DR solution.
The only problem that remains is that I still have the old server listed under servers and there is a public folder database that is still listed from the second server. Is there a way to remove this inasscible server from exchange without doing it through
ASDIedit? There is no way that i can turn this second server on again.

Your first option is to uninstall normally as commented by Ed.
If no way you can uninstall (in a documented way), then you can go with the final option of cleaning up from active directory. But take a backup of the active directory system state before doing this to be safe.
http://social.technet.microsoft.com/Forums/exchange/en-US/1c638bdd-67ba-44dd-996d-882be5fe5b09/remove-failed-exchange-2010-servers-that-are-no-longer-accessible?forum=exchange2010
http://windowsitpro.com/exchange-server/how-uninstall-stubborn-exchange-server
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

CatalogData folder too big on passive server in DAG

I have a two Exchange 2010 server DAG. One is active and the other is mounted but passive.
On at least two of the replicated and mounted databases on the passive server, the CatalogData folder is too big.
I noticed inside of them, they have old .ci and .dir files from last year.....really long ago and I need to get rid of them.
Can I delete them safely without affecting the DAG and/or replication?
What is the best way to do this on the passive server without affecting any mail flow or the DAG?

Simply stop the Exchange Indexing service on the server and delete the catalog folder and restart the indexing service. Or update-mailboxdatabasecopy (ServerCopy) -catalogonly
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

2010 server in Dag config. need to move logs

Similar Messages

Maybe you are looking for