Carbonite Server Backup
Director
Version 8.40.1347
Release Notes, September 11, 2018
______________________________________________________________________
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. 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
This document contains release notes for Director version 8.40. Director is an online data vault that securely receives and stores backup data from servers where Agents are installed. 
Director UI 8.40 is compatible with all supported Director versions. An earlier Director UI version cannot manage a later vault version.
Director 8.40 is supported with Vault API 8.40.
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 the vault and registered to the same Carbonite Server Backup API 1.3.0 instance as Portal version 8.60. 
Note: The Reporting service and data deletion is not supported on vaults in Microsoft Azure.
1.1	Release History
Version 8.40.1347, September 11, 2018
1.2	Supported Platforms
Director 8.40 vaults are supported on the following 64-bit platforms:
•	Windows Server 2016 Datacenter
•	Windows Server 2016 Standard
•	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.40 vaults (listed above) and:
•	Windows 7 Ultimate (SP1)
•	Windows 7 Professional (SP1)
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.40 vaults are supported on:
•	Windows Server 2016 Datacenter
•	Windows Server 2012 R2 Datacenter
For upgrades in Azure, Director 8.40 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.40 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
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.40  vaults.
1.5	Supported Vault Versions for Replication
In many-to-one (N:1) replication, data can be replicated from Director 8.30 and 8.40 Satellite vaults to a Director 8.40 Base vault. 
In one-to-one (1:1) replication, data can be replicated from:
•	a Director 8.40 Active vault to a Director 8.40 Passive vault. The vaults must have approximately the same storage capacity.
•	a Director 8.30 Active vault to a Director 8.40 Passive vault. This replication configuration is supported for upgrade purposes only.
In many-to-one-to-one (N:1:1) replication, data can be replicated from:
•	Director 8.30 and 8.40 Satellite vaults to a Director 8.40 Active Base vault.
•	a Director 8.40 Active Base vault to a Director 8.40 Passive Base vault. The vaults must have approximately the same storage capacity.
•	a Director 8.30 Active Base vault to a Director 8.40 Passive Base vault. This replication configuration is supported for upgrade purposes only.
2	NEW FEATURES
Data deletion
This Director version supports data deletion in response to requests from Carbonite Server Backup Portal. 
When deleting a job in Portal, an Admin user can request that backup data for the job be deleted from all vaults. If the data deletion is not canceled during a 72-hour waiting period, the deletion request is sent to vaults where the job data is stored. In response to the request, Director deletes the data from standalone, Satellite, and Active vaults. 
Note: Data is not deleted from Passive vaults in response to these requests. Instead, replication processes manage data deletions on Passive vaults.
If a deletion request fails, an email notification is sent to a vault administrator, whose email address is specified in Portal. The vault administrator can then manually delete the data.
To enable data deletion functionality: 
•	the Reporting service must be installed with the vault and registered to Carbonite Server Backup API 1.3.0.
•	Portal 8.60 or a later version must be registered to the same Carbonite Server Backup API instance as the Reporting service.
•	the data deletion feature must be enabled in Portal.
Location code change
Location codes (also known as billing codes) can now include alphanumeric characters and dashes (-).
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.40 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.40 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.
Cryptographic Services must be running for Director license activation.
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-40-1347.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.40.1347
  AgentInfoReports.exe – version 8.40.1347
  DBBackup.exe – version 8.40.1347
  MigrateSecondary.exe – version 8.40.1347
  QMCmd.exe – version 8.40.1347
  ReplService.exe – version 8.40.1347
  ReplVault.exe – version 8.40.1347
  SecondaryOp.exe – version 8.40.1347
  VVAnalyz.exe – version 8.40.1347
  VVArchive.exe – version 8.40.1347
  VVCopy.exe – version 8.40.1347
  VVExport.exe – version 8.40.1347
  VVImport.exe – version 8.40.1347
  VVListen.exe – version 8.40.1347
  VVMigrat.exe – version 8.40.1347
  VVMove.exe – version 8.40.1347
  VVPoolOp.exe – version 8.40.1347
  VVPurge.exe – version 8.40.1347
  VVQManager.exe – version 8.40.1347
  VVRecall.exe – version 8.40.1347
  VVServer.exe – version 8.40.1347
  VVSvrDae.exe – version 8.40.1347
  VVSvrMonitor.exe – version 8.40.1347
  Activation.dll – version 8.40.1347
  DailyStatusReport.dll – version 8.40.1347
  Evault.Synchweb.Bridge.dll – version 8.40.1347
  Evault.Synchweb.Data.dll – version 8.40.1347
  MigrateSecondaryManager.dll – version 8.40.1347
  PerfCounters.dll – version 8.40.1347
  Pool.dll – version 8.40.1347
  PoolManagement.dll – version 8.40.1347
  PoolManager.dll – version 8.40.1347
  PoolV5.dll – version 8.40.1347
  ReplicationTransport.dll – version 8.40.1347
  ReplPTCPXfer.dll – version 8.40.1347
  RetentionManager.dll – version 8.40.1347
  Shared.dll – version 8.40.1347
  SqlDbLib.dll – version 8.40.1347
  UNCStorage.dll – version 8.40.1347
  VaultHive.dll – version 8.40.1347
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.40.1347
  Activation.dll – version 8.40.1347
  PerfCounters.dll – version 8.40.1347
  Shared.dll – version 8.40.1347
  UpgradeDll.dll – version 8.40.1347
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.40.1347
  Activation.dll – version 8.40.1347
  Shared.dll – version 8.40.1347
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.40.1347
  Activation.dll – version 8.40.1347
  Shared.dll – version 8.40.1347
  SQLDbLib.dll – version 8.40.1347
  UNCStorage.dll – version 8.40.1347
