In Plug‑in for SQL Server version 6.1 and earlier, the plug-in could overrun the index markers for large-size databases. So, the start position marker had a higher value than expected. The issue was corrected in the plug-in version that followed the mentioned version 6.1 of the plug-in. Also, in Plug‑in for SQL Server 11.4.5 more policy checks has been added to policy the index markers. |
|
An issue has been corrected that resulted in the Plug‑in for SQL Server to display, in a failover cluster, the name of the active node listed under the All Instances browse tree node. |
|
Corrected an issue to ensure that the Plug‑in for SQL Server only logs on to instances selected for backup in an AlwaysOn Availability Group. The Plug‑in for SQL Server no longer logs on to each instance unless ‘All Instances’ option is selected. |
|
For Failover Cluster environments, an issue has been corrected, to allow the NetVault Backup Plug‑in for SQL Server display the SQL Server Failover Virtual Instance, during browsing sessions to create Backup Selections Sets. The SQL Server Failover Virtual Instance can be added using the Add Instance action, or automatically detected if the SQL Server Browser Service is running in all the nodes of the Failover Cluster. |
|
In previous versions of the Plug‑in for SQL Server, if a SQL Server database name contained one or more blank spaces, then the database was not being correctly displayed in the Backup Selections, and backups that included the database, also failed. The issue has been corrected, and the Plug‑in for SQL Server properly handles SQL Database names containing one or more blank spaces. |
|
Corrected an issue to describe the number of connections to the SQL Server a Plug‑in for SQL Server uses during VSS backup and VDI backup methods. |
|
Corrected an issue, that resulted in a failed restore of the msdb database, whenever the Plug‑in for SQL Server was not able to access or obtain the running status of the SQL Server Agent Service. The issue occurred, even in the case in which the running status was the appropriate for resulting in a successful restore of the msdb database. |
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/. |
|
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.” |
|
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 sub-folders 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. |
|
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. |
|
Plug‑in for SQL Server® 11.4.5 requires NetVault Backup 10.0 or later. For complete supported-platform information, see the Quest NetVault Backup Compatibility Guide.
© ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center