Exchange Database Availability Group

Hi,Long time lurker here, i always find what i need on spice works whenever looking for help, however i couldn't find a clear answer to my question this time, hence my first post!
I am currently going through planning a secondary exchange server to be paired with our current exchange in a DAG fail over, Ive been reading through some guides and online help it doesn't seem too difficult.However, the guide i was looking at (http://exchangeserverpro.com/installing-an-exchange-server-2013-database-availability-group/) said you need to move the mailbox database your going to replicate from the default path, now as Ive only been at this company six months i didn't set up the exchange and it currently sits at the default path, and the company works around the clock so finding a reasonable time for downing exchange for this will be difficult.So...
This topic first appeared in the Spiceworks Community

Similar Messages

Database Availability Group Missing on 2 Exchange Servers

I have a an existing Exchange 2007 setup and installed 2 Exchange 2013 servers that have the Mailbox and CAS role. When I go to the ECP menu and click on databases there is no option available to create the DAG.

I Don't think that the Exchange 2013 installation is successful. If it successful then it might have been a problem with RBAC Roles which were not delegated properly to the account you are using to logon to ECP.
Try below and check if you are able to create DAG.
1. Create a New User and make it a member of Organization Management, Enterprise admins, Domain Admins, Schema Admins,
Built-in Administrators, Group policy Creator Owners and run the command below on the powershell: Set-User NewUser -RemotePowershellEnabled:$True
2. Logoff and Login Back using the Newly create account and check if you are able to see the option to Create DAG.
IF you are not able to then Open Windows Powershell as administrator and run the commands below
Add-Pssnapin *Setup
Install-CannedRBACRoleAssignments -InvocationMode Install
Install-CannedRBACRoles
Install-CannedRBACRoleAssignmentsRAP
Install-CannedAddressLists
Lastly, i would also ask you to get the output of the command below:
Get-ManagementRoleAssignment -Role "Database Availability Groups" -RoleAssignee OriginalUserWhoDontHaveCreateDagOptiononECP
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
Information is provided is "AS IS" and confers NO Rights!!

SQL 2012 Database Availability Group - Force Automatic Failover

