Database changes during pool pairing in lync 2013

Hi,
I am planning for pool pairing.Can anyone tell what all database get copied on bacup pool.Do we need extra storage for pairing.
will all previous lcscdr & lcslog get copied to backup pool?

According to my understanding, the database Lcscdr and Lcslog are not copied to backup pool.
The Backup Service is a data replication mechanism introduced in Lync Server 2013 that transfers user data and conference content between two paired Front End pools continuously across two data centers for disaster recovery purposes.
Lisa Zheng
TechNet Community Support

Similar Messages

Error during the migration of Lync 2013 onpremise user to Office 365 Lync

Hi,
I am trying to migrate a Lync 2013 onpremise user to Office 365 Lync in a Hybrid environment.
I am connecting to the Lync server from my machine with the following commands
$lyncOptions = New-PSSessionOption -SkipRevocationCheck -SkipCACheck -SkipCNCheck
$lync = New-PSSession -ConnectionUri https://lyncserver/ocspowershell -SessionOption $lyncOptions -Authentication NegotiateWithImplicitCredential
Import-PSSession $lync
In the next step I am trying to migrate the user to the Office 365 Lync:
Move-CsUser -Identity "username" -Target 'sipfed.online.lync.com' -HostedMigrationOverrideUrl 'https://admin1e.online.lync.com/HostedMigration/hostedmigrationservice.svc'
After that I get a warning message due to to migration to a previous version which I accept.
WARNING: Moving a user from the current version to an earlier version (or to a service version) can cause data loss.
Confirm
Move-CsUser
[Y] Yes [A] Yes to All [N] No [L] No to All [?] Help (default is "Y"): y
Then I am getting the following error message:
Can not load Live Id module. Make sure correct version of Live Id Sign-in assistant is installed.
    + CategoryInfo          : NotSpecified: (:) [Move-CsUser], CommonAuthException
    + FullyQualifiedErrorId : Microsoft.Rtc.Admin.Authentication.CommonAuthException,Microsoft.Rtc.Management.AD.Cmdle
   ts.MoveOcsUserCmdlet
    + PSComputerName        : lyncserver
Tried to Google it but found nothing.
As far as I can see it is complaining about the Live ID Sign-in assistant, which is installed (the 64bit version) on my computer but not on the remote server. Does it need to be installed on the server as well?
Thanks for the answers in advance.
Regards,
Akos
Akos_DB

This error related to reporting services, you need to verify that reporting services is installed on these instances.
Secondly, you didn't need to create this instance manually then setup monitoring role. delete this instance from shared storage and try again to setup rule using different instance name and it will create automatic on shared storage.
You can also refer below link
http://windowspbx.blogspot.com/2012/07/aaa-donotpost-install-lync-standard.html
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

Lync 2013 Edge server compatibility with Lyn 2010 Front end Pool

