Tech Blog

I knew something was wrong this morning before I’d even sat down, then it hit…a colleague raise his head and said those dreaded words “all the Veeam jobs failed”….urrrrggghhhh, brilliant.

I love Veeam 95% of the time!!  When it works its ace but when it fails it’s a total bitch to sort.

Having said that I did manage a fairly quick fix today, so here was the error on every job:

[VeeamServer1] Failed to connect to Installer service.
[VeeamServer1] Failed to discover Installer service.
Backup Console version '6.5.0.128' is not compatible with Installer service on host ' VeeamServer1’.

So from the above error it looks like a service has been updated and Veeam can’t communicate.

So to confirm this let do to the Backup Infrastructure and see whats what:

There’s definitely a issue, if I try a rescan I get the following:

Here’s the text:

Fail Disks and volumes discovery for Windows server 'Server1.Doamin' failed Error: Backup Console version '6.5.0.128' is not compatible with Installer service on host ''Server1.Doamin'.
Fail Session failed Error: Backup Console version '6.5.0.128' is not compatible with Installer service on host ''Server1.Doamin'.

Veeam doesn’t make it particularly easy to work out version within Veeam itself so I’ve found the best thing to do is go to Control Panel and Programs and Features:

So as you can see the Veeam Backup Transport agent is newer than the rest of Veeam which is obviously where the problem is.

The reason this happened is a admin on a remote site on a different Veeam server running a newer version of Veeam must of opened Veeam and noticed an agent was out of date and decided to update it (Veeam can be used to copy jobs and proxy backups between sites and servers).

So once he did this the message went away his site and he was happy, the problem is we’re not!! Also just as a bonus we can prove this by digging in the event log:

So what do we do?  Restore Veeam to an older version on the remote site? Well that seems silly, so lets just update Veeam to match the other.

So I downloaded the patch and updates the server:

You’ll notice I was prompted to update the remote agents on other proxy servers (this is what the other admin did).

Double check the version in Veeam:

Run a test job:

And we’re fixed!!

I recently read a brilliant blog by Michael B. Smith which you can read here which talks about the flaws of Exchange 2013, all his options are absolutely valid and justified but here’s my take on some of them:

OWA

• Help -> About is gone – MEH
• It’s very slow. – Easily improved
• No S/MIME support – Thank god
• No Public Folder support, either for legacy public folders or modern public folders. – Who uses PFs anymore
• No distribution list moderation – Will miss this
• No way to move the reading pane – Odd
• Built-in spell-check is gone. IE 10 provides spell-check natively, but earlier versions of IE do not. A third-party add-in or an alternate browser is required. – THIS IS STUPID

Client Connectivity

• No BES support – No one seems to like BES anymore
• Outlook 2003 is no longer supported. – GOOD
• Direct MAPI access to the Exchange server is no longer supported.  RPC/HTTP (Outlook Anywhere) is required. – This will be annoying
• Outlook now reports that the server is it connected to is <<guid>>@<<active-directory-domain>>. This is intentional, if misguided. – Agreed

Installation and Architecture

• Cannot uninstall individual roles from a server, must uninstall all of Exchange – This is BALLS
• Install is painfully slow – I didnt find this
• The Hub Transport role is gone. There is now a Front End Transport service on CAS servers and Mailbox Transport services on Mailbox servers. – I don’t mind this as I never had a separate HT server for any installation
• The Unified Messaging role is gone. There is a now a Unified Messaging Call Router service on CAS servers and a Unified Messaging service on Mailbox servers. – Never installed it, UT is way too expensive!
• Documentation is minimal at best – This will change with time but agree it annoying
• Cannot be installed along with Exchange 2007 or Exchange 2010 – Really, that ridiculous!
• Exchange 2013 Edge server is not available – Interesting!
• Forefront Protection for Exchange is gone – Fail, I like Forefront

Exchange Management

• The Exchange Management Console is gone as is the Exchange Control Panel. They are mainly replaced by the Exchange Administration Center (EAC); which is completely web based. – I appreciate this is different but makes life easier in the long run.
• If you are attempting to use EAC with IE 10, you need KB2761465 (released on December 11, 2012). – Silly!
• The Exchange Best Practices analyzer is no more. – Urgh, this was always really useful when looking at new sites setups!
• The Exchange Mail Flow Troubleshooter is no more. – Shame, liked this.
• The Exchange Performance Troubleshooter is no more. – Shame, liked this.
• The Exchange Routing Log Viewer is no more. – Never used it personally
• Antispam cannot be managed from the Exchange Administration Center; it must be managed using PowerShell in the Exchange Management Shell – Thats annoying and I like powershell
• System Center Data Protection Manager (DPM) version required for backups of Exchange 2013 is SC DPM 2012 SP1 – for now maybe