EVault Software
Agent 64-bit for Microsoft Windows
Version 7.34.4009b
Release Notes, March 30, 2016
______________________________________________________________________
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
______________________________________________________________________
1	Overview
The Windows Agent is installed on each Windows server that you want to protect. Using Portal or a legacy CentralControl application, you can manage the Agent, back up data to a vault, and restore data from the vault.
You can also install Agent Plug-ins that protect specific applications and provide additional functionality. The following Plug-ins are available with the 64-bit Windows Agent:
·	Image Plug-in
·	Exchange 2010/2013 DR Plug-in
·	Exchange 2007 DR Plug-in
·	Exchange 2007/2010 MAPI Plug-in
·	Oracle Plug-in
·	SharePoint Plug-in
·	SQL Server Plug-in
·	Cluster Support Plug-in
Note: This Windows Agent version is provided for restoring data from existing Exchange MAPI, SharePoint Plug-in and SQL VDI jobs. You cannot create new backup jobs with these legacy types. Later Windows Agent versions do not support these legacy job types.
This Agent version is for use with:
·	Portal 7.61, Web CentralControl 7.61 or Windows CentralControl 7.30 
Note: The Image Plug-in is only supported in Portal.
·	Director version 6.22 or later
Note: For granular restores, Director version 7.00 or later is required. For Image Plug-in support, Director 7.02b or later is required.
The Windows Agent supports Bare Metal Restore (BMR) backup jobs. For full BMR recovery, EVault System Restore 2.10 or later is required. 
Note: Encrypted volumes (BitLocker, TrueCrypt, etc.) are not supported in BMR jobs.
1.1	Release History
Version 7.34.4009b, March 30, 2016
Version 7.34.4009a, November 20, 2014
Version 7.34.4009, November 14, 2014
Version 7.33.3441, August 18, 2014
Version 7.32.3423, May 8, 2014
Version 7.31.3422, April 3, 2014
Version 7.30.3420, March 17, 2014
Version 7.24.3120, October 31, 2013
Version 7.23.2219, August 29, 2013
Version 7.22.2211, May 9, 2013
Version 7.21.2205, March 28, 2013
Version 7.20.2167a, March 22, 2013
Version 7.20.2167, February 27, 2013
Version 7.10.1650, November 21, 2012
Version 7.00.1039, June 29, 2012
1.2	Supported Platforms
This 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 2012 R2	Foundation, Essentials, Standard, Datacenter, Server Core		
Windows Server 2012	Foundation, Essentials, Standard, Datacenter, Server Core		
Windows Storage Server 2012	Standard, Workgroup		
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 Small Business Server 2008	Standard, Premium	SP2	
Windows Server 2008	Standard, Enterprise, Datacenter, Server Core	SP2	
Windows Storage Server 2008	Basic, Workgroup, Standard, Enterprise	SP2	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	Standard, Enterprise	SP2	

