Carbonite Server Backup
Director
Version 8.50.1520
Release Notes, September 30, 2019
______________________________________________________________________
Contents
1	Overview
1.1	Release History
1.2	Supported Platforms
1.3	Supported Platforms and Functionality in Microsoft Azure
1.4	Supported Agent Versions
1.5	Supported Vault Versions for Replication
2	NEW FEATURES
3	INSTALLATION NOTES
3.1	System Requirements
3.2	System Requirements in Microsoft Azure
3.3	System Requirements for the Director UI Only
3.4	Licensing
3.5	Install/Uninstall/Upgrade Director
4	FIXES and KNOWN ISSUES
4.1	Fixes
4.2	Known Issues
5	PRODUCT SUPPORT
5.1	Technical Support
5.2	Product Updates
5.3	Documentation
© Carbonite Inc. 2019.  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
This document contains release notes for Director version 8.50. Director is an online data vault that securely receives and stores backup data from servers where Agents are installed. 
Director UI 8.50 is compatible with all supported Director versions. An earlier Director UI version cannot manage a later vault version.
Director 8.50 is supported with Vault API 8.50.
This Director version supports data deletion in response to requests from Carbonite Server Backup Portal. For data deletion, the Reporting service must be installed with each standalone, Base and Active vault and registered to the same Carbonite Server Backup API – Monitoring instance (version 1.30 or later) as Portal 8.60 or later. The Reporting service does not have to be installed with each Satellite and Passive vault; replication processes delete data from these vaults. However, we recommend installing the Reporting service with each Passive vault and registering it to the API so that it is available if you need to fail over to the (formerly) Passive vault. The Reporting service can be installed using the Director installation kit.
Note: Although it is not required for data deletion, the Reporting service must be installed with Satellite and Passive vaults and registered to API – Monitoring to provide data through API – Monitoring calls. 
Note: The Reporting service and data deletion are not supported on vaults in Microsoft Azure.
1.1	Release History
Version 8.50.1520, September 30, 2019
1.2	Supported Platforms
Director 8.50 vaults are supported on the following 64-bit platforms:
•	Windows Server 2019 Datacenter
•	Windows Server 2019 Standard
•	Windows Server 2016 Datacenter
•	Windows Server 2016 Standard
•	Windows Storage Server 2016
•	Windows Server 2012 R2 Datacenter
•	Windows Server 2012 R2 Standard
•	Windows Storage Server 2012 R2
•	Windows Server 2008 R2 Datacenter (SP1)
•	Windows Server 2008 R2 Enterprise (SP1)
•	Windows Server 2008 R2 Standard (SP1)
The Director UI is supported on the following 64-bit platforms:
•	All platforms supported for Director 8.50 vaults (listed above) and:
•	Windows 7 Ultimate (SP1)
•	Windows 7 Professional (SP1)
•	Windows 10 Enterprise
•	Windows 10 Pro for Workstations
Director is only supported on English operating system versions.
Director is not supported on a Windows system that is configured as a domain controller.
1.3	Supported Platforms and Functionality in Microsoft Azure
In Microsoft Azure, Director 8.50 vaults are supported on:
•	Windows Server 2016 Datacenter
•	Windows Server 2012 R2 Datacenter
For upgrades in Azure, Director 8.50 vaults are also supported on Microsoft Windows Server 2012 R2 Standard.
The maximum supported size for a vault in Azure is 12 TB.
A Director 8.50 vault in Microsoft Azure is only supported as:
•	a standalone vault that receives backup data directly from Agents.
•	a Passive vault in 1:1 replication 
•	a Base vault in N:1 replication
The Director UI can also be installed on a VM in Azure.
When Director is installed on a VM in Azure, the following components and functionality are not supported:
•	Secondary and archive storage
•	Carbonite Server Backup Reports on the same machine as the Director
•	N:1:1 replication
•	Reporting service functionality (including sending data to API – Monitoring and Data deletion in response to requests from Portal)
There is no support for blob storage in Azure. The Director writes all data to the VM’s local disks.
1.4	Supported Agent Versions
Agent versions 8.xx, 7.xx and the latest supported 6.xx Agents can be used with Director 8.50  vaults.
1.5	Supported Vault Versions for Replication
In many-to-one (N:1) replication, data can be replicated from Director 8.50, 8.4x, 8.30 and 8.00h Satellite vaults to a Director 8.50 Base vault. 
In one-to-one (1:1) replication, data can be replicated from:
•	a Director 8.50 Active vault to a Director 8.50 Passive vault. The vaults must have approximately the same storage capacity.
•	a Director 8.4x, 8.30 or 8.00h Active vault to a Director 8.50 Passive vault. These replication configurations are supported for upgrade purposes only.
In many-to-one-to-one (N:1:1) replication, data can be replicated from:
•	Director 8.50, 8.4x, 8.30 and 8.00h Satellite vaults to a Director 8.50 Active Base vault.
•	a Director 8.50 Active Base vault to a Director 8.50 Passive Base vault. The vaults must have approximately the same storage capacity.
•	a Director 8.4x, 8.30 or 8.00h Active Base vault to a Director 8.50 Passive Base vault. These replication configurations are supported for upgrade purposes only.
2	NEW FEATURES
Suspect task reduction
This Director version includes changes to reduce the occurrence of suspect tasks. In addition to defect fixes described here, the following changes have been made:
•	Each safeset now has its own optimized index. Because each safeset index is independent, if one safeset is deleted, indexes for other safesets in the same task do not have to be updated. This reduces the number of times that index files are processed and prevents changes which could result in suspect tasks.
•	Deduplication only occurs when there is a significant amount of data to deduplicate. Before running deduplication on a task, Director now determines the percentage of incremental data since the previous backup and the percentage of storage space that can be reclaimed through deduplication. Deduplication only runs if 25% more data has been backed up and 10% of storage space can be reclaimed. This reduces the number of times that files are changed and reduces the possibility of suspect tasks. 
•	Data is no longer deduplicated after it has been replicated to a target vault. Because data is deduplicated during dual-stage replication, there is no need to deduplicate the data again on the target vault. Eliminating this operation reduces the load on system resources which could reduce the possibility of suspect tasks.
Additional information in replication failure emails
Notification emails sent when a replication session fails now include the customer, location, agent and task names. This information appears in a task hierarchy (i.e., customer/location/agent/task).
Log files saved for 6 months by default
Director logs are now saved for 6 months instead of 14 days by default, making it easier to determine the cause of some problems. 
If the log file retention period has been changed for a Director vault, the custom value will be preserved when Director is upgraded to Version 8.50. 
3	INSTALLATION NOTES
3.1	System Requirements
Disk space	Minimum 3 GB of installation disk space	
Required software	Microsoft .NET Framework 3.5 and 4.5	
Ports	Ports for backup and replication must be configured. For a list of required ports, see the Director Installation Guide. 	
Cryptographic services	Cryptographic Services must be running on systems running Director.	
3.2	System Requirements in Microsoft Azure
You can install Director 8.50 on a VM in Microsoft Azure that has the following characteristics:
VM	A4 Standard (8 cores, 14 GB memory) or better	
Operating system	Windows Server 2016 Datacenter
Windows Server 2012 R2 Datacenter
Windows Server 2012 R2 Standard (for upgrades only)
Note: Director is not supported on a Windows system that is configured as a Domain Controller.	
Disks	16 attached disks, 1023 GB each
The disks must be formatted before the Director is installed. 	
Required software	Microsoft .NET Framework 3.5 and 4.5		
IP address	Static public IP address
After installing Director 8.50 on a VM in Azure, you must run the following command to specify an externally-available IP address or FQDN for backups, restores and replication:
vaultop update_node_in_cluster externalAddress:<external_IPaddress_or_FQDN> internalAddress:<internal_IPaddress_or_FQDN>
For more information, see the Director Installation guide.	
Ports	Ports for backup and replication must be configured on the VM. For a list of required ports, see the Director Installation guide. 
Ports must also be opened in your local firewall to allow backups and replication to Azure.	
3.3	System Requirements for the Director UI Only
CPU and RAM	Must meet the basic requirements of the operating system, as specified by Microsoft	
Disk space	100 MB of installation space	
Cryptographic Services must be running on systems running the Director UI.
3.4	Licensing
You must enter a valid vault license when installing a Director vault. Director will function with this license for only 30 days unless you activate the license during this time period.
For Director license activation, cryptographic services must be running, and port 443 must be open for outbound communication.
To enable vault replication, you must add replication licenses. 
3.5	Install/Uninstall/Upgrade Director
3.5.1	Install
The Director installation kit file name is: Director-8-50-1520.exe
This executable file contains all components necessary to install vaults, the Reporting service, and the Director UI. 
The following 64-bit vault application files are installed in the Director programs installation directory (Default location: C:\Program Files\Carbonite Server Backup\Director\prog):
  AdminService.exe – version 8.50.1520
  AgentInfoReports.exe – version 8.50.1520
  DBBackup.exe – version 8.50.1520
  MigrateSecondary.exe – version 8.50.1520
  QMCmd.exe – version 8.50.1520
  ReplService.exe – version 8.50.1520
  ReplVault.exe – version 8.50.1520
  SecondaryOp.exe – version 8.50.1520
  VVAnalyz.exe – version 8.50.1520
  VVArchive.exe – version 8.50.1520
  VVCopy.exe – version 8.50.1520
  VVExport.exe – version 8.50.1520
  VVImport.exe – version 8.50.1520
  VVListen.exe – version 8.50.1520
  VVMigrat.exe – version 8.50.1520
  VVMove.exe – version 8.50.1520
  VVPoolOp.exe – version 8.50.1520
  VVPurge.exe – version 8.50.1520
  VVQManager.exe – version 8.50.1520
  VVRecall.exe – version 8.50.1520
  VVServer.exe – version 8.50.1520
  VVSvrDae.exe – version 8.50.1520
  VVSvrMonitor.exe – version 8.50.1520
  Activation.dll – version 8.50.1520
  DailyStatusReport.dll – version 8.50.1520
  Evault.Synchweb.Bridge.dll – version 8.50.1520
  Evault.Synchweb.Data.dll – version 8.50.1520
  MigrateSecondaryManager.dll – version 8.50.1520
  PerfCounters.dll – version 8.50.1520
  Pool.dll – version 8.50.1520
  PoolManagement.dll – version 8.50.1520
  PoolManager.dll – version 8.50.1520
  PoolV5.dll – version 8.50.1520
  ReplicationTransport.dll – version 8.50.1520
  ReplPTCPXfer.dll – version 8.50.1520
  RetentionManager.dll – version 8.50.1520
  Shared.dll – version 8.50.1520
  SqlDbLib.dll – version 8.50.1520
  UNCStorage.dll – version 8.50.1520
  VaultDbCfg.dll – version 1.0.0.1
  VaultHive.dll – version 8.50.1520