3.5.2	SQL Server Express version
When you install a Director 8.40 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 only upgrade to Director 8.40 from Director 8.30. If a previous Director version is installed, you must upgrade to Director 8.30 before upgrading to version 8.40.
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 before upgrading Director to version 8.40. Director 8.40 is not supported with API – Monitoring 1.2.0.
If you upgrade a vault where Reporting service 8.30 is not installed, you can choose to install it during the upgrade.
If you upgrade a vault where Reporting service 8.30 is installed, the installer will upgrade the Reporting service to version 8.40. If the Reporting service is registered to API – Monitoring before the upgrade, the Reporting service remains registered to the API after the upgrade. 
4	FIXES and KNOWN ISSUES
4.1	Fixes
•	Some cases where Agents attempted to reconnect to vaults repeatedly after a network interruption have been addressed. (EV-25406, EV-23008)
•	When a vault is licensed for a specific amount of storage, the Reporting service now provides the correct Protected Storage usage amount to API – Monitoring. (EV-26511)
•	A vvmove operation now continues if it tries to move a file to a storage location where there is a file with the same name for the same task. If the files have matching CRC signatures, vvmove does not replace the existing file. If the files have different CRC signatures, vvmove chooses the file that is referenced by the pool system and saves the other file version with a “.duplicate” extension. (EV-14791)
•	Computer names in replication failure email notifications are now correct. (EV-25269)
•	After handling large files, Director no longer shows high RAM utilization. (EV-15865)
•	When Director is installed on Windows Server 2016 and has multiple UNC storage locations, Director processes do not fail because of storage access problems. (EV-21029)
•	Director vaults do not show performance degradation over time. (EV-19946)
•	When copying data at the customer or location level with the “I have both pool data files and meta information already in their respective locations and I only want to adjust the target files to the proper locations” option selected, the copy no longer fails with a “Please resolve all conflicts between location codes” message. (EV-16071)
•	Migratesecondary and cleanup operations no longer become deadlocked when they run on the same task. (EV-12763)
•	In most cases, when optimization is scheduled to run, the reported job sizes before and after optimization are the same as if optimization was run manually. (EV-17109)
•	CPU usage is no longer high in some cases when Director runs processes such as migrations and optimizations on large tasks. (EV-11748)
•	The CheckCRC process now runs significantly faster on large vaults. (EV-17876)
•	When copying data, the conflict detection screen is now updated if you go back and change the objects to be copied. (EV-12828)
•	Task names are no longer truncated by one character in the summary page for some wizards in the Director UI. (EV-14411)
•	In the Storage Usage Report, task details are not repeated in a line after tasks are migrated to secondary storage. (EV-13954)
•	The AgentInfoReport no longer scans for deleted detached storage locations. (EV-14158) 
•	Units of measure have been corrected for bandwidth usage in the Director UI. (EV-12650)
•	Host names now appear correctly in the Monitor service log. (EV-23337)
4.2	Known Issues
•	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 may become unresponsive and/or time out when you upgrade the vault to version 8.40. 
WORKAROUND: Upgrade API – Monitoring to version 1.3.0. Director 8.40 is not supported with API – Monitoring 1.2.0. (EV-26041)
•	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)