Carbonite Server Backup
Director
Version 8.61.0074
Release Notes, January 11, 2022
______________________________________________________________________
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
2.1	New Feature in Version 8.61
2.2	New Features in Version 8.60
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. 2021.  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.61. Director is an online data vault that securely receives, stores and manages backup data from servers where Server Backup agents are installed.
IMPORTANT: A critical security issue is addressed in Director 8.61. We strongly recommend upgrading all vaults to Director 8.61.
Director UI 8.61 is compatible with Director vault versions 8.61, 8.60 and 8.5x.
Director 8.61 is supported with Vault API 8.61.
This Director version supports data deletion in response to requests from Carbonite Server Backup Portal. For data deletion, install the Reporting service with each standalone, Base and Active vault and register the Reporting service to the same Carbonite Server Backup API – Monitoring instance (version 1.50 or later) as Portal 8.87 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.61.0074, December 21, 2021
Version 8.60.2257, August 20, 2021
1.2	Supported Platforms
Director 8.61 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
The Director UI is supported on the following 64-bit platforms:
•	All platforms supported for Director 8.61 vaults (listed above) and:
•	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.61 vaults are supported on:
•	Windows Server 2016 Datacenter
•	Windows Server 2012 R2 Datacenter
For upgrades in Azure, Director 8.61 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.61 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.61 vaults.
1.5	Supported Vault Versions for Replication
Replication is supported from Director 8.61 source vaults to Director 8.61 target vaults.
For a limited time, replication will be supported from Director 8.60, 8.5x, 8.4x and 8.30 source vaults to target vaults that are upgraded to Director 8.61. Replication between these vault versions will be automatically disabled by May 31, 2022. Although it is not recommended, you can change this cutoff date. For more information, see New Feature in Version 8.61.
Replication is not supported from Director 8.60, 8.5x, 8.4x or 8.30 source vaults to newly-installed Director 8.61 target vaults. 
Note: If you must replicate data from earlier vault versions to Director 8.61 vaults, please contact Support.
The following table lists the Director versions that are supported in many-to-one (N:1), one-to-one (1:1) and many-to-one-to-one (N:1:1) replication.
Replication scenario	Supported	Supported for a limited time (automatically disabled by May 31, 2022, by default)	
Many-to-one (N:1)	Replication from Director 8.61 Satellite vaults to a Director 8.61 Base vault	Replication from Director 8.60, 8.5x, 8.4x and 8.30 Satellite vaults to a Base vault that is upgraded to version 8.61*	
One-to-one (1:1)	Replication from a Director 8.61 Active vault to a Director 8.61 Passive vault. The vaults must have approximately the same storage capacity.	Replication from a Director 8.60, 8.5x, 8.4x or 8.30 Active vault to a Passive vault that is upgraded to Director 8.61*	
Many-to-one-to-one (N:1:1)	Replication from Director 8.61 Satellite vaults to a Director 8.61 Active Base vault	Replication from Director 8.60, 8.5x, 8.4x and 8.30 Satellite vaults to an Active Base vault that is upgraded to Director 8.61*	
	Replication from a Director 8.61 Active Base vault to a Director 8.61 Passive Base vault. The vaults must have approximately the same storage capacity.	Replication from a Director 8.60, 8.5x, 8.4x or 8.30 Active vault to a Passive Base vault that is upgraded to Director 8.61*	
