Sadly, I haven’t been able to commandeer a system for testing the 2013 Preview yet. Might have to use my own…
Anyway, today’s post is about the Monitoring and Archiving server roles. And what’s happening to them for 2013.
I find this particular set of changes interesting. Not because they aren’t as extensive as some other ones (which I’ll address later on), but because they represent a better service efficiency for server hardware. Lync Server is tightening itself up with its next iteration.
More Archives, More Efficient Location: How Monitoring and Archiving Will Change in Lync Server 2013
1. They are no longer separate servers. Both Monitoring and Archiving have become optional add-ons, collocated on Front End servers.
I think this is a smart idea. Monitoring Server for Lync Server 2010 does its job very well. Keeping its functionality intact makes sense (especially since we’re accustomed to the Server Reports format by now). Building them into Front End cuts down on hardware cost and administration time.
2. Archiving integrates with Exchange 2013 (still in Preview right now, as well). Separate SQL databases are not necessary, if users are homed on Exchange 2013 Preview.
3. Whiteboards and Poll content are now archived. Now if someone wrote an important note on the Whiteboard during the last meeting, and you forgot it? You can check the Archive (well, ask the Lync Server administrator to run a report for you!).
4. The SQL mirroring available in 2013 covers Archiving. Let’s say you have an Enterprise Edition pool in your local San Francisco office, and one set up in the Chicago office. You set up SQL mirroring between Back End servers at each location. All the SQL databases there – including your Archiving Server – are included. That is, if you want it to.
5. When you deploy your Archiving role, you can opt to enable mirroring of its SQL store as well. Mirroring is not a requirement; you choose whether or not to include Archiving.
Archiving in SQL Mirroring: To include or not to include?
On the one hand, mirroring will improve availability. But on the other hand, high availability is most important in daily operations. Does it make sense to use that for Archiving? Won’t existing backup routines be enough?
I can think of one situation when it makes sense to include Archiving in SQL mirroring: Legal compliance.
If your organization MUST maintain complete records in order to comply with federal compliance concerns, then yes. Mirror your Archiving role within Lync Server 2013.
One quick reminder: Create a new SQL instance in SQL Server 2008 or SQL Server 2012 when you setup these roles!
Do you plan to use Monitoring/Archiving in Lync 2013? The same way you do in Lync 2010, or something different?