1.2.1	Image Plug-in Supported Platforms
The Image Plug-in is supported on the 64-bit platforms shown in the following table:
Supported Operating System	Service Pack	
Windows Server 2012 R2		
Windows Server 2012		
Windows Server 2008 R2	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. 
Note: The Image Plug-in is only supported with Director 7.02b or later.
Note: Image backup jobs are not supported on clustered virtual nodes.
1.2.2	Exchange Plug-in Supported Platforms
The Exchange 2010/2013 DR Plug-in is supported on the 64-bit Microsoft platforms shown in the following table:
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	
Note: Backups and restores with the Exchange 2010/2013 DR Plug-in are only supported with Director version 6.0 or later. Portal or CentralControl version 6.82 or later is required.
Note: Granular Restore is only supported with DR safesets created with the Exchange 2010/2013 DR Plug-in or Exchange 2007 DR Plug-in version 7.10 or later, backed up to Director version 7.0 or later. Portal or CentralControl version 7.2 or later is required to share DR safesets.
The Exchange 2007 DR Plug-in is supported on the following 64-bit Microsoft platforms (including Cluster support):
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	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	Standard, Enterprise	SP2	
Note: Granular Restore is only supported with DR safesets created with the Exchange 2007 DR Plug-in or Exchange 2010/2013 DR Plug-in version 7.10 or later, backed up to Director version 7.0 or later. Portal or CentralControl version 7.2 or later is required to share DR safesets.
The Exchange 2007/2010 MAPI Plug-in is supported on the 64-bit Microsoft platforms shown in the following table:
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	
Exchange Server 2007 (SP3) (including Cluster support with the Cluster Support Plug-in) 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	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	Standard, Enterprise	SP2	
Note: Exchange 2013 MAPI backups are not supported. However, restore from older MAPI backups to PST is still supported for ANSI-encoded jobs on the Exchange 2013 Server.
Note: You can restore data from existing Exchange MAPI Plug-in jobs, but you cannot create new jobs with this legacy plug-in.
1.2.3	Oracle Plug-in Supported Platforms
The Oracle Plug-in is supported on the 64-bit Microsoft platforms shown in the following table:
Oracle 11g R2 is supported on:	
Windows Server 2008 R2	Standard, Enterprise	SP1	
Windows Server 2008	Standard, Enterprise	SP2	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	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.2.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 2014 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 2012 (SP2) 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 is 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	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	Standard, Enterprise	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	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	Standard, Enterprise	SP2	
Note: You can restore data from existing SQL VDI jobs, but you cannot create new jobs with this legacy type.
Note: 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.
Note: Host-named site collections in SharePoint are not supported for granular restore. 
1.2.5	SharePoint Plug-in Supported Platforms
The SharePoint Plug-in is supported on the following platforms:
Microsoft Office SharePoint Server 2007 (SP1) is supported on:	
Windows Server 2008 R2	Standard, Enterprise, Datacenter	SP1	
Windows Server 2008	Standard, Enterprise, Datacenter	SP2	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	Standard, Enterprise	SP2	
Windows SharePoint Services (WSS) 3.0 (SP2) is supported on:	
Windows Server 2008 R2	Standard, Enterprise, Datacenter	SP1	
Windows Server 2008	Standard, Enterprise, Datacenter	SP2	
Windows Server 2003 R2	Standard, Enterprise	SP2	
Windows Server 2003	Standard, Enterprise	SP2	
Note: To back up and recover Microsoft SharePoint 2010 and 2013 data, use the SQL Plug-in and BMR backups. 
Note: You can restore data from existing SharePoint Plug-in jobs, but you cannot create new jobs with this legacy plug-in. 
Note: SharePoint granular restore is supported with safesets created with SQL Plug-in version 7.22 or later, backed up to Director version 7.0 or later. Portal, Web CentralControl version 7.21 or later, or Windows CentralControl version 7.22 or later is required to share SQL safesets.
2	NEW FEATURES
2.1	New Feature in Version 7.34b
This version of the Windows Agent is provided by EVault from Carbonite for restoring data from Exchange MAPI, SharePoint Plug-in and SQL VDI jobs. Later Windows Agent versions do not support these legacy job types.
You cannot create new backup jobs with these legacy types. Please see the documentation for other ways to protect this data.
2.2	New Features in Version 7.33
·	The SQL Server Plug-in can now protect databases in SQL Server 2014.
·	The SQL Server Plug-in can now protect secondary databases in AlwaysOn Availability Groups. 
·	Support is ending for legacy SQL VDI, Exchange MAPI Plug-in and SharePoint Plug-in jobs. You cannot create new backup jobs with these legacy types. 
2.3	New Features in Version 7.32:
·	Hardware VSS providers are now supported for the Image Plug-in. 
·	The Agent Assistant is no longer installed as part of the "Typical" installation process. You can choose to install the Agent Assistant as part of a custom installation.
2.4	New Feature in Version 7.30:
·	A new Image Plug-in is available with the 64-bit Windows Agent. The Image Plug-in sequentially backs up all blocks on a volume at the block level. You can restore entire volumes, or specific files and folders from image backups. You can also restore entire systems from BMR image backups using the System Restore application.
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 (for communicating with the vault, Agent, and CentralControl software) 
- 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 install the Agent Assistant with the Agent, .NET Framework 2.0 is required.
·	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. 
·	To manage an Agent from both the legacy Windows CentralControl and Web CentralControl interfaces, install its services using the same user identity. That is, the service accounts for the BUAgent and the VVAgent must be the same. Otherwise, the BUAgent will not be able to provide status or administration functions.
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	Install/Upgrade
The file name of the Windows Agent installation kit is: Agent-Windows-x64-7-34-4009b.exe
Included application files: 
The 64-bit Agent kit installs: 
  BUAgent.exe - Version 7.34.4009
  VVAgent.exe - Version 7.34.4009
  VV.exe - Version 7.34.4009
  LogViewer.exe - Version 7.34.4009
  SystemStatePlugin.dll - Version 7.34.4009
  BMRCaptureEnvInfo.dll - Version 2.1.0.2141
  SystemVolumePlugin.dll - Version 7.34.4009
  evVss.dll - Version 7.34.4009
  evVss2003.dll - Version 7.34.4009
  evVssXP.dll - Version 7.34.4009
  Exchange2010Plugin.dll - Version 7.34.4009
  ExchangeVSSPlugin.dll - Version 7.34.4009
  ex2000.dll - Version 7.34.4009
  VVExch.dll - Version 7.34.4009
  VVExchMapi.dll - Version 7.34.4009
  VVClMsg.dll - Version 7.34.4009
  MapiComWrapper.exe - Version 7.34.4009
  OraPlugin.dll - Version 7.34.4009
  SharePointPlugin.dll - Version 7.34.4009
  SQLSvr70.dll - Version 7.34.4009
  SQLVSS.dll - Version 7.34.4009
  SQL2012Plugin.dll - Version 7.34.4009
  XLogTranslator.exe - Version 7.34.4009
