Carbonite Server Backup
Agent 64-bit for Microsoft Windows
Version 8.60.9144
Release Notes, July 10, 2018
______________________________________________________________________
Contents
1	Overview
1.1	Release History
1.2	Supported Platforms
2	NEW FEATURES
3	INSTALLATION NOTES
3.1	Agent Installation Notes
3.2	Plug-in Installation Notes
4	FIXES, KNOWN ISSUES AND lIMITATIONS
4.1	Fixes
4.2	Known Issues
4.3	Limitations
5	PRODUCT SUPPORT
5.1	Technical Support
5.2	Product Updates
5.3	Documentation
© Carbonite Inc. 2018.  All Rights Reserved.
The release notes are governed by the Terms of Service found at https://www.carbonite.com/terms-of-use/carbonite-general-enterprise-terms-of-service.  Carbonite, at its sole discretion, reserves the right to modify or revoke these Release Notes at any time, without notice.
______________________________________________________________________
1	Overview
The Windows Agent is installed on each Windows system that you want to protect. Using Portal or the legacy Windows CentralControl, you can manage the Agent, back up data to a vault, and restore data from the vault.
Note: Changing job configurations using Portal and Windows CentralControl alternately is not supported. Do not manage the same Agent using both Portal and Windows CentralControl.
You can also install Agent Plug-ins that protect applications and provide additional functionality. The following Plug-ins are available with the 64-bit Windows Agent:
•	Image Plug-in
•	Exchange 2010/2013/2016 DR Plug-in
•	Exchange 2007 DR Plug-in
•	Oracle Plug-in  
•	SQL Server Plug-in
•	Cluster Support Plug-in
Note: Support has ended for Exchange MAPI, SQL Server VDI, and SharePoint Plug-in jobs. Please see the documentation for other ways to protect your data.
1.1	Release History
Version 8.60.9144, March 23, 2018
1.2	Compatibility
Portal	Windows Agent 8.60 is supported with Portal version 8.50 and later.
Important: You can only register a newly-installed Windows Agent 8.60 to Portal version 8.30 or later. However, if a Windows Agent is already registered to a previous Portal version, you can upgrade the Agent to version 8.60 and it remains registered to Portal. To determine your Portal version, sign in to Portal and go to Need Help > About.	
Windows CentralControl	You can manage Windows Agent 8.60 with Windows CentralControl version 8.60 or later. 
Important: Changing job configurations using Portal and Windows CentralControl alternately is not supported. Do not manage the same Agent using both Portal and Windows CentralControl. 
Because important security fixes and new features are available in Portal, we recommend using Portal to manage the Windows Agent instead of the legacy Windows CentralControl. 	
Director	Windows Agent 8.60 is supported with Director version 8.00 and later. 	
Bare Metal Restore	The Windows Agent supports Bare Metal Restore (BMR) backup jobs. BMR backups created using Windows Agent version 8.60 can only be restored using System Restore version 8.60 or later.
Note: Encrypted volumes (BitLocker, TrueCrypt, etc.) are not supported in BMR jobs.	

