Carbonite Server Backup
Director
Version 8.72.0308
Release Notes, June 6, 2024
______________________________________________________________________
Contents
1	Overview
1.1	Release History
1.2	Compatibility
1.3	Supported Platforms
1.4	Supported Platforms and Functionality in Microsoft Azure
1.5	Supported Agent Versions
1.6	Supported Vault Versions for Replication
2	NEW FEATURES
2.1	New Feature in Version 8.72
2.2	New Features in Version 8.70
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
© 2024 Open Text. 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.72. Director is an online data vault that securely receives, stores and manages backup data from servers where Server Backup agents are installed.
1.1	Release History
Version 8.72.0308, June 6, 2024
Version 8.70.0266, April 26, 2023
1.2	Compatibility
Director UI 8.72 is compatible with Director vault versions 8.72 and earlier. An earlier Director UI version cannot manage a later vault version.
Director 8.72 is supported with Vault API 8.72.
Encryption-at-rest components provided with Director 8.70 are supported with Director 8.72 vaults.
This Director version supports data deletion in response to requests from Carbonite Server 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 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. 
1.3	Supported Platforms
Director 8.72 vaults are supported on the following 64-bit platforms:
•	Windows Server 2022 Datacenter 1
•	Windows Server 2022 Standard 1
•	Windows Server 2019 Datacenter
•	Windows Server 2019 Standard
•	Windows Server 2016 Datacenter
•	Windows Server 2016 Standard
•	Windows Storage Server 2016
1	Director is not yet supported on Windows Server 2022 configured with secured-core security. 
 	Carbonite strongly recommends excluding Director storage locations from antivirus scanning. Unusual behavior, including file locking, can occur if Director storage locations are included in antivirus scanning.
