EVault Software
Director
Version 8.00.7420h
Release Notes, July 18, 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 Director Management Console Only
3.4	Licensing
3.5	Install/Uninstall/Upgrade
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.00h.
Director 8.00h Management Console is compatible with all supported, generally-available Director versions. An earlier Director Management Console version cannot manage a later vault version.
Director 8.00h vaults are installed with SQL Server Express 2014 Service Pack 2 (SP2) for the vault database.
Director 8.00h is supported with Vault API 8.00.
For supported Agent versions, see Section 1.4. For supported vault versions for replication, see Section 1.5.
Vault Backup Agent is not supported with Director 8.00h.
1.1	Release History
Version 8.00.7420h, July 18, 2017
Version 8.00.7411f, March 16, 2017
Version 8.00.7404e, February 1, 2016 (for Azure only)
Version 8.00.7402d, June 20, 2016
Version 8.00.7383c, November 16, 2015
Version 8.00.7378b, October 8, 2015
1.2	Supported Platforms
Director 8.00h vaults are supported on the following 64-bit platforms:
·	Windows Server 2012 R2 Datacenter
·	Windows Server 2012 R2 Standard
·	Windows Server 2008 R2 Datacenter (SP1)
·	Windows Server 2008 R2 Enterprise (SP1)
·	Windows Server 2008 R2 Standard (SP1)
For EVault-provided appliances only, Director 8.00h vaults are supported on Windows Storage Server 2012 R2.
Director Management Console is supported on the following 64-bit platforms:
·	Platforms supported for Director 8.00h vaults (listed above)
·	Windows 7 Ultimate (SP1)
·	Windows 7 Professional (SP1)
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.00h is supported on Microsoft Windows Server 2012 R2 Datacenter. For upgrades from version 7.11e, Director 8.00h is also supported on Microsoft Windows Server 2012 R2 Standard.
The maximum supported size for a vault in Azure is 12 TB.
A Director 8.00h vault in Microsoft Azure is supported as:
·	a standalone vault that receives backup data directly from Agents.
·	a Passive vault in 1:1 replication. A Director 8.00h Active vault can replicate data to a Director 8.00h Passive vault in Azure.
·	a Base vault in N:1 replication. Director 8.00h, 8.00f and 8.00d Satellite vaults can replicate data to a Director 8.00h Base vault in Azure. 
After installing Director 8.00h 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.
When Director is installed on a VM in Azure, the following components and functionality are not supported:
·	Secondary and archive storage
·	QSM vaults
·	EVault 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 version can be used with Director 8.00h  vaults.
1.5	Supported Vault Versions for Replication
In many-to-one (N:1) replication, data can be replicated from Director 8.00h, 8.00f, 8.00d and 7.11e Satellite vaults to a Director 8.00h, 8.00f or 8.00d Base vault. We recommend upgrading Satellite vaults to version 8.00h. 
Note: Data can be replicated from Director 8.00h, 8.00f and 8.00d Satellite vaults to a Director 8.00h, 8.00f or 8.00e Base vault in Microsoft Azure. We recommend upgrading Satellite vaults to version 8.00h.
In one-to-one (1:1) replication, data can be replicated from: 
·	a Director 8.00h, 8.00f or 8.00d Active vault to a Director 8.00h, 8.00f or 8.00d Passive vault. The vaults must have approximately the same storage capacity. 
·	a Director 7.11e Active vault to a Director 8.00h, 8.00f or 8.00d Passive vault. This replication configuration is supported for upgrade purposes only. Failover is only supported in this case if the Active vault is unavailable. After a failover, you can only fail back to the original Active vault after it is upgraded to version 8.00h.
Note: Data can be replicated from a Director 8.00h Active vault to a Director 8.00h Passive vault in Microsoft Azure.
In many-to-one-to-one (N:1:1) replication, data can be replicated from:
·	Director 8.00h, 8.00f, 8.00d and 7.11e Satellite vaults to a Director 8.00h, 8.00f or 8.00d Active Base vault.
·	a Director 8.00h, 8.00f or 8.00d Active Base vault to a Director 8.00h, 8.00f or 8.00d Passive Base vault. The vaults must have approximately the same storage capacity. 
·	a Director 7.11e Active Base vault to a Director 8.00h, 8.00f or 8.00d Passive Base vault. This replication configuration is supported for upgrade purposes only. Failover to the Passive Base vault is only supported if the Active Base vault is unavailable. After a failover, you can only fail back to the original Active Base vault after it is upgraded to version 8.00h.
______________________________________________________________________
Important: When data is replicated from a Director 7.11e vault to a Director 8.00h vault, the following problems can occur with Agent versions 7.5 and earlier:
·	RPC errors can appear in backup logs, but the integrity of the data is not affected. 
·	Backups can fail when a Satellite vault is in Bypass Satellite mode.
·	Restores can fail. 
To avoid these issues, do one of the following:
·	Upgrade all vaults to version 8.00h.
·	Upgrade Agents to version 8.10 or later, where available. 
______________________________________________________________________
2	NEW FEATURES
The performance of backups, restores and replication has been improved. For best backup and restore performance, Agent version 8.xx is required.
3	INSTALLATION NOTES
3.1	System Requirements
The following table lists system requirements for Director 8.00h vaults.
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.00h 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 2012 R2 Datacenter
Windows Server 2012 R2 Standard (for upgrades from Director 7.11e)
Note: The 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.00h 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 Director Management Console 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 Director Management Console.
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
3.5.1	Install
The Director installation kit file name is: InfoStageDirector-8-00-7420h.exe
This executable file contains all components necessary to install vaults and Director Management Console. 
The following 64-bit vault application files are installed in the Director programs installation directory (Default location: C:\Program Files\EVault\InfoStage\Director\prog):
  AdminService.exe – version 8.00.7416
  AgentInfoReports.exe – version 8.00.7416
  DBBackup.exe – version 8.00.7416
  MigrateSecondary.exe – version 8.00.7416
  QMCmd.exe – version 8.00.7416
  QSM.exe – version 8.00.7416
  ReplService.exe – version 8.00.7416
  ReplVault.exe – version 8.00.7416
  SecondaryOp.exe – version 8.00.7416
  VVAnalyz.exe – version 8.00.7416
  VVArchive.exe – version 8.00.7416
  VVCopy.exe – version 8.00.7416
  VVExport.exe – version 8.00.7416
  VVImport.exe – version 8.00.7416
  VVListen.exe – version 8.00.7416
  VVMigrat.exe – version 8.00.7416
  VVMove.exe – version 8.00.7416
  VVPoolOp.exe – version 8.00.7416
  VVPurge.exe – version 8.00.7416
  VVQManager.exe – version 8.00.7416
  VVRecall.exe – version 8.00.7416
  VVServer.exe – version 8.00.7420
  VVSvrDae.exe – version 8.00.7416
  VVSvrMonitor.exe – version 8.00.7416
  Activation.dll – version 8.00.7416
  BackupDLL.dll – version 8.00.7416
  Evault.Synchweb.Bridge.dll – version 8.00.7416
  Evault.Synchweb.Data.dll – version 8.00.7416
  MigrateSecondaryManager.dll – version 8.00.7416
  PerfCounters.dll – version 8.00.7416
  Pool.dll – version 8.00.7416
  PoolManagement.dll – version 8.00.7416
  PoolManager.dll – version 8.00.7416
  PoolV5.dll – version 8.00.7416
  ReplicationTransport.dll – version 8.00.7416
  ReplPTCPXfer.dll – version 8.00.7416
  RetentionManager.dll – version 8.00.7416
  Shared.dll – version 8.00.7416
  SqlDbLib.dll – version 8.00.7416
  UNCStorage.dll – version 8.00.7416
  VaultHive.dll