Hi All,
I'd appreciate some help in understanding the following scenario in my test environment.
I have created a DAG with 2 replica servers (both of which are HyperV VM's running W2012 Std).
From a client PC in my test lab, I can connect to the virtual listener of my DAG and confirm via the "select @@servername" command that I am connecting to the primary replica server.
Using the Failover Wizard, I can easily move to primary instance between my 2 nodes and the command above confirms that the primary replica server has changed. So far so good.
What I wanted to test, was what would happen to my DAG in the event of a complete loss of power to the server that was acting as the primary replica server. At first, I thought I would stop the SQL Server service on the primary server, but this did not result
in my DAG failing over to the secondary replica. I have found out that the only way I can do this is by effectively shutting down the primary server in a controlled manner.
Is there any reason why either stopping the SQL Server service on the primary replica, or indeed forcing a power off of the primary replica does not result in the DAG failing over to the secondary replica?
Thanks,
Bob

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

SQL server 2012 - Database Availability Group

We have 2 new Servers ready to be deployed as Database Servers for Sharepoint 2013.
both server have 1TB RAID 5 Hard Disk Space.
We don't have any kind of Shared Storage/SAN etc & we cannot afford to buy this.
I have Configured Windows Server Fail-over Cluster with File Share Quorum.
May i Configure the SQL Database 2012 on Each Server on local disk and then make High Availability Groups?

As well as the youtube video that Edwin has posted for you have a read of my article on SimpleTalk.com.
https://www.simple-talk.com/sql/database-administration/sql-server-2012-alwayson/
This takes you through the step by step process.
HTH
Warwick Rudd (MCM - SQL 2008 | MCT)
(SQL Masters Consulting |
My SQL Server Blog | Twitter)

Cisco 5 with Exchange 2010 and Database Availability Groups

Hi,
Unity 5 was installed a long time. Recently installed with the latest ES88 to the system. The fact is we have Exchange 2007 (clustered) mailbox server in the network environment, and introduced the Exchange 2010 (with DAG activated).
So far we didn't do any "re-partnering" from the Exchange 2007 to Exchange 2010. The end users are working fine by leaving voice message and can retreive their voice without too much issue, no matter where the End Users account are located, Exchange 2007 or Exchange 2010.
But lately, there was some actions taken in the Exchange environment. Some Exchange 2010 mailstore databases in one of the Exchange 2010 server, with DAG has been activated.
In this case, we are now unable to leave any voice messages to the end usrs. All the voice messages are now being held in C:\CommServer\UnityMTA.
Want to ask, does Unity 5 and Exchange 2010 compatible with DAG? Also, is that my problem is caused by re-partnering server not taken place? If yes, which Exchange 2010 mailbox database server I should point to? Reason is, there will have 3 physical servers, and with several DB mailstore, if I select one of the physical server, and one of the D mailstore, will this be affected when the DAG is activated?
Thanks
Timothy

Hi Yancy,
If you're referring to integrating Microsoft Exchange 2010 with Cisco Unified Communications Manager (CUCM) 5.x for voicemail purposes, via a SIP Trunk, then you could certainly have a go at it (a Media Termination Point would be required and the codec would be G.711). However, I'm not aware of anyone having properly tested it with CUCM 5.x; given that it's not having software maintenance releases written for it anymore. CUCM 5.0 stopped having software maintenance releases written for it in June 2009, and CUCM 5.1 in February this year.
The following Tech Tip is likely to assist:
https://supportforums.cisco.com/docs/DOC-12544
Kind regards,
Craig

Database Availability Group - Network Problem

Hi All i have a question, hope that you can help me.
My domain have 2 site. Each site have 3 mailbox server.
This morning at 1 AM, mailbox database active move from HQ site to DR site because of network issue.
But at 3 AM, mailbox database active move again from DR site to HQ site automatically.
This is the first time i realize this act.
Can somebody explain to me what happen to my environment?
Why system can move mailbox database active from HQ site to DR site and otherwise?
Is it related with network issue?
Thanks for your help!
Best Regards,
Henry Stefanus

Hi Henry Stefanus,
I am not familiar with Exchange server and can not advice you how to check the Exchange log, but based on my experience in some situation there have instability of connection
between Exchange and Active Directory system may caused the failover ether, you can check your confirm your network work properly.
At the cluster side you can use the following method to get the cluster log then found the failover reason.
Please run: Get-ClusterLog –Destination C:\temp on Powershell in one Exchange 2013 server in the DAG. By default, it will collect the cluster logs on all DAG members.
If you need more information, please refer to following article:
http://technet.microsoft.com/en-us/library/hh847315.aspx
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Availability group Automatic failover

Hi
setup a simple 2 node AG, sync. (SQL 2014 enterprise on windows 2012R2 standard)
if I set it as manual failover everything works as expected. however when I switch to automatic failover and stop SQL service on the primary node the AG resource in cluster does offline and doesn't failover to secondary node.
both nodes are available to the cluster resourse.
would appreciate your feedback as to what might be the reason
Regards
Shaunt

Hi,
I would verify if Database Availability Group means AlwaysOn Availability Group.
How did you set the FailureConditionLevel?
Whether the diagnostic data and health information returned by sp_server_diagnostics warrants an automatic failover depends on the failure-condition level of the availability group. The failure-condition level specifies what failure conditions
trigger an automatic failover. There are five failure-condition levels, which range from the least restrictive (level one) to the most restrictive (level five). For details about failure-conditions level, see:
http://msdn.microsoft.com/en-us/library/hh710061.aspx#FClevel
There are two useful articles may be helpful:
SQL 2012 AlwaysOn Availability groups Automatic Failover doesn’t occur or does it – A look at the logs
http://blogs.msdn.com/b/sql_pfe_blog/archive/2013/04/08/sql-2012-alwayson-availability-groups-automatic-failover-doesn-t-occur-or-does-it-a-look-at-the-logs.aspx
SQL Server 2012 AlwaysOn – Part 7 – Details behind an AlwaysOn Availability Group
http://blogs.msdn.com/b/saponsqlserver/archive/2012/04/24/sql-server-2012-alwayson-part-7-details-behind-an-alwayson-availability-group.aspx
Thanks.
Tracy Cai
TechNet Community Support
Hi,
Thanks for the reply.
It's an AlwaysOn Availability Group.
In my test lab, I have changed the quorum configuration to a file share witness and that has allowed an automatic failover when I turn the primary replica server off (rather than power it off).
I'll take a look at the links you provided.
Regards,
Bob

How can you change data on a SQL 2012 application database that uses availability groups from BizTalk server?

If you use the WCF-SQL adapter it is recommend that you set UseAmbientTransaction to true if you are changing data. I think this requires MSDTC to be enabled on the SQL server that you are changing the data on. (http://msdn.microsoft.com/en-us/library/dd787981.aspx)
I think that Availability groups does not support MSDTC. (http://msdn.microsoft.com/en-us/library/ms366279.aspx).
How can you change data on a SQL 2012 application database that uses availability groups from BizTalk server?

Hi,
Yes, Availability groups doesn't support MSDTC. Please refer to the similar discusison which maybe helpfull:
http://dba.stackexchange.com/questions/47108/alwayson-ag-dtc-with-failover
http://stackoverflow.com/questions/17179221/msdtc-in-always-on-availability-groups

Maintenance plan for SQL Server 2012 Database in AlwaysOn Availability Group

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Thank you very much for your help!
Jake

Hi all,
I need assistance creating a maintenance plan that will backup a databases logs in order to prevent them from filling up the drive they are located on. I have looked at some blogs but they do not specifically show how this is done.
My database is in an AlwaysOn Availability Group.
Regular maintenance plan would work. Only thing to remember is that when you create log backup plan, there is a checkbox which says whether it should honor backup preference or not.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle

Add users to databases in Availability Groups

Hello,
I created a database.
On instance level I selected Security | Logins and added some users.
I granted the users a number of roles on the database I created.
I added the database to an Availability group. Now two replicas of the database are on two servers.
When I look on the server that is running the secondary replica the users have not been added to the users on instance level. Is that going to work fine after a failover?
Should I add the users to the Instance(s) of other cluster members before I restore the database? That would make sense.
I cannot find any documents that tell me about creating users in databases that have been added to an availability group.
Best regards,
Erik

Thanks for you answer.
I used sp_help_revlogin to script out the logins the applications and users need to connect to the database, including their SIDs, and executed it on the secondary replicas servers
so that it is available.
I have done that before I restored the database on the secondary replica servers.
I guess I have to run sp_help_revlogin every time I add a user on the primary server.
Best regards,
Erik
If it is a windows login, it will have the same SID across the domain so no need to run sp_help_rev_login, you can directly create the login in the secondary and the mapping is taken care itself with the database user. If you are creating SQL Logins
you need to script it out using sp_help_rev_login for the secondary server.
If you are willing to automate this activity, Please explore " ssis package to transfer logins" and try to customize it to your need and schedule it as a job.
http://technet.microsoft.com/en-us/library/ms137870.aspx
Thanks

Automatically add a Database to an Availability Group

Dears, I need to know if there any way to configure SQL always on to automatically add new Databases to an Availability Group.
Ayman Saleh

Hi can any one update the TSQL script here:
Requirements:
Every time the newly created or added databases should be full backed up once in the shared location with
automated script.
Newly created database should be added into always on group and should be added to available replica automatically
with the TSQL script

Move database while in AlwaysOn availability group

Hee Guys I have a question and I try to find answer on the internet but I could find it. I have a database that is in a Availability group. There is constantly data written in the database. I really want to move it to a new disk. I am working with a SQL
2012 enterprise edition. Is there a way to move the database on both servers without losing data?
I was thinking of de-attaching and attaching it but that is not allowed while in the availability group. When I take it out of the group and move it to the new disk on the secondary server, then I cannot put it back in an availability group because the path
is not the same. Can somebody tell me how to do this in the right way.
Any help is appreciated!

I did some testing. What I am missing in the script is to kill transactions and processes. On one database I got the following exception:
--MOVE FILES
xp_cmdshell 'move "F:\Database\DBName1*.*" M:\Database\' -- Change values
go
F:\Database\DBName1.ldf
The process cannot access the file because it is being used by another process.
0 file(s) moved.
NULL
On the another database I got something the same:
GO
ALTER DATABASE [DBName2] SET ONLINE -- Change values
GO
File activation failure. The physical file name "E:\Database\DBName2.ldf" may be incorrect.
The log cannot be rebuilt because there were open transactions/users when the database was shutdown, no checkpoint occurred to the database, or the database was read-only. This error could occur if the transaction log file was manually deleted or lost due to
a hardware or environment failure.
Msg 5181, Level 16, State 5, Line 2
Could not restart database "DBName2". Reverting to the previous status.
Msg 5069, Level 16, State 1, Line 2
ALTER DATABASE statement failed.
What is the best way to go around this? I tried to use EXEC sp_who2 and Kill but there are no processes for these database. I also looked in the resource monitor to see if there are files in used but this is also not the case.

How to install SSAS Cluster instance with Always On availability group(Standalone database instance) in same windows cluster servers

We have requirement like to Install the SSAS as Cluster instance where SQL Server Database engine was installed with Always On availability group.Please help me to how configure it
Currently we have following configuration in Current steup.
Node1 and Node2 are in windows cluster
Node1 has SQL Server Database engine Instance1 as Standalone
Node2 has SQL Server Database engine Instance2 as Standalone
Instance1 and Instance2 configured for Always On availability group with Listener.
Now we have to steup SSAS instance with High availibilty. I know we have only option is to install cluster SSAS instance.
Can some one provide information below.
1. How to steup Cluster SSAS instance in this servers.
2. Is this will have any dependancy on exisiting Listner name.
3. Is this affects the availiblity groups, if SSAS instance failed over to another node.
Thanks in Advance
Sriram

You will need to have SSAS installed as a clustered instance with shared storage. Refer to the whitepaper from this MSDN article
How To Cluster SQL Server Analysis Services
Availability Group is in it's own Role/Resource Group. When you create the clustered SSAS, it will create its own Role/Resource Group. This means that it will require its own virtual network name and virtual IP address and will not affect the existing Availability
Group. You can also have it on the existing Availability Group if you want to. However, you need to decide if you want SSAS to failover with the Availability Group or not. Your design choices will depend on that decision.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

SQL2012 SP2 CU1 Availability Group database not synchronizing after applying February Microsoft patches

Hi,
We are starting our monthly patching and have a situation with SQL2012 SP2 CU1 Availability Groups databases not synchronizing after patching the secondary replica. This seems a little like
http://support2.microsoft.com/kb/3033492/en-us which was for CU3 and CU4 builds. The dashboard on the Primary shows the secondary as not synchronizing. The errorlogs on both nodes show the connection
has recovered but the dashboard shows critical errors. This is running on Windows 2012.
Thanks
Chris

Lydia,
I am referring to MS15-009 to MS15-017 that came out on Tuesday. These are the only patches we have applied. On our two node Availability Group setup we had the patches applied to the secondary node and then it was restarted. It came up fine and SQL is running
as expected.
This is from the primary node errorlog:-
AlwaysOn Availability Groups connection with secondary database terminated for primary database 'XXX_DEVL' on the availability replica with Replica ID: {e6468c4d-9431-4052-88c0-07d3b3eb428c}. This is an informational message only. No user action is required.
A connection for availability group 'YYYYY50_AG' from availability replica 'YYYYY50AV' with id [0E53235A-0FBB-4E18-8C40-A0D72F30C36A] to 'YYYYY50BV' with id [E6468C4D-9431-4052-88C0-07D3B3EB428C] has been successfully established. This is an
informational message only. No user action is required.
AlwaysOn Availability Groups connection with secondary database established for primary database 'XXX_DEVL' on the availability replica with Replica ID: {e6468c4d-9431-4052-88c0-07d3b3eb428c}. This is an informational message only. No user action is required.
On the secondary node errorlog:-
Skipping the default startup of database 'XXX_DEVL' because the database belongs to an availability group (Group ID: 65541). The database will be started by the availability group. This is an informational message only. No user action is required.
The state of the local availability replica in availability group 'YYYYY50_AG' has changed from 'RESOLVING_NORMAL' to 'SECONDARY_NORMAL'. The replica state changed because of either a startup, a failover, a communication issue, or a cluster error. For more
information, see the availability group dashboard, SQL Server error log, Windows Server Failover Cluster management console or Windows Server Failover Cluster log.
AlwaysOn Availability Groups data movement for database 'XXX_DEVL' has been suspended for the following reason: "system" (Source ID 5; Source string: 'SUSPEND_FROM_RESTART'). To resume data movement on the database, you will need to resume the
database manually. For information about how to resume an availability database, see SQL Server Books Online.
Nonqualified transactions are being rolled back in database XXX_DEVL for an AlwaysOn Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required.
AlwaysOn Availability Groups connection with primary database terminated for secondary database 'XXX_DEVL' on the availability replica with Replica ID: {0e53235a-0fbb-4e18-8c40-a0d72f30c36a}. This is an informational message only. No user action is required.
Now I see the suspend message. Running the select on sys.dm_exec_requests there are NO DB_STARTUP ones on either node or blocking.
Next action is probably to have the patches removed from the secondary node and see if all is well and then try patch one by one to see which one causes the issue.
Chris

New-DPMRecoveryOption CopyToFolder for an Exchange database backup

I'm trying to restore an Exchange database from DPM 2010 into the file system using powershell. I'm able to perform this action in the DPM GUI simply by selecting the "Copy to a Network Folder" option. When I try this in powershell I
fail when creating the recovery option object. Here's what I'm trying:
$Pg = Get-DPMProtectionGroup –DPMServerName "DPM"
$Ds = Get-DPMDatasource -ProtectionGroup $Pg[0]
$RecoveryObject = Get-DPMRecoverypoint -Datasource $Ds[0] | Sort -Property RepresentedPointInTime -Descending | Select-Object -First 1
$RecoveryOption = New-DPMRecoveryOption -TargetServer "DPM" -RecoveryLocation CopyToFolder -RecoveryType Recover -TargetLocation "f:\test"
Restore-DPMRecoverableItem -RecoverableItem $RecoveryObject -RecoveryOption $RecoveryOption
I get the following error on the New-DPMRecoveryOption command:
New-DPMRecoveryOption : Parameter set cannot be resolved using the specified named parameters.
I've tried a few dozen permutations of the available options, but I continue to get the same error message. I'm not seeing much documentation to explain all these options. Any guidance is appreciated.

try this
EXAMPLE-1: Recovers the exchange data from tape to R:\ on the Exchange Server
=====================================================
Below are the DPM Power Shell commands as well as the results of the commands when executed.
PS C:\Program Files\Microsoft DPM\DPM\bin> $pg = Get-ProtectionGroup -DPMServerName Dpmserver1
PS C:\Program Files\Microsoft DPM\DPM\bin> $pg
Name Protection method
SQL Short-term using disk | Long-term us...
File Servers Short-term using disk | Long-term us...
Mail Short-term using disk | Long-term us...
MOSS Short-term using disk | Long-term us...
PS C:\Program Files\Microsoft DPM\DPM\bin> $ds = Get-Datasource -ProtectionGroup $pg[2]
PS C:\Program Files\Microsoft DPM\DPM\bin> $ds
Computer Name Type
EXCHANGE1 First Storage Group Storage group
EXCHANGE1 Medium2 Storage group
EXCHANGE1 Large Storage group
EXCHANGE1 Medium Storage group
PS C:\Program Files\Microsoft DPM\DPM\bin> $rp = Get-Recoverypoint -Datasource $ds[0]
PS C:\Program Files\Microsoft DPM\DPM\bin> $rp
Name Backup Time Datasource Location
First Storage Group 18/09/2009 8:00:... First Storage Gr... Disk
First Storage Group 19/09/2009 12:00... First Storage Gr... Disk
First Storage Group 19/09/2009 4:00:... First Storage Gr... Disk
First Storage Group 19/09/2009 8:00:... First Storage Gr... Disk
First Storage Group 19/09/2009 12:00... First Storage Gr... Disk
First Storage Group 19/09/2009 4:00:... First Storage Gr... Disk
First Storage Group 01/07/2009 8:00:... First Storage Gr... Media
First Storage Group 01/08/2009 8:00:... First Storage Gr... Media
First Storage Group 22/08/2009 8:00:... First Storage Gr... Media
First Storage Group 29/08/2009 8:00:... First Storage Gr... Media
First Storage Group 01/09/2009 8:00:... First Storage Gr... Media
First Storage Group 19/09/2009 8:00:... First Storage Gr... Media
PS C:\Program Files\Microsoft DPM\DPM\bin> $ri = Get-RecoverableItem -RecoverableItem $rp[10] -BrowseType Child
PS C:\Program Files\Microsoft DPM\DPM\bin> $ri
Name Backup Time Datasource Location
Mailbox Database 01/09/2009 8:00:... First Storage Gr... Media
Mailbox Database2 01/09/2009 8:00:... First Storage Gr... Media
PS C:\Program Files\Microsoft DPM\DPM\bin> $lib = Get-DPMLibrary -DPMServerName Dpmserver1
Name Drives Slots I/E ports Protection groups
Stand-alone Drive: F... 1 0 0
Library: Firestreame... 5 200 0 Mail
PS C:\Program Files\Microsoft DPM\DPM\bin> $rop = New-RecoveryOption -Exchange -ExchangeOperationType NeedCleanShutdown -RecoveryType Restore -StorageGroupName "First Storage Group" -TargetLocation "R:\" -TargetServer "exchange1.nwtraders.com" -RecoveryLocation CopyToFolder -dpmlibrary $lib[1]
PS C:\Program Files\Microsoft DPM\DPM\bin> Recover-RecoverableItem -RecoverableItem $ri[0] -RecoveryOption $rop
JobCategory Status HasCompleted
RestoreAsFilesFromArchive InProgress False
http://social.technet.microsoft.com/Forums/en-US/6833631b-de65-4568-afb8-e2b4f1522fd8/error-id31127-when-trying-to-restore-exchange-2007-mailbox-using-dpm-2007-sp1?forum=dpmexchbackup
Have a nice day !!!

Exchange Database Availability Group

Similar Messages

Maybe you are looking for