The Director UI is supported on the following 64-bit platforms:
•	All platforms supported for Director 8.72 vaults (listed above)
•	Windows 11
•	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.4	Supported Platforms and Functionality in Microsoft Azure
In Microsoft Azure, Director 8.72 vaults are supported on Windows Server 2016 Datacenter.
The maximum supported storage size for a vault in Azure is 12 TB.
A Director 8.72 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 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. Director writes all data to the VM’s local disks.
1.5	Supported Agent Versions
Agent versions 9.xx, 8.xx, 7.xx and the latest supported 6.xx Agents can be used with Director 8.72 vaults.
1.6	Supported Vault Versions for Replication
Replication is supported from Director 8.7x, 8.62, 8.61 and 8.56 source vaults to Director 8.72 target vaults.
IMPORTANT: Director 8.60, 8.51, 8.50, 8.4x and 8.30 vaults are susceptible to a critical security issue. To safeguard your environment, we recommend upgrading these vaults as soon as possible. If you must replicate data from these vault versions to a Director 8.72 target vault, see the Director User Guide for more information. 
2	NEW FEATURES
2.1	New Feature in Version 8.72
Cache files to reduce the time required for some calculations
Data used in pool size calculations, in optimization, and by target vaults during replication can now be aggregated in pf map cache files. These cache files replace the block size cache files used in pool size calculations in Director 8.70.
For more information, including procedures for enabling and disabling pf map cache files in a vault, see the Director User Guide.
Security enhancements
Security has been improved in this Director version.
2.2	New Features in Version 8.70
IMPORTANT: A new port (12546) is used for replicating data between Director 8.70 and later vaults. Before upgrading vaults to Director 8.70 or later, be sure that replication source vaults (i.e., Satellite and Active vaults) can connect to replication target vaults (i.e., Base and Passive vaults) on port 12546. 
Certificate verification and pinning for vault-to-vault communications
To improve the security of vault-to-vault communications, vault certificates are now verified when a Director 8.70 or later source vault connects to a Director 8.70 or later target vault to replicate data, copy or clone data, or run a replication report. For the operation to proceed:
•	The source vault certificate must be within its validity period (i.e., not expired).
•	The target vault certificate must be within its validity period (i.e., not expired). 
•	If the target vault certificate is CA-signed: 
o	The subject name or subject alternative name of the target vault certificate must match the FQDN of the target vault server. If the target vault has a wildcard certificate, the domain name of the certificate must match the domain name of the target server.
o	The CA-signing authority certificate must be in the Trusted Root Certification Authorities store on both the source vault server and the target vault server. 
If the certificate verification fails, the source vault does not connect to the target vault and the replication, copy, clone or replication report fails. 
If the certificate verification passes and the target vault certificate is self-signed, the source vault pins the target vault’s certificate when it first connects to the target vault. When the source vault tries to connect to the target vault again, it checks whether the target vault certificate has changed. If the vault certificate has changed to another self-signed certificate, the source vault will not connect to the target vault unless you delete the pinned certificate from the source vault. If the vault certificate has changed to a CA-signed certificate that passes verification, the source vault will connect to the target vault without manual intervention.
If you replace the CA-signed certificate on a target vault with a self-signed certificate, a source vault will not connect to the target vault again unless you delete the recorded certificate from the source vault. 
IMPORTANT: Do not delete a pinned or recorded vault certificate unless you have determined that there is no security risk.
Certificate verification and pinning for vault-to-vault communications is always performed when the source and target vaults are version 8.70 or later. You do not have to manually enable this security feature. 
Note: Vault certificates are not verified or pinned when a Director version 8.6x or earlier vault connects to a Director 8.70 or later vault.
Longer validity periods for self-signed vault certificates
When you install a Director 8.70 or later vault or upgrade a vault from Director 8.56 or earlier to Director 8.70, a self-signed TLS certificate that is valid for 10 years is generated for the vault. 
The self-signed TLS certificate that was generated in Director 8.6x was valid for one year. When you upgrade a vault from version 8.6x and the original self-signed certificate is used for the vault, the certificate is regenerated with a 10-year validity period. The certificate’s public and private keys are preserved when the certificate is regenerated so that, if agent-certificate pinning is enabled on the vault, backups continue to function without interruption.
Certificate verification for importing a vault certificate
When you import a vault certificate using the vaultop import_certificate command, the certificate being imported is now verified. If the root certificate is not found on the vault server, the import fails. If another issue is found with the certificate (e.g., the certificate has expired), a warning appears in the log but the certificate is imported.
Email notification improvements
Email notifications are now supported with SMTP servers that require authentication, including private SMTP servers and cloud email service providers (e.g., Amazon Simple Email Service (SES), Google Gmail email service or Microsoft 365). Secure email protocols (StartTLS and SSL/TLS) are also supported.
You can configure email notifications using the Vault Settings dialog box or the VaultOp command.
Security enhancements
Security has been improved in this Director version.
3	Installation Notes
3.1	System Requirements
Disk space	Minimum 3 GB of installation disk space	
.NET Framework	.NET Framework 4.8 must be installed on the server.	
Ports	Ports for backups and replication must be configured on the server. For a list of required ports, see the Director Installation Guide. 
Note: A new port (12546) is used for replicating data between Director 8.70 or later vaults. This port is used instead of port 2547, which is used for replication in previous Director versions. After all source vaults have been upgraded to Director 8.70 or later, port 2547 can be closed at the firewall.	
Cryptographic services	Cryptographic Services must be running on systems running Director.	
3.2	System Requirements in Microsoft Azure
You can install Director 8.72 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
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 Director is installed. 	
.NET Framework	.NET Framework 4.8 must be installed on the VM.	
IP address	Static public IP address
After installing Director 8.72 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. Ports must also be opened in your local firewall to allow backups and replication to Azure. For a list of required ports, see the Director Installation guide. 
Note: A new port (12546) is used for replication between Director 8.70 vaults. This port is used instead of port 2547, which is used for replication in previous Director versions. After all source vaults have been upgraded to Director 8.70, port 2547 can be blocked.	
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-72-0308.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.72.0308
  AgentInfoReports.exe – version 8.72.0308
  DBBackup.exe – version 8.72.0308
  MigrateSecondary.exe – version 8.72.0308
  QMCmd.exe – version 8.72.0308
  ReplService.exe – version 8.72.0308
  ReplVault.exe – version 8.72.0308
  SecondaryOp.exe – version 8.72.0308
  VVAnalyz.exe – version 8.72.0308
  VVArchive.exe – version 8.72.0308
  VVCopy.exe – version 8.72.0308
  VVExport.exe – version 8.72.0308
  VVImport.exe – version 8.72.0308
  VVListen.exe – version 8.72.0308
  VVMigrat.exe – version 8.72.0308
  VVMove.exe – version 8.72.0308
  VVPoolOp.exe – version 8.72.0308
  VVPurge.exe – version 8.72.0308
  VVQManager.exe – version 8.72.0308
  VVRecall.exe – version 8.72.0308
  VVServer.exe – version 8.72.0308
  VVSvrDae.exe – version 8.72.0308
  VVSvrMonitor.exe – version 8.72.0308
  Activation.dll – version 8.72.0308
  DailyStatusReport.dll – version 8.72.0308
  Evault.Synchweb.Bridge.dll – version 8.72.0308
  Evault.Synchweb.Data.dll – version 8.72.0308
  MigrateSecondaryManager.dll – version 8.72.0308
  PerfCounters.dll – version 8.72.0308
  Pool.dll – version 8.72.0308
  PoolManagement.dll – version 8.72.0308
  PoolManager.dll – version 8.72.0308
  PoolV5.dll – version 8.72.0308
  ReplicationTransport.dll – version 8.72.0308
  ReplPTCPXfer.dll – version 8.72.0308
  RetentionManager.dll – version 8.72.0308
  Shared.dll – version 8.72.0308
  SqlDbLib.dll – version 8.72.0308
  UNCStorage.dll – version 8.72.0308
  VaultDbCfg.dll – version 8.72.0308
  VaultHive.dll – version 8.72.0308
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.72.0308
  Activation.dll – version 8.72.0308
  PerfCounters.dll – version 8.72.0308
  Shared.dll – version 8.72.0308
  UpgradeDll.dll – version 8.72.0308
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.72.0308
  Activation.dll – version 8.72.0308
  Shared.dll – version 8.72.0308
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.72.0308
  Activation.dll – version 8.72.0308
  Shared.dll – version 8.72.0308
  SQLDbLib.dll – version 8.72.0308
  UNCStorage.dll – version 8.72.0308