The following 64-bit files are installed in the Director utilities installation directory (Default location: C:\Program Files\EVault\InfoStage\Director\Utils):
  VaultOp.exe – version 8.00.7416
  Activation.dll – version 8.00.7416
  PerfCounters.dll – version 8.00.7416
  Shared.dll – version 8.00.7416
  UpgradeDll.dll – version 8.00.7416
The following 32-bit files are installed in the Director Management Console installation directory (Default location: C:\Program Files(x86)\EVault\InfoStage\Director\Admin):
  VMAdmin.exe – version 8.00.7416
  Shared.dll – version 8.00.7416
  Activation.dll – version 8.00.7416
For installation information and instructions, see the Director Installation Guide.
3.5.2	SQL Server Express version
When you install a Director 8.00h vault, SQL Server Express 2014 SP2 is installed for the vault database.
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.
If Director was upgraded from version 7.11d or 7.11e, a SQL Server 2008 R2 Express (x86) instance named EVAULT_DB might remain on the system after you uninstall Director 8.00h. You can safely uninstall the SQL Server 2008 R2 Express (x86) instance.
3.5.4	Upgrade
You can upgrade to Director 8.00h from Director 8.00f, 8.00d, 7.11e or 7.11d.
A pre-upgrade validation script is available for Director 7.11 that checks for prerequisites for upgrading to version 8.00x. We recommend running this script on the Director server before upgrading from Director 7.11e or 7.11d to Director 8.00h.
Director installations earlier than version 7.11d must be upgraded to version 7.11d or 7.11e before they can be upgraded to version 8.00h.
During an upgrade from Director 8.00d, SQL Server Express 2014 is upgraded to SQL Server Express 2014 SP2.
During an upgrade from Director 7.11d or 7.11e, a SQL Server Express 2014 SP2 instance named EVAULT_DB_V800 is installed for the Director 8.00h vault database. After a successful upgrade, you can uninstall the SQL Server 2008 R2 Express (x86) instance named EVAULT_DB. This instance was used with Director 7.11. 
3.5.5	Upgrade in Microsoft Azure
On a virtual machine (VM) in Microsoft Azure, you can upgrade to Director 8.00h from Director 8.00f, 8.00e or 7.11e.
A pre-upgrade validation script is available for Director 7.11 that checks for prerequisites for upgrading to version 8.00x. We recommend running this script on the Director virtual machine before upgrading from Director 7.11e to Director 8.00h.
4	FIXES and KNOWN ISSUES
4.1	Fixes
4.1.1	Fixes in Version 8.00h
·	Director now prevents rare problems with deferred backups from a small subset of Agent versions. (EV-6157)
·	When deduplication is running on a task, a backup can interrupt any deduplication process and run successfully. (EV-6169)
·	When you run the agentinforeports command, data is correct in the resulting DatatypeReport.CSV file. (EV-8581)
4.1.2	Fixes in Version 8.00f
·	Data security improvements have been made, including using SHA-2 for communication between Director components. (32976)
·	In N:1 replication, if a Satellite vault is replaced or a job is reseeded on a Satellite vault, the job is no longer reseeded to the Base vault. (32941)
·	In 1:1 replication, the replication service on the Passive vault no longer hangs and refuses subsequent replication traffic. (32773, 32543)
·	Backups no longer fail with a “Failed to obtain safeset locks” error in rare cases when deduplication is running. (32266)
4.1.3	Fixes in Version 8.00e
·	A “Sharing Violation” error no longer occurs when Director tries to rename the poolfiles.dat.new or poolfiles.names.new file. (32369)
·	Backups and replication no longer fail with a “journal number mismatch” error. (31611)
·	Director upgrades from 7.11 now succeed when a SQL Server instance named EVAULT_DB_V800 is already installed. (32226)
4.1.4	Fixes in Version 8.00d
·	Replication from a Satellite vault to a Base vault, or from an Active vault to a Passive vault, now succeeds when Windows Update KB 3142033 is applied on the source vault server. (31781)
·	Replication sessions no longer fail because of references to deleted pf-map files. (31140)
·	Upgrades from Director 7.11e to 8.00 no longer fail with SQL exceptions. (30875)
·	During an upgrade, the installer now checks the existing Director version. If the upgrade path is not supported, the installer prevents the upgrade. (30852)
·	Longer computer names now appear correctly in StorageExtract log files. The maximum computer name length has been increased from 10 characters to 15 characters. (30830)
4.1.5	Fixes in Version 8.00c
·	In some cases, after a Passive vault was upgraded to version 8.0, data could not be replicated from a version 7.11 Active vault to the Passive vault. This problem has been resolved. (31040)
·	Upgrades from version 7.11d to 8.0 now set the listening ports to both 2546 and 807. (31019)
·	An error no longer occurs when you try to uninstall a Director 8.0 vault that was upgraded from version 7.11. (30993)
4.1.6	Fixes in Version 8.00
·	Replication sessions no longer fail because tasks are locked by VVQManager processes. (30215)
·	Backup tasks no longer fail because safesets are locked by VVQManager processes. (29864)
4.2	Known Issues
·	The Director installer does not correctly check whether .NET Framework 4.5 is installed on the system. If .NET Framework 4.0 is installed but .NET Framework 4.5 is not installed, the installation will succeed but replication-related functionality will fail. 
WORKAROUND: Ensure that .NET Framework 4.5 is installed on the system where Director is installed. (32010, 30985)
·	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)
·	When a vvcopy operation takes a long time (e.g., when a safeset includes many small files), the copy operation may fail. (30184)
·	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 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. (23539)
·	Running the vvmigrat command with the parameters file will completely delete the specified customer from the vault even only one job is specified in the parameters file. (22084)
·	If you change the Database Administrator password to a password that does not adhere to the Windows password policy, a SQL Exception message appears. (23644)
·	During installation, a VaultService account is automatically created for starting vault services. If the generated password for this account does not meet the machine's password policy, the installation fails. 
WORKAROUND: Create a local account with Windows Administrator permissions and the "Log on as a service" right, with a password that adheres to the password policy. Install the Director, then change the vault services to log on as "Local System account". (23197)
·	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)
·	When performing a QSM export, you must include the green cluster icon with the VRA job, or the VRA backup to the QSM vault fails due to invalid or expired licenses. (21968)
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)
Documentation is available on the Support website: http://csp.evault.com