The following 64-bit files are installed in the Director utilities installation directory (Default location: C:\Program Files\Carbonite Server Backup\Director\Utils):
  VaultOp.exe – version 8.50.1520
  Activation.dll – version 8.50.1520
  PerfCounters.dll – version 8.50.1520
  Shared.dll – version 8.50.1520
  UpgradeDll.dll – version 8.50.1520
The following 32-bit files are installed in the Director UI installation directory (Default location: C:\Program Files(x86)\Carbonite Server Backup\Director\Admin):
  VMAdmin.exe – version 8.50.1520
  Activation.dll – version 8.50.1520
  Shared.dll – version 8.50.1520
For installation information and instructions, see the Director Installation Guide.
If you choose to install the Reporting service, the following 64-bit files are installed in the Reporting Service installation directory (Default location: C:\Program Files\Carbonite Server Backup\Director\ReportingService):
  ReportingService.exe – version 8.50.1520
  Activation.dll – version 8.50.1520
  Shared.dll – version 8.50.1520
  SQLDbLib.dll – version 8.50.1520
  UNCStorage.dll – version 8.50.1520
3.5.2	SQL Server Express version
When you install a Director 8.50 vault, SQL Server Express 2014 Service Pack 2 (SP2) is installed as the vault database engine.
No other programs can have databases on the SQL Server instance for Director (named EVAULT_DB or EVAULT_DB_V800). If you uninstall Director, the SQL Server instance will be removed, along with all databases in the instance.
3.5.3	Uninstall
You can uninstall Director software by running the installation kit executable file or by using Add/Remove Programs in the Windows Control Panel. A restart may be required.
Uninstalling Director software removes Director programs, services (including the Reporting service) and most configuration data from the vault. Backup data (storage pools) must be removed manually. Re-installing a Director vault does not provide access to the old vault data.
3.5.4	Upgrade
You can upgrade from Director 8.4x, 8.3x or 8.00h to Director 8.50. If a previous Director version is installed, you must upgrade to Director 8.00h before upgrading to version 8.50.
We recommend bringing a vault offline before an upgrade. For more information, see the Director Installation Guide.
If a Director 8.30 vault with a Reporting service is registered to API – Monitoring 1.2.0, upgrade API – Monitoring to version 1.3.0 or later before upgrading Director to version 8.50. Director 8.50 is not supported with API – Monitoring 1.2.0.
If you upgrade a Director vault where the Reporting service is not installed, you can choose to install it during the upgrade.
If you upgrade a Director vault where the Reporting service is installed, the installer will upgrade the Reporting service to version 8.50. If the Reporting service is registered to API – Monitoring before the upgrade, the Reporting service remains registered to the API after the upgrade. 
IMPORTANT: To silently upgrade Director to version 8.50 or silently install Director 8.50, you must first record a response file (.iss file) using the Director 8.50 installation kit. You cannot use a response file created with a previous Director version. For instructions, see the Director 8.5 Installation Guide.
4	FIXES and KNOWN ISSUES
4.1	Fixes
•	An issue has been addressed where restores sometimes took a long time to finish, particularly when restoring a file from a backup that includes a large number (e.g., millions) of files. (EV-29205)
•	An issue has been addressed where replication started for a task while cleanup operations from a previous replication session were still working on the task. When this occurred, tasks were marked suspect and a File is not available error appeared in logs. (EV-19944, EV-26405)
•	If a Director 8.30 vault with a Reporting service is registered to API – Monitoring 1.2.0, the Admin service, Vault API and Director UI remain responsive and do not time out when you upgrade the vault to version 8.50. 
Note: You should upgrade API – Monitoring to version 1.30 or later. API – Monitoring 1.2.0 is not supported with Director 8.50. (EV-26041)
•	If the Director UI cannot connect to the Admin Service because of a network disruption or because the service is busy, the Director UI now tries connecting to the Admin Service ten times. This prevents workflows (e.g., vvcopy) from failing when the Director UI cannot connect to the Director Admin Service. (EV-27403)
•	An issue has been addressed where tasks were marked suspect after the replication service locked files but did not unlock them properly. (EV-27566, EV-27068, EV-7765)
•	A task is no longer marked as suspect when Director cannot read from a storage location during an operation on the task. (EV-23277, EV-23404)
•	An issue has been addressed where optimization processes incorrectly marked tasks as suspect after the tasks were fixed and verified. (EV-20147)
•	An issue has been addressed where backups encountered connection problems with the vault, got stuck and could not be stopped using the job monitor. (EV-29741, EV-21007)
•	During a copy operation involving multiple storage locations, optimized index files are now saved in the same location as their corresponding index files. This can prevent performance degradation when Director cannot find the optimized index files. (EV-22382)
•	In rare cases when moving safesets from primary storage to secondary storage, Director no longer repeatedly tries to delete a file that does not exist. (EV-20929)
•	When moving data between storage locations, Director always runs a crc check to validate files. The skipcrc option is no longer available in the vvmove command or in the Move Data/Retire a Failed Storage Location wizard. (EV-30280)
•	An issue with the vvmove command has been addressed where tasks were marked suspect and a Failed hash value check error appeared in logs after pool files were moved. (EV-30047)
•	An issue has been addressed where Director constantly wrote to ServerHost logs and caused high CPU usage, agent reconnection issues or failed backups. (EV-27180, EV-28533)
•	Performance issues with optimization processes that were launched from the maintenance queue have been addressed. (EV-23957)
4.2	Known Issues
•	In some cases, the Reporting service is not uninstalled when you uninstall Director.
WORKAROUND: After uninstalling Director, uninstall the Reporting service using the Control Panel or by running the separate Reporting service installer. (EV-33802)
•	Data is missing from the Storage Pool Summary report after a Director upgrade. Data for a job only appears in the report after an operation (e.g., backup, replication or maintenance) has run for the job. 
WORKAROUND: Wait until a backup or other operation has run for each job before running the Storage Pool Summary report. Alternatively, expand the vault’s entire tree structure in the left pane of the Director UI before running the report. To do this, click the vault and then press the asterisk (*) key on the keyboard. (EV-33236)
•	If a job is seeded to a vault using Agent version 7.34 or earlier and reseeded using Agent version 7.50 or later, the vault cannot deduplicate the job data to reduce the size of the pool system. (EV-25740)
•	If you change the account for running Director services after the Reporting service is registered to API – Monitoring, the Reporting service becomes unregistered to the API.
WORKAROUND: After changing the account for running Director services, re-register the Reporting service to the API to retain Reporting service and data deletion functionality.
•	If vault storage is accessed using a user account, backups can fail with the following error: Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.
WORKAROUND: When you connect to a vault, use the VaultService account credentials. (30466)
•	After a vault with multiple NICs is upgraded, the correct NIC might not be used for 1:1 replication.
WORKAROUND: Update the vault’s external and internal IP address using the vaultop update_node_in_cluster command. (30163)
•	If you try to fail over from the Active vault to a Passive vault in 1:1 replication, if safesets have been expired from the Active vault and all non-expired safesets have been replicated to the Passive vault, a dialog box incorrectly states that replication events are pending or running. (30317)
•	After an upgrade, the Passive vault in a 1:1 replication configuration may have incorrect alternative vault information. After a failover, tasks may fail.
WORKAROUND: After a failover, using the Agent Connection tab of the Vault Settings dialog box for the new Active vault, remove incorrect alternative vault information and enter the IP address of the formerly Active vault. (30219)
•	If you try to copy a safeset for a task when a backup is running for the same task, the copy operation fails. 
WORKAROUND: Before copying a safeset for a task, check that there is no backup running for the task. (30130)
•	If you clone a computer from a location on the Satellite vault to a new location on the Base vault, subsequent replications for the computer happen between the original location on the Satellite vault and the new location on the Base vault. The Diff report shows many mismatched objects because the computers are under different locations.
WORKAROUND: Delete the location on the Base vault or Satellite vault, and then replicate. (23539)
•	Running the vvmigrat command with the parameters file will completely delete the specified customer from the vault even if only one job is specified in the parameters file. (22084)
•	If a Director upgrade is cancelled because a Director process is running, the installation rollback is not always complete. Existing Director installations might become unusable. A reboot is required after the upgrade is cancelled. (22831)
5	PRODUCT SUPPORT 
5.1	Technical Support 
Contact information for your provider is available through the Help > Getting Support menu.
5.2	Product Updates
Product updates are available from your provider's website.
5.3	Documentation
The following documentation is available for Director: 
•	Director User Guide
•	Director online help
•	Director Installation Guide
•	Director release notes (this document)