1.3	Supported Platforms
The Agent is supported on the 64-bit Microsoft platforms shown in the following table, with Intel x64 or AMD64 processors:
Supported Operating System	Editions	Service Pack	
Windows Server 2016	Essentials, Standard, Datacenter, Server Core		
Windows 10	Home, Pro, Enterprise	Fall Creators Update (version 1709)	
Windows Server 2012 R2	Foundation, Essentials, Standard, Datacenter, Server Core		
Windows 8.1	Enterprise		
Windows Server 2012	Foundation, Essentials, Standard, Datacenter, Server Core		
Windows Storage Server 2012	Standard, Workgroup		
Windows 8	Enterprise		
Windows Small Business Server 2011	Essentials, Standard, Premium		
Windows Server 2008 R2	Standard, Enterprise, Datacenter, Server Core	SP1	
Windows Storage Server 2008 R2	Standard, Enterprise, Workgroup, Essentials	SP1	
Windows 7	Enterprise, Premium, Professional, Ultimate	SP1	
Windows Server 2008	Standard, Enterprise, Datacenter, Server Core	SP2	
Windows Small Business Server 2008	Standard, Premium	SP2	
Windows Storage Server 2008	Basic, Workgroup, Standard, Enterprise	SP2	
1.3.1	Image Plug-in Supported Platforms
The Image Plug-in is supported on the 64-bit Microsoft platforms shown in the following table:
Supported Operating System	Service Pack	
Windows Server 2016		
Windows 10		
Windows Server 2012 R2		
Windows 8.1		
Windows Server 2012		
Windows 8		
Windows Server 2008 R2	SP1	
Windows 7	SP1	
Windows Server 2008	SP2	
Note: The Image Plug-in is supported with both UEFI and BIOS firmware.
Note: The Image Plug-in is only supported with NTFS file systems. The Image Plug-in is not supported with ReFS file systems.
Note: Only GPT disks are supported for Image backups (including application-consistent Image backups of volumes with database files) in a cluster.
1.3.2	Exchange Plug-in Supported Platforms
The Exchange 2010/2013/2016 DR Plug-in is supported on the 64-bit Microsoft platforms shown in the following table:
Exchange Server 2016 is supported on:	
Windows Server 2016	Standard, Datacenter		
Windows Server 2012 R2	Standard, Datacenter		
Windows Server 2012	Standard, Datacenter		
Exchange Server 2013 (SP1) is supported on:	
Windows Server 2012 R2	Standard, Datacenter		
Windows Server 2012	Standard, Datacenter		
Windows Server 2008 R2	Standard Enterprise	SP1	
Exchange Server 2010 (SP3) is supported on:	
Windows Server 2012	Standard, Datacenter		
Windows Small Business Server 2011	Standard, Premium		
Windows Server 2008 R2	Standard, Enterprise	SP1	
Windows Server 2008	Standard Enterprise	SP2	
The Exchange 2007 DR Plug-in is supported on the 64-bit Microsoft platforms shown in the following table (including Cluster support with the Cluster Support Plug-in):
Exchange Server 2007 (SP3) is supported on:	
Windows Server 2008 R2	Standard, Enterprise	SP1	
Windows Server 2008	Standard, Enterprise, Datacenter	SP2	
Windows Small Business Server 2008	Standard, Premium	SP2	
Note: Granular Restore is only supported with DR safesets created with the Exchange 2010/2013/2016 DR Plug-in or Exchange 2007 DR Plug-in version 7.10 or later, backed up to Director version 8.00 or later. Portal or Windows CentralControl is required to share DR safesets.
Note: Support has ended for legacy Exchange MAPI jobs. To restore from Exchange MAPI safesets on the vault, install a pre-version 7.5 Agent and restore data using Restore From Another Computer in Portal.
1.3.3	Oracle Plug-in Supported Platforms
The Oracle Plug-in is supported on the 64-bit Microsoft platforms shown in the following table:
Oracle 12c is supported on:	
Windows Server 2012 R2	Standard, Datacenter		
Windows Server 2012	Standard, Datacenter		
Windows Server 2008 R2	Standard, Enterprise	SP1	
Windows Server 2008	Standard, Enterprise	SP2	
Oracle 11g R2 64-bit is supported on:	
Windows Server 2012 R2	Standard, Datacenter		
Windows Server 2012	Standard, Datacenter		
Windows Server 2008 R2	Standard, Enterprise	SP1	
Windows Server 2008	Standard, Enterprise	SP2	
Note: Oracle 11g R2 32-bit is supported on 64-bit operating systems when the corresponding Oracle Instant Client is installed. 
1.3.4	SQL Server Plug-in Supported Platforms
The SQL Server Plug-in is supported on the 64-bit Microsoft platforms shown in the following table (including Cluster support with the Cluster Support Plug-in):
SQL Server 2017 64-bit is supported on:	
Windows Server 2016	Standard, Datacenter		
Windows Server 2012 R2	Foundation, Essentials, Standard, Datacenter		
Windows Server 2012 	Foundation, Essentials, Standard, Datacenter		
SQL Server 2016 (SP2) 64-bit is supported on:	
Windows Server 2016	Essentials, Standard, Datacenter		
Windows Server 2012 R2	Foundation, Essentials, Standard, Datacenter		
Windows Server 2012 	Foundation, Essentials, Standard, Datacenter		
SQL Server 2014 (SP2) 64-bit and 32-bit are supported on:	
Windows Server 2016	Essentials, Standard, Datacenter		
Windows Server 2012 R2	Foundation, Essentials, Standard, Datacenter		
Windows Server 2012 	Foundation, Essentials, Standard, Datacenter		
Windows Server 2008 R2	Standard, Enterprise, Datacenter	SP1	
Windows Server 2008	Standard, Enterprise, Datacenter	SP2	
SQL Server 2012 (SP3) 64-bit and 32-bit are supported on:	
Windows Server 2012 R2	Foundation, Essentials, Standard, Datacenter		
Windows Server 2012 	Foundation, Essentials, Standard, Datacenter		
Windows Server 2008 R2	Standard, Enterprise, Datacenter	SP1	
Windows Server 2008	Standard, Enterprise, Datacenter	SP2	
SQL Server 2008 R2 (SP3) 64-bit and 32-bit are supported on:	
Windows Server 2012 R2 	Foundation, Essentials, Standard, Datacenter		
Windows Server 2012 	Foundation, Essentials, Standard, Datacenter		
Windows Small Business Server 2011 	Premium		
Windows Server 2008 R2 	Standard, Enterprise, Datacenter	SP1	
Windows Server 2008 	Standard, Enterprise, Datacenter 	SP2	
SQL Server 2008 (SP4) 64-bit are supported on:	
Windows Server 2012 R2 	Foundation, Essentials, Standard, Datacenter		
Windows Server 2012 	Foundation, Essentials, Standard, Datacenter		
Windows Server 2008 R2 	Standard, Enterprise, Datacenter	SP1	
Windows Server 2008 	Standard, Enterprise, Datacenter	SP2	
Windows Small Business Server 2008 	Standard, Premium	SP2	
SQL Server 2005 (SP4) 64-bit Standard and Enterprise are supported on:	
Windows Server 2008 R2 	Standard, Enterprise, Datacenter	SP1	
Windows Server 2008 	Standard, Enterprise, Datacenter	SP2	
Windows Small Business Server 2008 	Standard, Premium	SP2	
Notes
•	Support has ended for legacy SQL Server VDI jobs. To restore from SQL Server VDI safesets on the vault, install a pre-Version 7.5 Agent and restore data using Restore From Another Computer in Portal.
•	The SQL Server Plug-in does not support SQL Server Express. To back up a SQL Server Express database, export the database to a flat file and back it up using the Windows Agent.
•	If you back up a SQL Server database and restore it to a different machine running Windows Server 2016 or later, you will not be able to access the restored database using Windows authentication. Instead, do one of the following:
o	Log in to the SQL Server instance using SQL Server authentication. If some databases used accounts with Windows authentication, change the security settings and change ownership to different accounts or recreate the accounts.
o	Start SQL Server in single-user mode and log in to the instance as a member of the computer’s local Administrators group.
o	Use the System Restore application to restore the original machine.
•	SharePoint granular restore is supported with safesets created with SQL Server Plug-in version 7.22 or later, backed up to Director version 8.00 or later. Portal or Windows CentralControl is required to share SQL safesets.
•	Granular restore is not currently supported for SharePoint 2016. 
•	Host-named site collections in SharePoint are not supported for granular restore. 
2	NEW FEATURES
•	Support for Windows 10 Home and Pro editions
•	You can now specify whether scheduled backups should automatically retry after  failed backup attempts. You can also specify the number of times that a backup should retry, and the number of minutes to wait before the next backup attempt.
Note: Automatic retries are only available for scheduled backup attempts. A job will not automatically retry after a failed ad-hoc backup.
•	The Oracle plug-in can now delete archived redo logs after a successful backup. In an Oracle database backup job, you can specify whether archived logs should be deleted after a successful backup, and how old archived logs must be before they are deleted.
Note: Archived logs will be permanently removed from the system after the specified number of days. Please ensure that the logs are backed up using a Local System or Image job.
Note: Automatic retry settings and Oracle archived log settings are available in Portal version 8.50 and later. These settings are not available in Windows CentralControl. 
3	INSTALLATION NOTES
3.1	Agent Installation Notes
3.1.1	Installation Requirements
•	CPU and RAM to meet the basic requirements of your operating system, as prescribed by Microsoft 
•	16-bit (or greater) video properties for optimal GUI display
•	Windows Internet Explorer version 6 or later 
•	A TCP/IP stack 
•	At least 200 MB of free disk space for a new installation. An upgrade may require more. Additional free space is required for Agent files created for backup jobs. 
3.1.2	Conditional Requirements
If you use an antivirus program, disable real-time scanning on reads (called "outgoing" in some antivirus products). 
Note: As a best practice, do not back up antivirus product installation directories. 
3.1.3	Licensing
Agent and Plug-in licenses are distributed automatically when the Agent connects to a vault (based on your license quota). To back up and restore data to or from a vault, you need a valid account, username and password. Contact your service provider to obtain the required information.
3.1.4	Installation/Upgrade
The file name of the Windows Agent installation kit is: Agent-Windows-x64-8-60-9144.exe
The 64-bit Agent kit installs: 
buagent.exe – Version 8.60.9144
VV.exe – Version 8.60.9144
VVAgent.exe – Version 8.60.9144
XLogTranslator.exe – Version 8.60.9144
LogViewer.exe – Version 8.60.9144
BMRCaptureEnvInfo.dll – Version 8.60.3953
evVss.dll – Version 8.60.9144
Exchange2010Plugin.dll – Version 8.60.9144
ExchangeVSSPlugin.dll – Version 8.60.9144
OraPlugin.dll – Version 8.60.9144
SQL2012Plugin.dll – Version 8.60.9144
SystemStatePlugin.dll – Version 8.60.9144
SystemVolumePlugin.dll – Version 8.60.9144
VolumeImagePlugin.dll – Version 8.60.9144
VVClMsg.dll – Version 8.60.9144
VVExch.dll – Version 8.60.9144
Note: The Agent installation places the VVClMsg.dll file in the Agent installation path. This file contains the error codes and resource strings that the event viewer uses to display Agent messages.
Note: Do not install the Agent in a Windows-encrypted directory.
You can upgrade the following Windows Agent versions to version 8.60:
•	Version 8.3x
•	Version 8.10
•	Version 8.0x
•	Version 7.x
•	Version 6.85
Support has ended for legacy Exchange MAPI, SQL Server VDI, and SharePoint Plug-in jobs. You must delete any jobs with these legacy types before you can upgrade the Agent. If you upgrade an Agent where a legacy plug-in is installed, the plug-in will be removed.
Note: To restore from a safeset with a legacy type, install an Agent version 7.34 or earlier with the required plug-in, and restore data using Restore From Another Computer in Portal.
3.2	Plug-in Installation Notes
3.2.1	Image Plug-in Installation/Upgrade Notes
A system reboot is required after you first install the Image Plug-in with an Agent.
A system reboot is also required after you upgrade an Agent with the Image Plug-in to version 8.30.
3.2.2	Exchange 2010/2013/2016 DR Plug-in Installation Notes
An Agent with the Exchange 2010/2013/2016 Plug-in only needs to be installed on one member of a Data Availability Group (DAG). The Agent will have access to the database copies on that particular DAG member.
3.2.3	Exchange 2007 DR Plug-in Installation Notes
For information regarding LCR, SCR, and CCR support, see the Cluster Support Plug-in section.
3.2.4	Oracle Plug-in Installation Notes
The Oracle Plug-in can be installed during a clean install or on an existing Agent. To install on an existing Agent, select "Modify" from the installation options.
3.2.5	SQL Server Plug-in Installation Notes
This version of the Plug-in supports Transparent Data Encryption (TDE) in SQL Server 2017, SQL Server 2016 (SP2), SQL Server 2014 (SP2), SQL Server 2012 (SP3) and SQL Server 2008 R2 (SP3).
3.2.6	Cluster Support Plug-in Installation Notes
To install the SQL, Exchange, and Cluster Support Plug-ins:
1.	Install Agents, SQL Server or Exchange Plug-in, and Cluster Plug-in on the physical nodes.
2.	Register the virtual node to Portal, or connect to the virtual IP using Windows CentralControl to manage the virtual node.
3.	Register the physical nodes to the vault before using the virtual Agent.
4.	Use the new registered virtual Agent as a normal Agent to register to the same vault and create backup jobs. 
4	FIXES, KNOWN ISSUES AND lIMITATIONS
4.1	Fixes
After network interruptions, the Agent can reconnect to the vault and successfully complete backups. (EV-17427, EV-17328)
The Agent has an updated SSL certificate. (EV-19835)
When the Agent tries to reconnect to a vault after a network interruption, failures are logged correctly as information instead of errors unless all reconnection attempts fail. (EV-17547)
German umlauts (e.g., ä, ü, ö) now appear correctly in backup email notifications. (EV-18991)
You can now upgrade a non-English Agent that has a legacy Exchange MAPI, SQL Server VDI, or SharePoint Plug-in. Problems with uninstalling non-English Agents have also been resolved. (EV-10180) 
4.2	Known Issues
4.2.1	Agent Configuration and Backup Issues
Running multiple UNC jobs simultaneously (to the same UNC path) from Windows CentralControl may fail.
WORKAROUND: Run concurrent UNC jobs from the command prompt. (24226)
Backups may fail over UNC path to or from a Windows operating system running an older Windows operating system. Microsoft does not support all Windows operating system combinations for UNC paths. Only those combinations supported by Microsoft are supported. (25579/23712)
On Windows 2012 with deduplication, when a backup job includes the deduplication chunk store, it may be backed up again by the system state job.
WORKAROUND: If backing up system state, exclude the deduplication chunk store data from the job backups to avoid multiple backups of the same data. (24228)
4.2.2	Agent Restore Issues
Granular Restore mount points may not be removed properly after a restore.
WORKAROUND: Manually delete the mount point or reboot the server. (EV-8213/EV-15572)
Backup to a Satellite vault resets the status and location of safesets that exist only on the Base vault. If a safeset is available on the Base vault (but not on the satellite), the Agent may not restore unless you synchronize first. You must run a synchronize operation before you restore. Synchronizing provides updated status and location information about safesets on vaults. (20573/21168/21896)
Windows Server 2012 and 2012 R2 may not restore security streams properly when restoring to an alternate location in some circumstances (UNC path, backup mountpoint). This is Microsoft issue that they are currently addressing. (25780/25775/24166)
4.2.3	Plug-in Configuration and Backup Issues
When an Oracle database is first backed up after the database is changed from NOARCHIVELOG mode to ARCHIVELOG mode, the database’s archived redo logs may not be backed up.
WORKAROUND: Run the Oracle database backup job a second time after the database is changed from NOARCHIVELOG mode to ARCHIVELOG mode to back up the archived redo logs. (EV-19604)
When Cumulative Update 14 is applied to an Exchange 2013 server, an Exchange backup may fail with timeout issues.
WORKAROUND: Apply the following registry key to the Exchange server: HKEY_LOCAL_MACHINE\SOFTWARE\EVault\InfoStage\Agent\Ex2010SequentialValidation=1 (32388)
You cannot back up a SQL Server database that has an AlwaysOn replica in Microsoft Azure. (28055/28054/28053)
A backup job created on a physical node of a SQL Server 2012 cluster may fail (on the physical node) with a stream backup error. Note that this is not a supported backup scenario. There is no support for protecting databases on the virtual node with jobs created on the physical node.
Support for backing up SQL 2012 on a virtual node in a cluster is available with the Agent with the Cluster Support Plug-in. (23622)
An Exchange DR job may fail if launched while a BMR job is running. 
Recommendation: A user should avoid running more than one backup of the same database at the same time.
WORKAROUND: To enable simultaneous backups, manually add the following section to the bottom of job .vvc file (located in the Agent installation directory):
1. vssadmin list writers, copy "writer name" and "writer ID"
2. Append the following section to BMR job vvc 
For an Agent 7.00.1039 and higher:
VSSWriterBackup001 {
  ID = <writer ID>       <<<<<<<<<<<< change to 
       copied "writer ID"
  Include = ".\*"
  InstName = 
  Name = Microsoft Exchange Writer       <<<<<<<<<<<< change to 
       copied "writer name"
  Options = 4
}
(23599)
If you reregister a different computer than was used for the original backup (reregister computer Y to the vault as computer X) and attempt to do another backup of the existing SQL VSS job, the backup may fail. A restore may still be performed successfully.
WORKAROUND: Create a new job and run the backup from the reregistered computer. (23270)
A database with a Simple Recovery Model may not run transaction log backups, but the error message in the log when the backup fails may not indicate this is the reason for the failure:  BKUP-E-04706 job will be forced to fail  BKUP-F-04110 job failed to complete  CAT -E-08056 backup aborted. (24811)
When the VSS backup warning: "Some hard links <> were not selected and have not been backed up.", a file within a selection has hardlinks and some of the hardlinks were not included. These hardlinks may be ignored, but the file and the hardlinks included in the selection may be backed up.
WORKAROUND: Manually include the folder(s) that contain the missing hardlinks. (20281)
4.2.4	Plug-in Restore Issues
A database restore may fail in a mirroring environment when restoring with the "overwrite" option or "overwrite with no recovery" option. As per MSDN: While a database mirroring session is active, the following restrictions apply: 
•	Backup and restore of the mirror database is not allowed. 
•	Backup of the principal database is allowed, but BACKUP LOG WITH NORECOVERY is not allowed. 
•	Restore of the principal database is not allowed. 
(23359)
After reregistering an Agent or running Restore From Another Computer, when performing a VSS Restore job of a SQL 2005 backup (original database names with overwrite selected) to a Windows 2008 R2 machine, the restore may fail. The Restore log and process dialog, however, may report success. (23304)
With Windows CentralControl, using Restore From Another Computer from a SQL standalone machine to a virtual SQL cluster, Restore to file on disk may fail and the wizard may disappear after you select the vault, computer and job. No Dump or Log file may be created.
WORKAROUND: Use Portal to run this type of Restore From Another Computer, or restore using the physical node. (23261)
Safeset bytes processed on the vault for a SQL job with a random read restore of SharePoint may be more than double the actual size of the safeset data. (25016)
A SQL restore may fail when restoring to an alternate database, under the same instance, with the overwrite existing database option selected.
Note: This restore scenario is not supported as we do not rename the database files upon restore. 
Restoring this database may be accomplished if you remove or rename the original database file names before trying to restore. (23099)
When restoring a database to a SQL database other than the original database, the logical and file names may not be renamed to match the database where it is being restored. This feature is not supported by VSS. (22981)
Using Restore From Another Computer on a machine where the SQL Plug-in is not installed, a SQL safeset may be shared using an older UNC path format. (25907)
4.2.5	Install/Uninstall/Upgrade Issues
If a 6.85 Agent that is not registered to Portal is upgraded, the Cluster Plug-in may create a duplicate evault_shared folder on another shared drive (two EVault_Shared folders may exist on one virtual server). (24471)
You may be unable to uninstall the Spanish Agent 7.23 via Windows Control Panel when it has been installed on the Spanish version of the Windows operating system.
WORKAROUND: Launch the Agent installation kit and select Remove. (25365)
When you upgrade a non-English Agent from version 7.24 and attempt to register the Agent to Portal at the same time, the Agent may fail to register to Portal.
WORKAROUND: Instead of upgrading the non-English Agent, uninstall the Agent's program files only, and install the new Agent version to the same folder. (28032)
A silent install on Windows 2012 running Exchange 2013 may require an additional switch when running the command from Power Shell.
WORKAROUND: Run the silent install command from a command prompt.
Correct command: C:\Users\Administrator\Desktop> setup.exe /s 
/v"ACCOUNTTYPE=AutoCreate FEATUREEXCHANGE2010=On SILENTINSTALLDIR=C:
\EVault /l C:\install.log /qn" /IAcceptExchangeServerLicenseTerms
(24368)
4.3	Limitations
The Agent expands deduplicated data before backing it up, which results in larger-than-expected backup sizes.
You can only specify an IPV4 address when registering the Agent to Portal or a vault. IPV6 addresses are not supported. 
The Image Plug-in can back up:
•	Volumes up to 4 TB in size, for volumes with a 2 KB block size 
•	Volumes up to 8 TB in size, for volumes with a 4 KB block size
•	Volumes up to 16 TB in size, for volumes with a 8 KB block size
The SQL Server Plug-in cannot back up a database in the following cases:
•	the database name includes one of the following special characters:  \ ’ ” , / : * ? < > | ^
•	the database has files in Microsoft Azure, and the SQL Plug-in is not installed on the Azure VM
In these cases, the SQL Server Plug-in skips the database that it cannot back up, but backs up other databases in the job.
If you back up a SQL Server database using Windows authentication and restore it to a different machine running Windows Server 2016, you will not be able to access the restored database. To avoid this limitation, back up databases using SQL Server authentication. Alternatively, use the System Restore application to restore the original machine.
After restoring a SQL Server 2016 database that is stretched to Microsoft Azure, you must run a stored procedure (sys.sp_rda_reauthorize_db) to reconnect the local restored database to the remote Azure data. See “Restore the connection between the SQL Server database and the remote Azure database” on the Microsoft Developer Network website: https://msdn.microsoft.com/en-us/library/mt733205.aspx#reconnect
5	PRODUCT SUPPORT
5.1	Technical Support
Contact information for your provider is available through the:
•	Need Help button in Portal
•	Help menu in Windows CentralControl
5.2	Product Updates
Product updates are available from your provider.
5.3	Documentation
The following documentation is available for the Agent:
•	Agent for Windows User Guide
•	Agent release notes (this document)
•	Portal help
•	Windows CentralControl Operations Guide (and help)
•	Plug-in guides