Hi All,
Technet article (http://technet.microsoft.com/en-us/library/jj688121.aspx) says the following:
If your legacy Lync Server 2010 Edge Server is configured to use the same FQDN for the Access Edge service, Web Conferencing Edge service, and the A/V Edge service, the procedures in this section are not supported. If the
legacy Edge services are configured to use the same FQDN, you must first migrate all your users from Lync Server 2010 to Lync Server 2013, then decommission the Lync Server 2010 Edge Server before enabling federation on the Lync Server 2013 Edge Server.
Can you tell me why it is you have to change the External Lync Web services URL during a migration to Lync 2013 from Lync 2010. What purpose does this serve?
Also can you clarify this and explain why this is required, why would you have to migrate all of your users, would a Lync 2013 Edge not talk to a Lync 2010 front-end?
Any help would be much appreciated. MANY THANKS.

Thank you very much for all your inputs.
We still have few questions:
Questions:
Can you tell me if Lync 2010 users will be able to login using mobility if we repoint the reverse proxy (TMG) web services publishing rule to the Lync 2013 server? Remember both systems Lync 2010 and 2013 are using the same web
services URL so they will both end up at the Lync 2013 server. Alternatively if not we will migrate all users to 2013, this is not a problem
In addition to this I cannot find anything that states how Exchange UM will operate when you are running from a backup pool and the exchange UM contacts are not available because they are homed on the server that is down. This
configuration is 2 x standard edition servers pool paired. How can we make sure Exchange voice mail works during a pool failover?
Call Park is not clear to me I read the following:
Lync Server 2013 provides new disaster recovery mechanisms in the form of failover and failback processes. These failover and failback processes support recovery of Call Park functionality by allowing
users who are homed in the primary pool to leverage the Call Park application of the backup pool when an outage occurs in the primary pool. Support for disaster recovery of the Call Park application is enabled as part of the configuration and deployment of
paired Front End pools.
Is this saying we need to deploy Call Park in the DR pool and use a different range of orbit numbers, or can we use the same range in the DR pool?
Further, I can see that Common Area Phones will be fine as they will log into the DR pool automatically. Response Groups need to be exported and imported to the DR pool. Incidentally these did not migrate well at all and have
caused us a big headache!
Any inputs will be greatly appreciated. Thanks again for all of your time.

Lync 2013 Mirror Database fails to install - Error: DsRoleGetPrimaryDomainInformation failed with error "6BA".

Database primary installs just fine for Lync 2013 - however fails instantly when trying to install mirror DB to mirror SQL Server. The account has dull domain admin, Enterprise admins, and schema admins. Full access to the share as well. I
get the following error:
InstallMirrorDatabaseCmdlet.StartMirroring
4/7/2014 10:38:56 AM
Failed
└
Error: DsRoleGetPrimaryDomainInformation failed with error "6BA".
▼ Details
└ Type: CannotGetDomainInfoException
└ ► Stack Trace
└
at Microsoft.Rtc.Management.ADConnect.NativeHelpers.NativeHelper.GetPrimaryDomainInformation(String server)
at Microsoft.Rtc.Management.Deployment.MirrorUtils.GetSqlServerAccount(String server, String instanceName)
at Microsoft.Rtc.Management.Deployment.TopologyParser.PopulateDatabasesForSqlInstance(ISqlInstance sqlInstance)
at Microsoft.Rtc.Management.Deployment.TopologyParser.FindDatabasesForMachine(IMachine machine)
at Microsoft.Rtc.Management.Deployment.TopologyParser.FindDatabasesForFqdn()
at Microsoft.Rtc.Management.Deployment.TopologyParser.GetDbListToMirror()
at Microsoft.Rtc.Management.Deployment.TopologyParser.get_DbInfoList()
at Microsoft.Rtc.Management.Deployment.InstallMirrorDatabaseCmdlet.StartMirroring()
at Microsoft.Rtc.Management.Internal.Utilities.LogWriter.InvokeAndLog(Action action)
4/7/2014 10:38:58 AM
Error
└
Error: An error occurred: "Microsoft.Rtc.Management.ADConnect.CannotGetDomainInfoException" "DsRoleGetPrimaryDomainInformation failed with error "6BA"."

The issue could be a typo in the SQL server name or that the SQL server isn't allowing remote connections. If you run the Install-csmirrordatabase command from powershell you should see more details about the error.
Take a look at Doug Deitterick's blog: http://blogs.technet.com/b/dodeitte/archive/2013/03/05/issue-configuring-sql-mirroring-for-lync-server-2013-when-sql-witness-is-defined-but-not-available.aspx
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Change Lync 2013 Edge Server Natted public ip addresses

we changed public ip addresses for Lync 2013 edge. I changed only a/v edge service NAT-Enabled public ipv4 address to the new public ip address .
published the topology
run
Invoke-CsManagementStoreReplication command
restarted edge server.
what else to do to solve it ?
Error:
The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server sip.*****.com on port 5061.
The Microsoft Connectivity Analyzer wasn't able to obtain the remote SSL certificate.
Additional Details
The certificate couldn't be validated because SSL negotiation wasn't successful. This could have occurred as a result of a network error or because of a problem with the certificate installation.

Hi,
Please re-run Step 2-Setup or Remove Lync Server Components after changing IP in topology.
Kent Huang
TechNet Community Support

How CMS replication works in Lync 2013.

Hi can you anyone tell how CMS replication works in LYnc 2013 2 FE servers in pool scenario and Lync 2013 3 FE servers in pool scenario.
Please give me the useful article if you have related to this topic?
Thanks
Thanks

all good articles which you can find in internet in shared above. read those and you would get a fair idea.
my 2 cents - in short summary.
these is no difference in CMS replication in case of 2 FE or 3 FE or max of FE in a pool of lync server. the CMS replication mechanism is the same.
CMS - it's a repository to store management data ie Topology, configurations and policies inform of xml documents in the data called XDS (Xml Data Store) in SQL.
CMS is implemented using three Windows services:
1. Lync server File Transfer Afent ( FTA )
2. Lync server Master Replicator Agent ( MRA )
3. Lync server Replica Replicator Agent ( RRA )
Workflow
1. MRA generates data packages in to-replica as needed
2. MRA has change notifications on from-replica to pickup status packages coming in from replica
3. FTA has change notifications on to-replica for all replicas on the Master to pickup data packages going out to the replicas
4. All replicas
\xds-replica\from-master">\\<replica>\xds-replica\from-master to pickup data packages coming in from master
Sreejith.PS CCNA, MCTS Lync

Lync 2013 problem with interaction in Hyper-V

Hello,
during the conference in Lync 2013 does
not work the guest interaction service,
which has been referred to the control
(display the
desktop). The
guest can move the
cursor, but
can't click or
write in Hyper-V virtual
machine. In
a virtual machine running Windows Server 2012R2. Enhanced VM Interaction is
on.
What to do to give away full
control for the guest?

I may be confused, but it looks like you're trying to control a server VM with this capability. Do the actions require elevated or administrator access? If so, by security design this won't work.
"It is worthwhile mentioning that people who you gave control to in a desktop sharing session will not be able to interact with elevated prompts."
The article below mentions this, and suggests running as Lync as administrator which we've not had great success with.
http://blogs.technet.com/b/lync/archive/2012/11/02/presenting-your-screen-in-lync-2013.aspx
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Installing Lync 2013 and remove 2010 client via SCCM

We have Windows 7 x64 PC’s running Lync 2010 64-Bit client.
What I need to do is install the Lync 2013 32-Bit client and then uninstall the Lync 2010 64-Bit client.
Using the Office Customization Took, I am able to install the Lync 2013 client fine, however the 2010 client isn’t not removed.
Here is what I did:
-Have the standalone Lync 2013 installer.
I then copied the Lync 2010 64-bit install files into a new folder in the Lync 2013 source files.
This folder is c:\Lync2013\Lync2010
-Created MSP file using OCT set to never reboot.
-Under ‘Add installations and run programs’ option, I specified the Lync 2010 to be removed post install of Lync 2013.
The Command line: [post install] [INSTALLLOCATION]\Lync2010\LyncSetup.exe /silent /uninstall
-Loaded this into SCCM and set to run at a logon event.
As stated above, Lync 2010 is not removed.
A few questions:
Is this even possible using the OCT?
In the OCT, is it a problem trying to mix two different installers?
One 32-Bit, the other 64-Bit?
If not, then is the command line correct for the Lync 2010 uninstall?
If no for # 3, how do I make SCCM use the correct path to the package where the Lync 2010 install files are?
In the OCT, do I need to have the Lync 2010 command line as:
\%WINDIR%\SystemWOW64\CCM\Cache\nameofpackage
Please help me alleviate some frustration with any ideas for the above.

You can use the command msiexec.exe /uninstall “C:\Program Files (x86)\OCSetup\Lync.msi” to uninstall Lync 2010.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
I'll try this, thanks! For the post uninstall of Lync 2010 using the OCT, should I also ad /quiet switch or /no restart to suppress dialog boxes and not restart the PC when the removal is complete? Or will the OCT prevent it from being restarted
and 'suppress modals' as I set this during the install of Lync 2013.

CMS Migration - Lync 2010 to Lync 2013 & Pool Pairing

Hi all,
Question regarding CMS installation when migrating away from Lync 2010.
Here's a brief overview of topology
- Lync 2010 Pool in Data Centre 1
- Lync 2013 Pool #1 in Data Centre 1
- Lync 2013 Pool #2 in Data Centre 2
- Lync 2013 Pools are paired
Consider the following
- CMS located on SQL Backend server for Lync 2010 Pool
- CMS database installed on SQL Back end for Lync 2013 Pool #1. CMS is moved to this location
Now for correct pool pairing and failover capabilities I would assume that
- CMS database needs to also be installed on SQL back end for Lync 2013 Pool #2
Once this is done then Lync 2013 Pool #2 Front Ends should replicate back into the CMS stored on the back end SQL database for pool #2? Nothing else would need to be done? As soon as it's installed its now a backup?
If I'm reading into this correctly the following from TechNet is basically telling me to do this?
When you establish a pool pairing that includes the pool hosting the Central
Management store, a backup Central Management store database is set up in the
backup pool, and Central Management store services are installed in both pools.
At any point in time, one of the two Central Management store databases is the
active master, and the other is a standby. The content is replicated by the
Backup Service from the active master to the standby.
Thanks,
paul.

Correct, when you enable pool pairing on Pool A - if it's a CMS server - it will prompt you to create the CMS database on Pool B. If you move CMS into a pool that is already pool paired, my experience is that CMS doesn't get created on Pool B because the
creation only happens during the pool pairing setup. Thanks -Richard
Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

Lync 2013 Enterprise Edition Pool Pairing

Hello
I am trying to understand Lync pool pairing, my question is:
I have two geographically dispersed locations, Site1 and Site2. If I were to do pool pairing, would I create two sites in the topology builder with a separate FE pool for each site or do you create one site with more than one FE pool (or can you only put
one FE pool per site?)
Another part of the question, if I have two sites would they both be active/active where user's would register to both locations and each site would act as a failover for the other, or would all users register to Site1 and if Site1 were to go down, they
would re-register to Site2?
Thanks,

Hi,
Agree with Michael, what’s more, when the failed pool is once more up and running, administrators can then run the Invoke-CsPoolFailBack cmdlet in order to "fail back" users of that pool. If a user is currently logged on to the backup pool then he or she
will be redirected back to their home pool after service has been restored.
You can refer to the link of “Managing Lync Server 2013 Disaster Recovery, High Availability, and Backup Service”:
http://technet.microsoft.com/en-us/library/jj721939.aspx
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Lync 2013 - Number of FE servers in paired pools

Hi,
We have an Ent. Edition Lync 2013 pool with 4 FE servers, we would like to implement a second pool at a different location for disater recovery.
Does the DR pool which will be paired with production one need to have exactly the same number of FE servers or can it have less (i.e. 3) ?
Thanks for your help,
Luca

You can have 1, or 3, or whatever number, it just has to be Enterprise to match Enterprise, you can't use Standard Edition with Enterprise for example.
Per: http://technet.microsoft.com/en-us/library/jj204697.aspx
"Each pool in a pair should have the capacity to serve all users from both pools in the event of a disaster."
That's not a statement on the number of servers, just the capacity to do what you need to do if you fail. It's sort of an obvious statement that speaks to load sharing among pools. Don't max out two pools and expect to be able to fail over to
one and run at full capacity.
In a DR situation, you may not need full capacity, so the amount of resources you'll be giving it will be based upon your own internal best practices.
Edit: And finally, yes I've done exactly what you're asking, it's fine.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

Lync 2013 Error 31055 ,31059 LS Call Park Service, The database being used by Group Pickup is not the appropriate version and There was a problem communicating with the Group Pickup backend database.

Hello
I have Lync 2013 and 2010 , still i didn't finish my migration completely from 2010 to 2013 .this is coexistence environment that contains both Lync Server 2010 and Lync Server 2013 .
There was no error's in my lync 2013 front end and back end server's and every thing was fine, yesterday I installed windows updated AND CU for my lync 2013 front end and backend server's .
later on after restarting both the front end and the back end server's i start having hundred's of these error's related to "LS Call Park Service".
so any advice for these issue ? and what is the effect for these error .
below is the error I got .
The database being used by Group Pickup is not the appropriate version.
The database is not the correct version:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Expected... SchemaVersion: 1, SprocVersion: 1, UpgradeVersion: 2
Actual... SchemaVersion: 0, SprocVersion: 0, UpgradeVersion: 0
Cause: The database has not been upgraded.
Resolution:
Upgrade the database to CU1.
==============================================================
There was a problem communicating with the Group Pickup backend database.
There were problems accessing SQL server:
Connection: Data Source=HQ-LYNC2013-BE.aaaaaaaaaaaaaaaaaaaaaaaaaa\rtc;Initial Catalog=cpsdyn;Integrated Security=True
Message: The EXECUTE permission was denied on the object 'DbpGetVersionSchema', database 'cpsdyn', schema 'dbo'.
Error code: -2146232060
Error number: 229
Cause: This may be caused by connectivity issues with the backend database.
Resolution:
Check if SQL backend is running and accepts connections from Group Pickup.
=============================================================================
Kind Regards
MK

Hello
thanks Holger for u r replay .
due to the Microsoft article about the cu :
I run only :
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose
Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 and in which the Central Management Service is located on a Lync Server 2010 pool, do not run the
Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the
Install-CsDatabase -CentralManagementDatabase command to apply the changes.
here is what I get on my power shell after i run the command : "WARNING: Warning: Failed to execute batch --"
PS C:\Users\MK> Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn HQ-LYNC2013-BE.MyDomain -Verbose
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.xml".
VERBOSE: Install databases required by Lync Server role(s).
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
VERBOSE: Assigning "BackendStore:BlobStore:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ArchivingStore:ArchivingDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:MonitoringDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "MonitoringStore:QoEMetricsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:LogPath" to F:\CsData
VERBOSE: Assigning "BackendStore:BlobStore:DbPath" to F:\CsData
VERBOSE: Assigning "BackendStore:RtcSharedDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ABSStore:AbsDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsConfigDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:RgsDynDatabase:DbPath" to F:\CsData
VERBOSE: Assigning "ApplicationStore:CpsDynDatabase:DbPath" to F:\CsData
VERBOSE: Installing "BackendStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.BlobStore'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcxds.
Checking state for database rtcxds.
State of database rtcxds is DbState_RequiresMinorUpgrade.
Database rtcxds set to mode Restricted.
Dropping all procedures, functions and views from database rtcxds.
Executing RtcDb.sql...
Adding master role...
Setting owner for database rtcxds to sa.
Creating login MyDomain\RTCHSUniversalServices.
Creating user MyDomain\RTCHSUniversalServices.
Creating Schema MyDomain\RTCHSUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCHSUniversalServices to role ConsumerRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ConsumerRole.
Adding account MyDomain\RTCHSUniversalServices to role ReplicatorRole.
Adding account MyDomain\RTCHSUniversalServices to role PublisherRole.
Adding account MyDomain\RTCUniversalServerAdmins to role PublisherRole.
Setting database version: Schema Version 15, Sproc Version 13, Update Version 2.
Setting the database rtcxds to multi user mode.
Database rtcxds is set to multi user mode.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RtcSharedDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcshared.
Database created by script "RtcSharedDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-BackendStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_01].log"
VERBOSE: Installing "ABSStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.AbsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rtcab.
Checking state for database rtcab.
State of database rtcab is DbState_RequiresMinorUpgrade.
Database rtcab set to mode Restricted.
Dropping all procedures, functions and views from database rtcab.
Executing RtcAbTypes.sql...
WARNING: Warning: Failed to execute batch --
-- Copyright (c) Microsoft Corporation. All rights reserved.
exec sp_addrole N'ServerRole'.
Executing RtcAbDb.sql...
Setting owner for database rtcab to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 42, Update Version 3.
Setting the database rtcab to multi user mode.
Database rtcab is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ABSStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_20].log"
VERBOSE: Installing "ApplicationStore" on HQ-LYNC2013-BE.MyDomain\rtc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsConfigDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsconfig.
Database created by script "RgsConfigDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.RgsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database rgsdyn.
Database created by script "RgsDynDatabase" already exists and is current.
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.CpsDynDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\rtc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database cpsdyn.
Checking state for database cpsdyn.
State of database cpsdyn is DbState_RequiresMinorUpgrade.
Database cpsdyn set to mode Restricted.
Dropping all procedures, functions and views from database cpsdyn.
Executing CpsDyn.sql...
Setting owner for database cpsdyn to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Creating login MyDomain\RTCUniversalReadOnlyAdmins.
Creating user MyDomain\RTCUniversalReadOnlyAdmins.
Creating Schema MyDomain\RTCUniversalReadOnlyAdmins.
Creating login MyDomain\RTCUniversalServerAdmins.
Creating user MyDomain\RTCUniversalServerAdmins.
Creating Schema MyDomain\RTCUniversalServerAdmins.
Adding account MyDomain\RTCComponentUniversalServices to role ReadWriteRole.
Adding account MyDomain\RTCUniversalServerAdmins to role ReadWriteRole.
Adding account MyDomain\RTCUniversalReadOnlyAdmins to role ReadOnlyRole.
Setting database version: Schema Version 1, Sproc Version 1, Update Version 2.
Setting the database cpsdyn to multi user mode.
Database cpsdyn is set to multi user mode.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ApplicationStore-HQ-LYNC2013-BE.MyDomain_rtc-[2014_11_13][14_35_37].log"
VERBOSE: Installing "ArchivingStore" on HQ-LYNC2013-BE.MyDomain\arc, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.ArchivingDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\arc. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsLog.
Database created by script "ArchivingDatabase" already exists and is current.
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-ArchivingStore-HQ-LYNC2013-BE.MyDomain_arc-[2014_11_13][14_35_51].log"
VERBOSE: Installing "MonitoringStore" on HQ-LYNC2013-BE.MyDomain\mon, collocated: False
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.MonitoringDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
Checking state for database LcsCDR.
State of database LcsCDR is DbState_RequiresMinorUpgrade.
WARNING: The database LcsCDR being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\LcsCDR.mdf. Supplied path will be ignored.
WARNING: The database LcsCDR being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\LcsCDR.ldf. Supplied path will be ignored.
Database LcsCDR set to mode Restricted.
Dropping all procedures, functions and views from database LcsCDR.
Executing CdrDb.sql...
Setting owner for database LcsCDR to sa.
Creating login MyDomain\CSAdministrator.
Creating user MyDomain\CSAdministrator.
Creating Schema MyDomain\CSAdministrator.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Adding account MyDomain\RTCComponentUniversalServices to role ReportsReadOnlyRole.
Adding account MyDomain\CSAdministrator to role ReportsReadOnlyRole.
Setting database version: Schema Version 39, Sproc Version 82, Update Version 2.
Setting the database LcsCDR to multi user mode.
Database LcsCDR is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing CdrJobs.sql...
****Creating DbSetupInstance for 'Microsoft.Rtc.Common.Data.QoEMetricsDatabase'****
Trying to connect to Sql Server HQ-LYNC2013-BE.MyDomain\mon. using windows authentication...
Sql version: Major: 11, Minor: 0, Build 5058.
Sql version is acceptable.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
Checking state for database QoEMetrics.
State of database QoEMetrics is DbState_RequiresMinorUpgrade.
WARNING: The database QoEMetrics being updated has data file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\DbPath\QoEMetrics.mdf. Supplied path will be ignored.
WARNING: The database QoEMetrics being updated has log file path at
\\HQ-LYNC2013-BE.MyDomain\C$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf and supplied data file path is
\\HQ-LYNC2013-BE.MyDomain\F$\CsData\MonitoringStore\mon\LogPath\QoEMetrics.ldf. Supplied path will be ignored.
Database QoEMetrics set to mode Restricted.
Dropping all procedures, functions and views from database QoEMetrics.
Executing QoEDb.sql...
Setting owner for database QoEMetrics to sa.
Creating login MyDomain\RTCComponentUniversalServices.
Creating user MyDomain\RTCComponentUniversalServices.
Creating Schema MyDomain\RTCComponentUniversalServices.
Adding account MyDomain\RTCComponentUniversalServices to role ServerRole.
Setting database version: Schema Version 62, Sproc Version 90, Update Version 1.
Setting the database QoEMetrics to multi user mode.
Database QoEMetrics is set to multi user mode.
SQL Server Agent is running and its start mode was detected as Auto.
Executing QoEJobs.sql...
VERBOSE: Successfully installed the database. For details, see the following log:
"C:\Users\MK\AppData\Local\Temp\2\Create-MonitoringStore-HQ-LYNC2013-BE.MyDomain_mon-[2014_11_13][14_35_51].log"
VERBOSE: No changes were made to the Central Management Store.
VERBOSE: Creating new log file
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
WARNING: "Install-CsDatabase" processing has completed with warnings. "5" warnings were recorded during this run.
WARNING: Detailed results can be found at
"C:\Users\MK\AppData\Local\Temp\2\Install-CsDatabase-82d6613c-f2e3-47e6-8fc4-8f75d2efe6e4.html".
PS C:\Users\MK>
I hope some one can confirm no issue with what I did ??
Kind Regards
MK

