NetVault Plug-in for SQL Server 11.0 - Release Notes

Corrected an issue that prevented closure of backup streams when a backup job was canceled.

23529

Corrected an issue that caused an erroneous “Backup not allowed. Check Configuration and Plug-in Edition License” message to appear when expanding a node under a Virtual Client.

27270

Corrected an issue in which using a named instance and a default instance on the same node prevented the plug-in from displaying the AlwaysOn Availability Group nodes on the named instance.

29074

Corrected an issue that prevented the plug-in from correctly using the Secondary Only algorithm option for backing up an AlwaysOn Availability Group.

29196

Fixed memory leaks.

29393

Reduced the time required to open the All Instances node if an instance is not running when the plug-in starts.

29767

SQL Server® 2005 SP2 is required for Windows Server® 2008 (32/64-bit): For more information, see http://www.microsoft.com/sqlserver/2005/en/us/system-requirements.aspx#ws.

If SP2 is not installed, you might encounter errors when performing differential backups using either the Virtual Device Interface [VDI] or VSS backup methods as described in this article, http://support.microsoft.com/kb/921106/.

17108 (MSG‑321)

Restoring SQL Server® Instances with filestream data fails if the database name is changed or relocated: If the database contains filestream data or files and you rename or relocate the database during the restore, an error message appears and the restore fails. On VSS-based restores, the message is “File <filestreamGroupName> cannot be restored to <originalFilestreamGroupDirectory>. Use WITH MOVE to identify a valid location for the file.”

17196 (MSG‑402)

If you use the Copy Database Files to Target Directory feature, restoring database files from VSS-based backups that contain filestream data does not retain folder structure: Restoring a VSS-based backup of a database that contained subfolders restores all files to the same folder, that is, the directory structure is “flattened.” Because the folder structure of the database is not recreated, a file-activation error appears when you try to access the database.

17200 (MSG‑406)

You must create separate jobs to restore databases from an AlwaysOn Availability Group and databases that are not included in a group. Also, you can only use the same job to restore databases from an AlwaysOn Availability Group if they reside in the same group.

27431

As noted in the user's guide, the plug-in always uses the MTF format for the Media Format during VSS Restores option if the backup target is tape-based.

29778, 29928

On a Virtual Client, the plug-in logs in to each instance listed under the All Instances node when you run a backup job, even if you are not backing up all the listed instances.

29799

When you select Create New for the Selections field during creation of a backup job, the plug-in might erase all settings for the Default Backup Options item. If you have backup jobs that were set up using the Default Backup Options selection, subsequent runs of the jobs might fail.

Workaround: Enter the settings for the Default Backup Options item, or create and assign a new set to jobs that previously used Default Backup Options.

30278

If you upgrade to SQL Server® 2012 or later, you can create a database by restoring a backup that was created using SQL Server 2005 or later; however, you cannot restore backups of master, model, or msdb.

25048