3.5.2	SQL Server Express version
When you install a Director 8.72 vault, SQL Server 2019 Express is installed as the vault database engine. Please keep this SQL Server instance updated with the latest security and critical updates from Microsoft.
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.3x or later to Director 8.72. 
A new port (12546) is used for replication between Director 8.70 or later vaults instead of port 2547, which is used for replication in previous Director versions. After all source vaults have been upgraded to Director 8.70 or later, port 2547 can be closed at the firewall.
We recommend bringing a vault offline before an upgrade. For more information, see the Director Installation Guide.
If you upgrade a vault where the Reporting service is installed, the installer will upgrade the Reporting service. If the Reporting service is registered to API – Monitoring before the upgrade, the Reporting service remains registered to the API after the upgrade. If you upgrade a vault where the Reporting service is not installed, you can choose to install it during the upgrade.
To silently upgrade Director to version 8.72 or silently install Director 8.72, you must first record a response file (.iss file) using the Director 8.72 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.72
•	To address issues where Director 8.70 installations or upgrades failed due to SQL Server upgrade issues, the Director 8.72 installer checks for inactive SQL Server instances and a C:\sqlExpress folder on a system during an installation or upgrade. If an inactive SQL Server instance is detected on the system, the user is prompted to contact Support for assistance to resolve the issue before trying the installation or upgrade again. If a C:\sqlExpress folder is detected on the system, the user is prompted to remove the folder before trying the installation or upgrade again. (EV-97871, EV-97581)
•	All Director executable files are now digitally signed. (EV-100203)
•	An issue has been addressed where the replication service sometimes crashed on Director 8.70 Base vaults that were under a heavy load. (EV-99677, EV-100201)
•	Block size cache files that were available in Director 8.70 have been replaced by pf map cache files. When you install a Director 8.72 vault, pf map cache files are not enabled by default but can be enabled using a new vault setting: UsePfMapCacheFile. If you upgrade a Director 8.70 vault where block size cache files are enabled, pf map cache files are automatically enabled after the upgrade to version 8.72. For more information, see the Director User Guide. (EV-98713, EV-98712, EV-97647) 
•	Read and write cache sizes have been increased for some files to improve storage efficiency when working with larger backups. (EV-100606)
•	An issue with TLS has been fixed on Windows Server 2016. (EV-99274)
•	The Missed Backup report no longer shows incorrect missed backups when multiple jobs are scheduled for an agent. (EV-97413, EV-26797)
4.1.2	Fixes in Version 8.70
•	To address an issue where agents could not connect to vaults because the vaults were busy with pool size recalculations:
o	The pool size is only recalculated once during optimization. In previous Director versions, pool sizes could be recalculated more than once during optimization. 
o	Block size data that is used in pool size calculations can now be held in cache files at the task level. Block size cache files use extra storage, but can significantly reduce the time required for pool size calculations during optimization, migration and replication. For more information, see the Director User Guide. 
(EV-90991)
•	An issue has been addressed where, if two customers on a vault had the same name, a computer could be cloned to the wrong customer. (EV-92873)
•	An issue has been addressed so that ransomware threat information for a task is transferred correctly when the task is copied, replicated, or migrated to secondary storage. (EV-95323, EV-94544)
•	An issue has been addressed where a safeset was incorrectly deleted from a Satellite vault after it was copied to a standalone vault. (EV-85127, EV-85459)
•	On the License Summary tab in the Vault Settings dialog box, the Current Usage and Licensed For vault size values are now rounded to three decimal places and are both measured in the same unit (MB, GB, TB or PB). Previously, only whole numbers were shown and different units were sometimes used, making it difficult to understand pool size warnings that appeared. (EV-63891)
•	When data deletion requests are submitted for objects that no longer exist on the vault, MigrateDelete.GUID files are automatically deleted from the <DirectorInstallation>\conf folder. Previously, MigrateDelete.GUID files remained in the …\conf folder.
Note: MigrateDelete.GUID files that were created by previous Director versions might remain in the <DirectorInstallation>\conf folder. You must delete these files manually. For assistance, please contact Support. (EV-49084)
4.2	Known Issues
•	After you replace a Satellite vault, if data is not completely replicated from the Base vault to the Satellite vault, the first backup to the Satellite vault could create Safeset #1 even though there are safesets on the Base vault.
WORKAROUND: After you replace or install a Satellite vault, be sure that data has been completely replicated from the Base vault to the Satellite vault before running backup jobs. (EV-97884)
•	If the certificate chain for a replication target vault (i.e., Base or Passive vault) is incomplete, metadata might be replicated but data replication and copy/clone operations fail.
WORKAROUND: Ensure that all vault certificate chain elements are available in the local machine certificate store. Do not add the certificates to user certificate stores. 
Note: When the certificate chain for a target vault is incomplete, warning messages appear in the ReplService log at startup. (EV-89090)
•	If vault servers have an external network connection and a local network connection, and a CA-signed certificate for the external network is used on the vaults, copy-clone operations between Director 8.70 vaults do not work over the local network. 
WORKAROUND: Use an Alternative DNS Name on the certificate so that copy/clone operations succeed. If this is not possible, use the vaultop update_node_in_cluster command to specify the external address and internal address for the vault. The domain name of the external address on the vault will then be used for certificate validation. (EV-91538)
•	In rare cases when you try to upgrade Director from version 8.50 or earlier, the upgrade fails with a ‘JSON_VALUE' is not a recognized built-in function name message and the installation does not roll back successfully. If this occurs, please contact Support for assistance. (EV-77815, EV-79590)
•	The Director UI allows you to copy data from a source vault that has the same major and minor version but a later patch version than the target vault (e.g., from a version 8.62 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.70 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.70 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)