Note: The Agent installation will place the VVClMsg.dll file in the 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 these Agents to version 7.34b:
Version 7.3x
Version 7.2x
Version 7.10
Version 7.00
Version 6.85
Version 5.6
3.2	Plug-in Installation Notes
3.2.1	Image Plug-in
A CBT (Changed Block Tracker) driver is installed with an Agent with the Image Plug-in. To take advantage of CBT, a reboot is required for this kernel mode driver to start.
3.2.2	Exchange 2010/2013 DR Plug-in 
An Agent with the Exchange 2010/2013 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 
For information regarding LCR, SCR, and CCR support, see the Cluster Support Plug-in section.
3.2.4	Exchange 2007/2010 MAPI Plug-in 
The MAPI plug-in should be installed and used on the Exchange server that has the Client Access Service role. To protect User Mailboxes, Archive Mailboxes and Public Folders on an Exchange 2010 DAG, the MAPI Plug-in must be installed on each server with the Client Access Service role.
Microsoft CDO (Collaboration Data Objects) version 1.2.1 must be installed on any Exchange server where you want to run MAPI jobs.
Note: Support is ending for the Exchange MAPI Plug-in. You cannot create new backup jobs with this legacy plug-in. Existing jobs will be supported for a period of time. 
3.2.5	Oracle Plug-in 
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.6	SQL Server Plug-in
This version of the Plug-in supports Transparent Data Encryption (TDE) in SQL Server 2008 R2 (SP1), SQL Server 2012, and SQL Server 2014.
This version of the Plug-in uses VSS for full backups (for SQL 2005, 2008, 2008 R2, 2012, 2014) and VDI for transaction logs. It also supports VDI for older backup jobs (for SQL 2005, 2008, 2008 R2).
For information regarding cluster support, see the Cluster Support Plug-in section.
For legacy VDI-based backups: For Microsoft SQL Server 2008 (SP2), the Plug-in requires the SQL-DMO component, which was removed from Microsoft SQL Server 2008. You need to install the "Microsoft SQL Server 2005 Backward Compatibility Components" package. A download is available (within a feature pack for Microsoft SQL Server 2008) at: http://www.microsoft.com/downloads/details.aspx?FamilyID=536FD7D5-013F-49BC-9FC7-77DEDE4BB075&displaylang=en
For legacy VDI-based backups, you must install the Microsoft SQL Server 2005 Native Client. SQL 2008 and 2005 Native Clients can co-exist.
Note: Support is ending for legacy SQL VDI jobs. You cannot create new backup jobs with this legacy type. Existing jobs will be supported for a period of time. 
3.2.7	SharePoint Plug-in
SQL Server Native Client is required.
SharePoint Plug-in backup jobs that use multiple, separate SQL Servers are not supported. That is, you cannot have SharePoint environments that use different SQL Server instances to host the various SharePoint databases.
Note: Support is ending for the SharePoint Plug-in. You cannot create new backup jobs with this legacy plug-in. Existing jobs will be supported for a period of time. 
3.2.8	Cluster Support Plug-in
To install the SQL, Exchange, and Cluster Support Plug-ins:
1. Install Agents, SQL, or Exchange Plug-in, and Cluster Plug-in on the physical nodes.
2. Register the cluster node using Portal or Web CentralControl, or connect to the virtual IP using Windows CentralControl.
3. Use the new registered virtual Agent as a normal Agent. 
4	FIXES and KNOWN ISSUES
4.1	Fixes
4.1.1	Fix in 7.34a release
Compatibility issues have been resolved between the Windows Agent on Windows Server 2003, and Portal or Web CentralControl when recent Windows security updates are installed on the Portal server. This version of the Windows Agent is supported on Windows Server 2003. 
IMPORTANT: You cannot create Exchange MAPI, SharePoint Plug-in, or legacy SQL VDI jobs using Windows Agent 7.34a. If you need to create these legacy jobs, do not upgrade to Windows Agent 7.34a. Use Windows CentralControl to manage the previous Agent version. (28873)
4.1.2	Fixes in 7.34 release
Compatibility issues have been resolved between the Windows Agent and Portal or Web CentralControl when recent Windows security updates are installed on the Portal server. (28059)
SQL backups no longer fail with an ADO timeout error. (24326)
Gaps are now detected correctly for SQL transaction log backups. (28253)
Validation no longer takes an excessive amount of time during an Exchange 2007 backup. (28633)
The Agent can now back up volumes that are larger than 5 TB in one job. However, consider the resulting job size on the vault. When data for a job exceeds 2 TB on the vault, maintenance operations for the job can be negatively affected. For more information, see the Director Operations Guide. (27043)
4.1.3	Fix in 7.33 release
When you run a BMR backup job, EnumDisk:GetDrives warning messages no longer appear. (24815)
4.1.4	Fix in 7.31 release
For Image Plug-in backups, the original size reported now reflects the actual amount of data protected on the volume, and does not include empty space. (27393)
4.1.5	Fixes in 7.30 release
When a SQL database had non-standard file extensions, SQL VSS backups and restores completed successfully, but restored databases were corrupted. This problem no longer occurs. (27119)
The SQL VSS backup now detects log gaps when another 3rd-party backup runs at the same time. (27088)
The following warning no longer appears during successful BMR backups: ENVC-W-04096 Kernel32DLL GetProcAddress of GetFirmwareType failed error=0x7f - API exists on Win2012 and above. (26028)
4.2	Known Issues
4.2.1	Agent Backup Issues
Running multiple UNC jobs simultaneously (to the same UNC path) from CentralControl fails.
WORKAROUND: Run concurrent UNC jobs from the command prompt. (24226)
A backup to a local drive fails when the deferral time specified in the backup job is reached. All SSI files created are left on the local drive. (23921)
Backups can 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 will 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)
When attempting to create a new job after a vault failover (1:1 vault), Windows CentralControl limits the job name to 8 characters instead of 30 characters. When the old active vault comes back online, the 1-30 character limit returns for job name length when creating a new job. (19893)
4.2.2	Agent Restore Issues
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 cannot 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)
Windows Server 2012 storage pools are not restored.
Note: Windows Server 2012 storage spaces are not supported. (23420)
4.2.3	Plug-in Backup and Configuration Issues
You cannot back up a SQL database that has an AlwaysOn replica in Microsoft Azure. (28055/28054/28053)
You cannot test a MAPI profile on Exchange 2013 using Web CentralControl. (25605)
The dates in an Exchange MAPI backup log may be displayed incorrectly if there are XML incompatible characters inside the message. Log messages cannot correctly save non-ANSI characters. (24097)
A MAPI job appears as if reseeding after a Windows Agent 6.85 upgrade to Agent 7.x. This is not a re-seed. Due to a change in the security stream backup option in MAPI backups, the first backup of upgraded Agent will be re-deltized, creating a larger than usual delta file. The delta will return to its typical size on subsequent backups. Also, the log includes the following warning "EXMA-W-09073 skip message body property PR_HTML by error". These warning messages are informational and can be ignored. (23545)
A backup job created on a physical node of a SQL Server 2012 cluster fails (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 will 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 will fail. A restore can still be performed successfully.
WORKAROUND: Create a new job and run the backup from the reregistered computer. (23270)
Windows UAC prevents a new user from launching the Agent VV process on SQL 2008 SP2 / Server 2008. No status is shown on the Process Information screen.
WORKAROUND: (These steps are performed only once)
1.  Press "Start" and run "Control panel".
2.  Select "System and Security".
3.  Select "Change User Account Control settings"
4.  Move button down to "Never notify". Press OK.
5.  Reboot the system.
    (These steps are performed each time for a new user)
6.  Create user 'new user' as an example.
7.  Assign a group of administrators to it.
8.  Run SQL Server Management Studio.
9.  Right-click the Security folder, point to "New", and select "Login…".
10. In the Login – New dialog box, on the General page, enter the name of a user ('new user') in the Login name box.
11. To create a login based on a Windows principal, select Windows authentication. This is the default selection.
12. Press OK. User 'new user' is ready for use.
(23216)
A database with a Simple Recovery Model cannot run transaction log backups, but the error message in the log when the backup fails does 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)
For legacy VDI backups, running SQL maintenance procedures such as re-indexing or Shrink Database may cause the backup to reseed. VSS backups are not affected in this manner as the SQL 2012 Plug-in, using VSS, efficiently detects the changes within database file and sends the changed blocks only (delta). (23163)
You cannot do a MAPI backup of a mailbox with an existing job when the user account associated with the account is moved to a different Organizational Unit (OU) in Active Directory (AD). This issue only affects mailboxes that are specifically selected in the backup. If the backup job is set up to back up at the server or recipient level, the mailbox will be backed up but it will be treated as a new mailbox. The User Principal Name (UPN) should be unique for all users and will not be affected by moving the account in AD.
WORKAROUND: The mailbox must be added to the backup job again and the existing entry removed, as it will generate errors. If planning on moving users between OU within AD, set the backup job to use theserver or recipient levels with recursive settings to continue backing up the mailbox after any changes in AD without having to modify the backup job. (20362)
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 will be ignored, but the file and the hardlinks included in the selection will be backed up.
WORKAROUND: Manually include the folder(s) that contain the missing hardlinks. (20281)
4.2.4	Plug-in Restore Issues
If you mount more than one volume from an Image Plug-in job, and browse, read or copy files from only one volume, the inactive volume will time out all volumes, including the one you are actively using. 
WORKAROUND: When restoring files and folders from Image Plug-in jobs, only mount volumes that you will actively use. (26927)
You cannot restore an Exchange MAPI backup from another computer to Exchange 2013 using Web CentralControl. 
WORKAROUND: Use Windows CentralControl to restore an Exchange MAPI backup from another computer to Exchange 2013. (25608)
Restore to SQL Server 2008 using VDI, with Filestream (BLOB) content, fails.
WORKAROUND: Create the backup job using SQL VSS. (24158)
A database restore can 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, 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 fails and the wizard disappears after you select the vault, vomputer and job. No Dump or Log file is created. 
WORKAROUND: Use Web CentralControl 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 is more than double the actual size of the safeset data. (25016)
SharePoint Workflows and Alerts do not work after a restore using the SharePoint Plug-in. The SharePoint Plug-in does not support backups or restores of Alerts.
WORKAROUND: To back up workflows, a registry key must be set: HKEY_LOCAL_MACHINE\SOFTWARE\EVault Software\Agent\SPS_Workflow_Support=(REG_SZ)"1" (23692)
A SQL restore fails 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 could 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 are not 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 can be shared using an older UNC path format. (25907)
You cannot restore a MAPI backup of a mailbox in which the user was moved to a different Organizational Unit (OU) in Active Directory. 
Note: The user's location in AD when restoring must be the same as when backed up.
WORKAROUND: If the backup was done using ANSI (default) encoding, the contents of the mailbox can be restored to a PST file and then imported into the user's mailbox. If the backup was done using Unicode encoding, the user must be moved back to the original Organizational Unit in AD to restore the contents. (20361)
SQL Plug-in restore fails if the database directory is missing.
WORKAROUND: Manually create the database directory prior to restore. (19466)
When restoring large files (>250mb), a SharePoint restore may fail with the following error: "ADO Error: (E_FAIL) Unspecified error for file SharePoint". This error may occur when RAM resources are relatively limited.
Recommendation: Restore large files in separate restore jobs or to alternate locations (i.e., directory on disk). (15898/15900/17699)
Note: This does not apply to restores from BMR or SQL VSS backup safesets for SharePoint 2010/2013.
Default ANSI MAPI backups can be restored to a PST file, but restores of Unicode MAPI tasks to PST are not supported. (11677/9554)
4.2.5	Install/Uninstall/Upgrade Issues
If a 6.85 Agent that is not registered to Web CentralControl is upgraded, the Cluster Plug-in creates a duplicate evault_shared folder on another shared drive (two EVault_Shared folders exist on one virtual server). (24471)
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 Web CentralControl at the same time, the Agent fails to register to Web CentralControl.
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)
Silent install on Windows 2012 running Exchange 2013 requires 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
Support is ending for Exchange MAPI, SharePoint Plug-in, and legacy SQL jobs. You cannot create new backup jobs with these legacy plug-ins. Existing jobs will be supported for a period of time. Please see the documentation for other ways to protect this data.
The SQL 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 Plug-in skips the database that it cannot back up, but backs up other databases in the job.
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
·	Support link in Web 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)
·	Web CentralControl help
·	Agent Plug-in guides
All documentation is available from your service provider.