Note: Replication is not supported from Director 8.60, 8.5x, 8.4x or 8.30 source vaults to newly-installed Director 8.61 target vaults.	
2	NEW FEATURES
2.1	New Feature in Version 8.61
Critical security fix
A critical security issue is addressed in Director 8.61. A vault is susceptible to the security issue if it has not been upgraded to Director 8.61, or if it receives replicated data from a vault that has not been upgraded to Director 8.61. We strongly recommend upgrading all vaults to Director 8.61.
When you first upgrade a replication target vault (e.g., Base vault or Passive vault) to Director 8.61, data can be replicated from Director 8.60, 8.5x, 8.4x and 8.30 source vaults (e.g., Satellite vaults or Active vault). To ensure that your servers are secure, replication from these vault versions to the Director 8.61 target vault will be automatically disabled:
•	when only Director 8.61 vaults are replicating to the target vault. This can occur:
o	In a Passive vault when the Active vault has been upgraded to Director 8.61.
o	In a Passive Base vault when the Active Base vault has been upgraded to Director 8.61.
o	In a Base vault or Active Base vault when Satellite vaults have been upgraded to Director 8.61 and/or replication has not occurred from Director 8.60, 8.5x, 8.4x or 8.30 Satellite vaults for 60 days.
•	on May 31, 2022, if it was not disabled earlier. Although it is not recommended, you can change this cutoff date. For more information, see the Director User Guide.  
After replication from Director 8.60, 8.5x, 8.4x and 8.30 source vaults is disabled in a target vault, only Director 8.61 vaults can register to or replicate data to the target vault. When you upgrade source vaults to version 8.61, replication resumes.
Replication is not supported from Director 8.60, 8.5x, 8.4x or 8.30 source vaults to newly-installed Director 8.61 target vaults. 
Note: If you must replicate data from earlier vault versions to Director 8.61 vaults, please contact Support.
2.2	New Features in Version 8.60
Support for hourly backups
Beginning with Windows Agent 8.90 and Linux Agent 8.90, backups to a Director 8.6x vault can be scheduled to run hourly or multiple times per day using Portal 8.88 or later. 
To ensure that replication and maintenance processes run on tasks with intra-daily backups, the following changes have been made:
•	Backup load management. Beginning with Windows Agent 8.90 and Linux Agent 8.90, when an agent contacts a vault to start a backup, Director now indicates whether the vault is busy with high-priority maintenance for the task. High-priority maintenance includes operations that identify and remove expired safesets from the vault.
If the vault is busy and the backup is scheduled by an intra-daily schedule, the agent skips the backup. 
If the vault is busy and the backup is scheduled to run daily, weekly or monthly or is an ad hoc backup (i.e., not scheduled), the backup starts when the maintenance is finished. 
Note: Beginning with Windows Agent 8.72 and Linux Agent 8.90, if a backup job is scheduled to run more than once daily by one schedule, and a backup is already running for the job the agent skips the incoming backup. In this case, the backup is skipped before the agent contacts Director.
•	Replication load management and deferral. If a target vault is busy with high-priority maintenance for a task and data for the task was replicated successfully within the past 12 hours, incoming replication for the task is deferred for 30 minutes and then retries. If replication for a task has been deferred for more than 12 hours, the incoming replication is performed immediately without checking whether the vault is busy. 
Replication for a task is also delayed or deferred if:
•	Outbound replication is triggered by a backup or incoming replication but maintenance has not run successfully on the task in the past 24 hours and successful outbound replication has run in the past 24 hours.
•	Replication for a task fails (e.g., due to network failure). If this occurs, the replication is deferred for 5 minutes and then retries multiple times. 
•	Triggered maintenance and replication. Some maintenance and replication operations are now triggered to run when another operation finishes.
On a vault where maintenance is enabled, if ‘vvpoolop optimize’ did not run successfully on a task in the past 12 hours, ‘vvpoolop optimize’ is triggered for the task after:
•	A successful backup for the task finishes.
•	Incoming replication for the task finishes, even if it does not finish successfully. 
On a vault which is set to replicate data as soon as possible after changes are made, outbound replication for a task is triggered after:
•	A successful backup for the task finishes and pool optimization is not triggered. 
•	Incoming replication for the task finishes, even if it does not finish successfully, and pool optimization is not triggered. 
•	‘vvpoolop optimize’ for the task finishes, regardless of whether it was triggered by a backup or incoming replication or not.
•	Streamlined processes. To ensure that replication and maintenance processes run on tasks with intra-daily backups, the following changes have been made in Director 8.60:
•	When more than one safeset is replicated in the same replication session, Director now verifies only the last safeset that is replicated. In previous versions, Director verified every safeset on the target vault and the same data could be verified multiple times.
•	When more than one safeset is replicated in the same replication session, Director now collects information for each data block once during the session. In previous versions, Director sometimes collected information multiple times for the same data blocks.
•	If a replication session lasts longer than 24 hours, it is ended when the safeset that is being replicated at the 24-hour point is finished. A new replication session will be started a short time later. This allows the replication to apply retention settings to the remaining safesets and, if necessary, run maintenance on the source or target vault.
For more information about changes to support hourly backups, see the Director User Guide.
Vault certificate management and certificate pinning
When you install a Director 8.6x vault or upgrade a vault to version 8.6x, a self-signed TLS certificate is generated for the vault. 
You can replace the generated vault certificate with a certificate of your choice. The certificate can be another self-signed certificate or a certificate from an enterprise or commercial Certificate Authority (CA). 
The vault certificate is used in certificate pinning, which can be enabled in Director 8.6x and used in agent-vault certificate pinning. This security feature is designed to prevent attackers from redirecting network traffic intended for legitimate vaults to servers under their control. This mechanism is available beginning with Windows Agent 8.90, Linux Agent 8.90, vSphere Recovery Agent 8.87 and Hyper-V Agent 9.00. 
IMPORTANT: Do not enable certificate pinning in a vault until the intended vault certificate is installed. If you enable this feature and then import a certificate with a different public key, agents that have pinned the certificate will not connect to the vault until the certificate failure is resolved.
For more information about vault certificate management and certificate pinning, see the Director Installation Guide and the Server Backup online help.
Vault services quiesced before a system shutdown
Before a system shutdown or restart, Director services and processes are now quiesced to ensure that data is committed in a consistent state. Vault services and running processes, such as backups and restores, now have ten minutes to stop gracefully before a system shutdown. 
Note: If a system restart happens during a pool file update, some temporary files might not be deleted until the next time cleanup runs.
Security enhancements
Security has been improved in this Director version. Director uses TLS and strong ciphers to ensure secure communications. 
3	Installation Notes
3.1	System Requirements
Disk space	Minimum 3 GB of installation disk space	
Required software	Microsoft .NET Framework 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.61 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 4.5	
IP address	Static public IP address
After installing Director 8.61 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-61-0074.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.61.0074
  AgentInfoReports.exe – version 8.61.0074
  DBBackup.exe – version 8.61.0074
  MigrateSecondary.exe – version 8.61.0074
  QMCmd.exe – version 8.61.0074
  ReplService.exe – version 8.61.0074
  ReplVault.exe – version 8.61.0074
  SecondaryOp.exe – version 8.61.0074
  VVAnalyz.exe – version 8.61.0074
  VVArchive.exe – version 8.61.0074
  VVCopy.exe – version 8.61.0074
  VVExport.exe – version 8.61.0074
  VVImport.exe – version 8.61.0074
  VVListen.exe – version 8.61.0074
  VVMigrat.exe – version 8.61.0074
  VVMove.exe – version 8.61.0074
  VVPoolOp.exe – version 8.61.0074
  VVPurge.exe – version 8.61.0074
  VVQManager.exe – version 8.61.0074
  VVRecall.exe – version 8.61.0074
  VVServer.exe – version 8.61.0074
  VVSvrDae.exe – version 8.61.0074
  VVSvrMonitor.exe – version 8.61.0074
  Activation.dll – version 8.61.0074
  DailyStatusReport.dll – version 8.61.0074
  Evault.Synchweb.Bridge.dll – version 8.61.0074
  Evault.Synchweb.Data.dll – version 8.61.0074
  MigrateSecondaryManager.dll – version 8.61.0074
  PerfCounters.dll – version 8.61.0074
  Pool.dll – version 8.61.0074
  PoolManagement.dll – version 8.61.0074
  PoolManager.dll – version 8.61.0074
  PoolV5.dll – version 8.61.0074
  ReplicationTransport.dll – version 8.61.0074
  ReplPTCPXfer.dll – version 8.61.0074
  RetentionManager.dll – version 8.61.0074
  Shared.dll – version 8.61.0074
  SqlDbLib.dll – version 8.61.0074
  UNCStorage.dll – version 8.61.0074
  VaultDbCfg.dll – version 8.61.0074
  VaultHive.dll – version 8.61.0074
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.61.0074
  Activation.dll – version 8.61.0074
  PerfCounters.dll – version 8.61.0074
  Shared.dll – version 8.61.0074
  UpgradeDll.dll – version 8.61.0074
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.61.0074
  Activation.dll – version 8.61.0074
  Shared.dll – version 8.61.0074
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.61.0074
  Activation.dll – version 8.61.0074
  Shared.dll – version 8.61.0074
  SQLDbLib.dll – version 8.61.0074
  UNCStorage.dll – version 8.61.0074
