EVault Reports Version 74. 3039 Release Notes, March 14, 2016

______________________________________________________________________

1. OVERVIEW

Once all the parts of the EVault Reports system are installed and running, the following steps occur to produce reports. This list of steps provides an overview only.

1. The Extractor program is run (manually or scheduled) on each vault and collects the data.

2. The data is sent to the Loader web service on the IIS Server.

3. The Loader web service stores the data in the SQL database.

4. A user on a web browser logs into the report viewer and requests a report.

5. The web application pulls the appropriate data from the database, and sends it as a report to the user.

Replication:

In a replication environment, the EVault Reports Extractor must be installed on both vaults. It will detect the “Active” or “Passive” vault. In this configuration the extractor will only extract and load the information from the active vault.

In case of a failover, the extractor will detect the newly active vault and will start sending data to EVault Reports from the newly active vault. However, the data will be sent using the vault name where the initial extraction was done, so only one vault is represented in the reports for this configuration.

In an N:1 configuration, the extractor (installed on the Base vault only) will work as on a “regular” vault. Satellite configuration will not be visible to the EVault Reports Extractor.

See the Director Operations Guide for more information about vault replication.

1. Release History

Version 2.73.2838, October 15, 2014

Version 2.72.2631, December 10, 2013

Version 2.71.1674a, January 18, 2012

Version 2.71.1674, February 15, 2011

2. Supported Platforms

• 
  Windows Server 2012 R2 Standard
  
• 
  Windows Server 2012 R2 Datacenter
  
• 
  Windows Server 2012 Standard
  
• 
  Windows Server 2012 Datacenter
  
• 
  Windows Server 2008 R2 Standard
  
• 
  Windows Server 2008 R2 Enterprise
  
• 
  Windows Server 2008 R2 Datacenter
  

• 
  SQL Server 2012 SP2 64-bit
  
• 
  SQL Server 2008 R2 SP2 64-bit
  

EVault Report Manager 2.74 is supported with the current version of the following web browsers:

• 
  Mozilla Firefox
  
• 
  Microsoft Internet Explorer
  

2. NEW FEATURES

• 
  Integration with EVault Portal 7.62 or later
  
• 
  Integration with Web CentralControl 7.62 or later
  

3. INSTALLATION NOTES

   1. Installation Requirements

• 
  Internet Information Services (IIS) server (Version 7 or later)
  
• 
  ASP.NET (3.5) Framework
  
• 
  A supported version of SQL Server with Reporting Services must be installed and running
  

2. Licensing

3. Install/Uninstall/Upgrade

The Extractor program is not a part of the EVault Reports installation. It is a separate kit, and you install it on the vault system. Silent installation is supported for the Extractor.

After you install EVault Reports, you must configure the Extractor (SynchWeb) program on each vault. It requires the URL of the EVault Reports Loader service so that the vault can send its data there.

Note: If you use NT Authentication, and you install on multiple servers, you must select the NT Authentication component. You must do this for each server on which you install an EVault Reports component. See item 20746 in the Known Issues section for details.

For custom installations, if you are using NT Authentication for user authorization to the reports, you do not need to install the Token Manager or Login components.

You can install the Report Viewer without the NT Authentication component, but you must also install the Token Manager and Login components.

Before upgrading EVault Reports, back up the UserCustomer.xml file in the main directory of the ERLogin web application (C:\inetpub\ERLogin).

An upgrade sometimes overwrites the UserCustomer.xml file. If this occurs, users will not be able to log in. You can then restore the backed up UserCustomer.xml file.

4. FIXES and KNOWN ISSUES

   1. Fixes

      1. Fix in Version 2.74

2. Fix in Version 2.73

3. Fixes in Version 2.72

In previous versions, the Activity Details Report did not list a job unless at least one successful backup for the job had already occurred. The Activity Details Report now lists each job as Successful, Failed, or Unknown, as appropriate. (25226)

2. Known Issues

- WebReference.ReportService2005

- ReportSubscription_WebReference_ReportingService2010

- ReportSubscriptionWebApp_WebReference_ReportingService2010

After EVault Reports is upgraded, users might not be able to log in.
WORKAROUND: Before upgrading EVault Reports, back up the UserCustomer.xml file in the main directory of the ERLogin web application (C:\inetpub\ERLogin). If the file gets overwritten during the upgrade, restore the backed up UserCustomer.xml file. (28142)

In Internet Explorer, after EVault Reports is upgraded from version 2.72 to version 2.74, the label on the "Run Report" button is "Hide Filters". However, the report runs correctly if you click the "Hide Filters" button. (29165)

If you use NT Authentication, and you install on multiple servers, you must select the NT Authentication component. You must do this for each server on which you install an EVault Reports component (including the SQL server system). Please refer to the following example. On the SQL server, install these components:

Reports Database

NT Authentication

On the IIS server, install these components:

Loader

Report Viewer

Report Manager

(20746)

The Extractor may not run long enough, and missing extractions can result in inaccurate report data. For example, the "Storage Reports for all Safesets Report" might repeat the original size of safesets for all jobs for the entire report period. This is expected behavior because there were no extractions during the specified time. The Extractor cannot determine which safesets are online or offline when it is not running. The Extractor can only show the state of the vault before and after it runs. (19542)

EVault Reports Extractor (the Director component of EVault Reports) is not supported on satellite vaults. The Extractor should only be run on the Base vault. (14326)

If you log into EVault Reports directly, there are no tabs to return you to Web CentralControl. If you integrate Web CentralControl and EVault Reports, you should access EVault Reports from within Web CentralControl. If you log into EVault reports directly, you will not be able to see the Backup Console tabs.

Group Storage Details reports can become misaligned, and new scrollbars may appear. This is an effect of DTS #8080. Note that the exported group storage reports in PDF are not affected.

If the client is on a different domain from the server domain, or if the server is not on a domain, there may be a slight delay displaying and switching between reports. To resolve this, add the server to the domain, or configure IIS to use anonymous access. Alternatively, you can force NTLM authentication (i.e., disable Kerberos) with the help of the following Microsoft KB article: http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/7258232a-5e16-4a83-b76e-11e07c3f2615.mspx?mfr=true

The Last Backup Date, Backup Duration, Original Size (GB) and Delta size (MB) columns on the Backup Status Report might show "Unavailable" for some deleted customers/locations/computers/jobs.

You must have mixed mode authentication turned on for the SQL 2008 installation. You must also enable named pipes and TCP/IP.

A Custom installation may show soap exceptions, and item not found, after logging in. In order for the Reporting Services to be configured correctly, the database installation must be done from the machine on which Reporting Services is running. The NT Authentication component (if used) must be installed on the same machine as the Report Viewer.

Failed restores may indicate successful results in 'Activity Details' and 'Backup and Restore Summary' Reports. This may be due to an incorrect password supplied for the restore operation.

Storage Details Report may show incorrect values (i.e., swapped) for attached secondary and detached secondary (offline) safesets.

A discrepancy may be perceived in EVault Reports on Version 4 pools. Because "Storage Details Report" uses safeset active time, and "Backup Status Report" uses backup activity time, you may notice a discrepancy in task size between these two reports if the times are close to each other. For example, in one report, the original size may be 0, and in the other, it may be 10 GB.

5. PRODUCT SUPPORT

   1. Technical Support

2. Product Updates

3. Documentation

• 
  EVault Reports release notes (this document)
  
• 
  EVault Reports User Guide
  
• 
  EVault Reports Migration Guide