Lync 2013 On Prem - Front End Pool - Second server in pool becomes unavailable when first server is offline

We have one front end pool, that contains 2 front end servers running Lync Server 2013.
When the first server, LFE01 goes offline (to be restarted for instance), the second front end server LFE02 in the same pool's Lync services will suddenly stop and will refuse to start until LFE01's Lync services have started again.
During this time, the Lync client will go from full functioning mode whilst LFE01 is up and running, to reduced functionality (when LFE01 is restarting), to the user being signed out of Lync and not able to log back in. As soon as LFE01 comes back up, users
can log back in to Lync.
We'd ideally like LFE02 to take over the front end server role whilst LFE01 is restarting, and vice-versa.
Checking the event logs on LFE02, I can see the following errors when LFE01 is offline:
This process was not able to update its health status
The Audio-Video Conferencing Server failed to send health notifications to the MCU factory at https://frontendpool.contoso.com:444/liveserver/mcufactory/.
Failure occurrences: 30, since 7/11/2013 3:40:38 PM.
Cause: Either the Front End service is not running, or poor network connectivity.
Resolution:
Verify that the Front End Service is available, and its machine is visible over the network.
This process was not able to update its health status
The IM Conferencing Server failed to send health notifications to the MCU factory at https://frontendpool.contoso.com:444/liveserver/mcufactory/.
Failure occurrences: 30, since 7/11/2013 3:40:42 PM.
Cause: Either the Front End service is not running, or poor network connectivity.
Resolution:
Verify that the Front End Service is available, and its machine is visible over the network.
Server startup is being delayed because fabric pool manager is initializing.
Cause: This is normal when Pool is bootstrapped and indicates that the Front-End is waiting for a quorum of other Front-Ends to be started.
Resolution:
If this event recurs persistently, ensure that 85% of the Front-Ends configured for this Pool are up and running. For 2 or 3 machine Pools, initial cold-start of the Pool requires all machines to be started. If multiple Front-Ends have been recently
decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.
Does the first server in the pool need to be up at all times for the second server to be running? If so, I may need to re-plan my redundancy.