3.5.2	SQL Server Express version
When you install a Director 8.61 vault, SQL Server 2017 Express 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 to Director 8.61 from Director 8.60, 8.5x, 8.4x and 8.30. If a previous Director version is installed, you must upgrade to Director 8.30 before upgrading to version 8.61.
IMPORTANT: When you upgrade a vault from Director 8.50 or an earlier version, the vault database engine is upgraded to SQL Server 2017 Express. A reboot may be required to complete the SQL Server upgrade procedure. Please plan your upgrade accordingly. 
IMPORTANT: You cannot upgrade a Director vault to version 8.61 on Windows Server 2008 R2. You must upgrade the operating system to a supported version before you can upgrade the vault to version 8.61.
We recommend bringing a vault offline before an upgrade. For more information, see the Director Installation Guide.
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.61. If the Reporting service is registered to API – Monitoring before the upgrade, the Reporting service remains registered to the API after the upgrade. 
To silently upgrade Director to version 8.61 or silently install Director 8.61, you must first record a response file (.iss file) using the Director 8.61 installation kit. You cannot use a response file created with a previous Director version. For instructions, see the Director Installation Guide.
4	FIXES and KNOWN ISSUES
4.1	Fixes
4.1.1	Fixes in Version 8.61
•	Clone (Safeset by Safeset) operations no longer stop after 24 hours. In Director 8.60, when Clone (Safeset by Safeset) was used to copy a large amount of data, the operation stopped after the safeset that was being copied at the 24-hour point was finished. (EV-74012)
•	An issue has been addressed where, in some cases on vaults with frequent backups, vault processes did not exit properly and .dmp files were created on the Windows volume (typically C:). (EV-71062, EV-70945)
•	An issue has been addressed where, in Director 8.60, ssiverall stopped running when it found a problem with a safeset and did not check the remaining safesets in the pool. (EV-70276)
4.1.2	Fixes in Version 8.60
•	An issue has been addressed where a task was marked as suspect on a Base vault because CRC errors were found during replication, but the task was not marked as suspect on the Satellite vault. (EV-51379)
•	Before cleaning up files after a backup is cancelled or interrupted, Director now only verifies safesets if the interruption occurred while safesets were being committed. In previous versions, Director always verified safesets after an interruption even though verification is only necessary if the backup is interrupted during the commit process when files could be between states. (EV-41854, EV-47313)
•	An issue has been addressed where, after Director lost communication with a storage location, backup jobs did not resume automatically. Backups now end with an error if Director loses communication with a storage location, and subsequent backups continue automatically. (EV-40038)
•	An issue has been addressed where replication sessions got “stuck” after a network interruption, and did not proceed or stop unless replication services were disabled and re-enabled. (EV-63680, EV-52000)
•	An issue has been addressed where, in some cases, vault operations such as backups, restores and replications failed when metadata files (e.g., synch.*, poolsync.*, poolfiles.*) were distributed across UNC locations. (EV-58440, EV-57184)
•	An issue has been addressed where, after you started the Director UI, the first log file that you opened took a minute or longer to load. (EV-53308)
•	An issue has been addressed where tasks were not locked correctly during Director operations and were sometimes marked as suspect. (EV-52019)
•	An issue has been addressed where long-running vault-wide maintenance processes missed the same tasks each day. (EV-47956, EV-47695)
•	An issue has been addressed where, after an operation failed because of insufficient disk space, a subsequent operation failed with the following error: The process cannot access the file because it is being used by another process. (EV-46585, EV-46221)
•	When identifying and deleting unused pool files, optimization processes now check for incoming backups. This prevents incoming backup requests from timing out while optimization processes are running. (EV-41250, EV-35932)
•	An issue has been addressed where, in an N:1:1 replication environment, locking errors occurred when the genoptidxv5 command tried to run after data was replicated to the Active Base vault. (EV-40720, EV-40687)
•	Changes have been made to improve the performance of the replvault diff vault 
-diffmethod=IDX command. (EV-38452, EV-36314)
•	An issue has been addressed where the wrong customer was sometimes selected if you copied or cloned a customer using the Storage Management > Copy command in the Director UI. (EV-25174)
•	An issue has been addressed where the Director UI could not connect to a vault using credentials in a trusted domain. (EV-22083) 
•	An issue has been addressed where deduplication did not always run when the threshold for deduplication was reached. (EV-41684) 
•	When ssifixone or ssifixall fixes a corrupted file, the correct filename now appears in the log. Previously, the log showed the wrong file name or did not show any file name. (EV-40498)
•	An issue was addressed where, in some cases, the Reporting service was not uninstalled when you uninstalled Director 8.50. (EV-33802)
•	An issue with the vvmigrat command has been fixed. The vvmigrat command now works with the noninterruptible switch. (EV-16024)
4.2	Known Issues
•	The Director 8.61 UI allows you to copy data from a version 8.61 vault to a version 8.60 vault, even though this operation is not supported. The log does not indicate that the operation fails because of incompatible vault versions. Client closed connection, Client was unable to send message, and Error while getting node information messages appear in the log. (EV-73729)
•	A Replication Comparison report fails if you try to run the report from a Director 8.61 Passive vault that receives replicated data from a Director 8.60 or earlier Active vault. 
WORKAROUND: Run the replication comparison report from the Active vault, or upgrade the Active vault to Director 8.61 before running the report. (EV-73549)
•	Replication fails when a partial safeset on the target vault has been deleted from the source vault. The replication log on the target vault includes the following message: Error sending the source tree to the target: Attempted to get non-existing safeset #safesetNumber from the sync list. 
WORKAROUND: Delete the partial safeset from the target vault by running the following command: vvmigrat delete taskNumber safesetNumber /partial-safesets
Obtain the task number by viewing the task’s properties in the Director UI. Obtain the safeset number from the error message shown above. (EV-60241)
•	After a Director upgrade, data is missing from the Storage Pool Summary report. 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 the Monitor service goes offline, the Listener service goes offline. However, if the Monitor service restarts, the Listener service does not always restart.
WORKAROUND: Restart the Listener service after the Monitor service is restarted. (EV-23275)
•	In an N:1:1 replication setup where two customer short names start with the same 18 characters, you cannot fail over from the Active Base vault to the Passive Base vault.
WORKAROUND: Make sure that the first 18 characters of each customer short name is unique. (EV-21342)
•	Scheduled Replication Lag reports are not sent when email addresses are separated by spaces in addition to commas.
WORKAROUND: When you schedule a Replication Lag report to send to multiple email addresses, separate the email addresses with commas only. Do not add spaces between email addresses. (EV-53406)
•	When you try to clone data to a vault where the hostname is longer than 15 characters, authentication errors can occur. 
WORKAROUND: Ensure that vault server hostnames are no longer than 15 characters. (EV-35437)
•	After you copy an agent to another location on the same vault, backups could fail. For assistance, please contact Support. (EV-21047)
•	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)