CommVault Synthetic Full Issue – SharePoint

Currently backing up a SharePoint Portal of which the database is not even 150GB. The backup isn’t a VM snapshot, but the Application Aware backup which backs up all the SharePoint Lists, Libraries and Sites.

Been running synthetic full backups on this site for the past 18months.

Noticed the last month that it was reporting that the application size was growing rapidly. Like really rapidly and causing the backup to run well over its allocated time.

Jan 2018 1.55TB – 65hours

Apr 2018 2.86TB – 80hours

July 2018 3.55TB – 100hours

Nov 2018 4.13TB – 120hours

Jan 2019 4.29TB – 89hours (with 8 streams running).

Ran a Full backup.
Ran in 9 hours. Total application size was 79GB.

What the synthetic full does, is append any changes to the Full backup (the first full backup file back before Jan 2018). This keeps the physical backup file footprint small.

Running a Full backup instead of Synthetic backup cleaned the ‘slate’.

So the new schedule we have is:
Full backups once a month
Synthetic Full every other Friday night
Incrementals throughout the week.

 

Reading Material:

http://documentation.commvault.com/commvault/v11/article?p=11694.htm

 

Technical Details:

CommVault v11 Service Pack 10.

SharePoint 2010 with March 2018 CU.

Windows Server 2008 R2.

SQL Server 2008 R2.

April 2019 Microsoft Patching Issues

There are several Windows Patches released for April 2019 that are causing problems:

Applies to Windows 7, Windows 8.1, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2.

  • Issues with computers running Sophos Endpoint Protection managed by Sophos Central or Sophos Enterprise Console that cause machines to become unresponsive.
  • Issues with Avast and Avira machines that cause machines to become unresponsive.


Solution if running Sophos:

If you are running Sophos, follow the below instructions:
– Add the following Windows exclusions to all Antivirus and HIPS policies in your Enterprise Console.

%programfiles%\Sophos\Sophos Anti-Virus

%programfiles(x86)%\Sophos\Sophos Anti-Virus

NP – only perform the above if the machine hasn’t rebooted.

If the machine has rebooted, uninstall all the April patches and apply the above solution.

Solution if running Avast:
Avast has released a micro-update to fix this issue.
Once the update has been maked ‘completed’, reboot your machine and leave for 15mins or so for the emergency updater to work. Then reboot the machine again.

Microsoft has temporarily blocked devices from receiving certain updates if Avira, Sophos or Avast are installed.

Sources:

https://community.sophos.com/kb/en-us/133945

https://kb.support.business.avast.com/GetPublicArticle?title=Windows-machines-running-Avast-for-Business-and-Cloud-Care-Freezing-on-Start-up

Visual Studio Error – Unable to access the IIS metabase

Tried to deploy a SharePoint 2010 build via Visual Studio 2015.

Got the following error:

Unable to access the IIS metabase. You do not have sufficient privledge to access IIS web sites on your machine.

On the server/workstation, click run and enter the following path:

%systemroot%\System32\inetsrv\config

You will be prompted with a window to grant permissions to the folder and click yes.

I performed this and still no luck.

The solution was to run Visual Studio as Administrator. And the solution was able to build.