I can't believe how inaccurate these statements are.
Yes as per Microsoft it is best practice to have 3 FE in a pool but that absolutely does not mean that if you have 2 FE server in a pool that your pool will stop working!!
In case when you do have 2 FE servers in a pool your Back End primary database server will act as a vote to keep the quorum for single server still left in a pool and all your clients will keep operating in a pool with one FE still running.
The problem with having 2 FE in a pool as per Microsoft documentation is as follows:
If one of the two Front End Servers goes down, you should try to bring the failed server back up as soon as you can. Similarly, if you need to upgrade one of the two servers, bring it back
online as soon as the upgrade is finished.
If for some reason you need to bring both servers down at the same time, do the following when the downtime for the pool is finished:
The best practice is to restart both Front End Servers at the same time.
If the two servers cannot be restarted at the same time, you should bring them back up in the reverse order of the order they went down.
If you cannot bring them back up in that order, then use the following cmdlet before bringing the pool back up:.
http://technet.microsoft.com/en-us/library/gg412996.aspx
I tested this in my environment which I currently am running with 2 FE servers and I can categorically confirm that pool will continue operating.
However, with all this said I did notice that clients with connection to FE server that is shut down take anywhere from 2-9 min to reconnect. I was trying to figure out why such a long delay until clients reconnect. Possibly it might be because there are
2 FE servers in a pool and Back End server is taking a while to vote in turn delaying auto reconnect process for clients. Second possibility that I'm looking into is that we deployed HLB for sip traffic internally as well and I'm curious if using DNS LB would
fix this delay.
I'm just so disappointed how inaccurate some of these accepted answers above are.

