Carbonite Server Backup
Director
Version 8.30.1335
Release Notes, December 20, 2017
______________________________________________________________________
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
______________________________________________________________________
1	Overview
This document contains release notes for Director version 8.30. 
Director UI 8.30 is compatible with all supported Director versions. An earlier Director UI version cannot manage a later vault version.
Director 8.30 is supported with Vault API 8.30.
QuickShip (QSM) functionality has been discontinued in Director 8.30. You can use copy functionality to perform tasks that were previously supported using QSM vaults.
1.1	Release History
Version 8.30.1335, December 20, 2017
1.2	Supported Platforms
Director 8.30 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:
•	Platforms supported for Director 8.30 vaults (listed above)
•	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.30 vaults are supported on:
•	Windows Server 2016 Datacenter
•	Windows Server 2012 R2 Datacenter
For upgrades, Director 8.30 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.30 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
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.30 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.00h Satellite vaults to a Director 8.30 Base vault.
In one-to-one (1:1) replication, data can be replicated from:
•	a Director 8.30 Active vault to a Director 8.30 Passive vault. The vaults must have approximately the same storage capacity.
•	a Director 8.00h Active vault to a Director 8.30 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.00h Satellite vaults to a Director 8.30 Active Base vault.
•	A Director 8.30 Active Base vault to a Director 8.30 Passive Base vault.
•	A Director 8.00h Active Base vault to a Director 8.30 Passive Base vault. This replication configuration is supported for upgrade purposes only.
2	NEW FEATURES
•	Newly-installed Director 8.30 vaults only accept encrypted data. Vaults upgraded to version 8.30 continue to accept unencrypted backups for existing tasks. 
•	If a replication session is interrupted (e.g., due to power or network loss) before a safeset is completely replicated, the next replication session begins where the last session ended. Data that has already been replicated does not have to be sent again. To support this feature, Director 8.30 only replicates data using dual-stage replication.
Note: You cannot restore data from a partial safeset on a target vault. A safeset must be completely replicated before it can be restored from the target vault. 
•	Copy and clone operations which could cause data problems are now detected and prevented in the Director UI.
Note: The Director UI only detects data conflicts for copy and clone operations between Director 8.30 vaults. Copying and cloning data where the source or target vault is a pre- version 8.30 vault could still cause data problems.
•	Notepad is now the default program for opening log files.
•	Automatically-generated passwords for the VaultService account are now more complex.
•	An optional NoOnline parameter is available for silent installations. When specified, the installer will not request a transition of the node (vault) to Online when installation completes. When not specified, the system will automatically request transition to an Online state after a successful installation.
•	Inline replication is not used in Director 8.30.
3	INSTALLATION NOTES
3.1	System Requirements
RAM	Recommended: 16 GB or more. Minimum: 4 GB.	
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 must be running on systems running Director.
3.2	System Requirements in Microsoft Azure
You can install Director 8.30 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.30 on a VM in Azure, you must run the following command to specify an externally-available IP address or fully-qualified domain name (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-30-1335.exe
You can install vaults and the Director UI using this executable file. 
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.30.1335
  AgentInfoReports.exe – version 8.30.1335
  DBBackup.exe – version 8.30.1335
  MigrateSecondary.exe – version 8.30.1335
  QMCmd.exe – version 8.30.1335
  ReplService.exe – version 8.30.1335
  ReplVault.exe – version 8.30.1335
  SecondaryOp.exe – version 8.30.1335
  VVAnalyz.exe – version 8.30.1335
  VVArchive.exe – version 8.30.1335
  VVCopy.exe – version 8.30.1335
  VVExport.exe – version 8.30.1335
  VVImport.exe – version 8.30.1335
  VVListen.exe – version 8.30.1335
  VVMigrat.exe – version 8.30.1335
  VVMove.exe – version 8.30.1335
  VVPoolOp.exe – version 8.30.1335
  VVPurge.exe – version 8.30.1335
  VVQManager.exe – version 8.30.1335
  VVRecall.exe – version 8.30.1335
  VVServer.exe – version 8.30.1335
  VVSvrDae.exe – version 8.30.1335
  VVSvrMonitor.exe – version 8.30.1335
  Activation.dll – version 8.30.1335
  Evault.Synchweb.Bridge.dll – version 8.30.1335
  Evault.Synchweb.Data.dll – version 8.30.1335
  MigrateSecondaryManager.dll – version 8.30.1335
  PerfCounters.dll – version 8.30.1335
  Pool.dll – version 8.30.1335
  PoolManagement.dll – version 8.30.1335
  PoolManager.dll – version 8.30.1335
  PoolV5.dll – version 8.30.1335
  ReplicationTransport.dll – version 8.30.1335
  ReplPTCPXfer.dll – version 8.30.1335
  RetentionManager.dll – version 8.30.1335
  Shared.dll – version 8.30.1335
  SqlDbLib.dll – version 8.30.1335
  UNCStorage.dll – version 8.30.1335
  VaultHive.dll
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.30.1335
  Activation.dll – version 8.30.1335
  PerfCounters.dll – version 8.30.1335
  Shared.dll – version 8.30.1335
  UpgradeDll.dll – version 8.30.1335
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.30.1335
  Activation.dll – version 8.30.1335
  Shared.dll – version 8.30.1335
For installation information and instructions, see the Director Installation Guide.
3.5.2	SQL Server Express version
When you install a Director 8.30 vault, SQL Server Express 2014 Service Pack 2 (SP2) is installed for the vault database.
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 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 to Director 8.30 from Director 8.00h.
We recommend bringing a vault offline before an upgrade. For more information, see the Director Installation Guide.
Do not upgrade a vault to version 8.30 until any problems related to deferred backups (issue EV-6157) have been identified and sufficiently addressed. For more information, see documentation for the scan tool and fix tool provided for issue EV-6157.
3.5.5	Upgrade in Microsoft Azure
On a virtual machine (VM) in Microsoft Azure, you can upgrade from Director 8.00h to Director 8.30.
4	FIXES and Known issues
4.1	Fixes
•	Users with Sales level access to a vault can no longer take nodes offline or perform a failover to a Passive vault. (EV-15267/EV-15619)
•	The Director UI now blocks or warns about clone operations that could cause data problems. (EV-10232)
•	Replication from a Satellite vault to a Base vault no longer fails with the following error: Could not acquire the Task x Safesets ownership; they are still owned by thread y. (EV-9035)
•	Tasks are now marked as suspect when pool sync issues are detected. (EV-8910)
•	Replication no longer fails with the following error: Error committing partial pool: the ownership has already been obtained by thread. (EV-8793)
•	Optimize and ReplayTransactions processes finish without “Bad stream header start” messages. (EV-6187/EV-7823/33314)
•	Tasks are marked as suspect if “journal number mismatch” issues are detected. (EV-6181/33266/31611)
•	Vaults do not use excessive CPU resources when under heavy load. (EV-6178/33242)
•	Deduplication locks do not cause backups to fail. (EV-6169/EV-6158/EV-10523/33148)
•	Director prevents rare problems with deferred backups from a small subset of Agent versions. (EV-6157/EV-6152/32965) 
•	Replication no longer fails in some cases where there are unchanged blocks. (30890)
•	After a loss of storage connectivity, tasks are no longer flagged as suspect with the “.pf-map bad stream header start” message. (30751)
•	A Passive vault does not become "Unconfigured Active" and accept backups after an upgrade. (30934)
•	The vaultop start_services command does not hang when the SQL Server service is not running. (EV-11469)
•	The vaultop shutdown_vault command gracefully stops all active vault processes. (EV-11062)
•	The Director correctly checks whether .NET Framework 4.5 is installed on the system. (30985)
•	Replication no longer fails with the following error: Attempted to get non-existing safeset. (EV-7876/32814)
4.2	Known Issues
•	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)