Merge Lync 2013 Edge servers in same pool

Hi guys.
- We had Lync 2013 FE STD version.
- We have added one more Lync 2013 FE STD and done front end pool pairing.
- We had single Edge Pool, soo only 1 EDGE server being in 1 POOL.
We wish to add another Edge server and put previous and this new Edge server in one pool.
This is a printscreen of our current Edge Deployment.
Because we have a federation enabled with external partners who had put in their lync configuration
to trust to our public external address of current edge server: LyncEDGESIP.domain.com, we would like to avoid sending them new address and we have decided to keep that public address and make it EDGE POOL NAME where both edge servers would be inside.
Now we are little bit confused/amused what to do next.
If use LyncEDGESIP.domain.com to be FQDN of EDGE POOL with 2 two edge servers, what would we need to do with our current edge server.
What to put for:
Access Edge Service public address on both edge servers
Web Conferencing Edge Service public address on both edge servers
A/V Edge Service public address on both edge servers.
bostjanc

Go with cutover migration if you can take downtime. Here is the high level summary for your reference;
Remove existing edge server from topology and publish the changes.
Create a new edge server pool in topology builder.
Make sure that access edge , web conference edge and AV edge name remains the same.
Publish the topology and run the setup on both edge servers. You need to configure external and internal IP addresses based on Lync topology.
Replicate the configuration change and run the deployment wizard.
Import the certificate and start the services.
Create additional DNS A records for load balancing externally.
Thanks
Saleesh
If answer is helpful, please hit the green arrow on the left, or mark as answer.
Technet Blog

Questions in Lync 2013 Pool failover behaviour

Hello Team,
Please let us know answers for the below questions:
If
Pool A fails over to Pool B in disaster mode.
Then the original front ends for Pool A are recovered successfully, and services start. Is it expected that User Services, Conference services and CMS would continue to backup via the backup service for pool A routing Groups,
back to their original Pool A servers for the fail back? Or does the fail back, obtain all information from the SQL databases / the pool A user groups in Pool B? Is Pool pairing inactive after a fail over has occurred?
MANY THANKS.

The Failback will sync any changes that were made while users are running on Pool B. My understanding is that Pool pairing resume once Pool A was back online and attempt to sync the data ahead of the actual Pool Failback command.
Have a look at this preso for more details - http://bit.ly/120Ogls View the powerpoint in presentation mode and you will see that when Pool A is repaired, mirroring operations resume even though Pool A users are
still running off Pool B.
Of course the devil is in the details so I would test this out if you can and observe behavior and queuing the health of the pool mirroring process.
Hope this helps.
Dino
Dino Caputo, BA | MCSE | MCTS:OCS/Lync http://www.ucguys.com http://www.enableUC.com

Database changes during pool pairing in lync 2013

Similar Messages

Maybe you are looking for