Table 3. General known issues 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. 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 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. The plug-in name has been changed to use the “Plug-in for <product>” naming convention (that is, Plug‑in for SQL Server). If you upgrade the plug-in for a system that is managed by a NetVault Backup Server 9.2, savesets created with the upgraded plug-in are not displayed in the NVBU Restore window when the Selection Method is set to Plugin; only savesets created with an earlier version are displayed.Workaround for NetVault Backup Server 9.2: On the Selections tab of the NVBU Restore window, select Job in the Selection Method list to view savesets or backups created with a previous version or the upgraded plug-in. NetVault Backup 9.2 creates separate backup savesets for each node contained in an All Instances node of an AlwaysOn Availability Group: If you use the plug-in with NetVault Backup 9.2, selecting the All Instances node as the backup target creates a backup saveset for each instance included in the node. To restore a backup, follow the guidelines and steps in “Restoring data to a Virtual Client” in the user's guide.
Table 4. Third-party known issues 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.
Table 5. Requirements Windows Server® 2003 SP1 (32-bit) SQL Server® 2005 (32-bit) Windows Server® 2003 SP1 (64-bit) SQL Server® 2005 (32/64-bit) Windows Server® 2003 SP2 (32-bit) SQL Server® 2008 (32-bit) Windows Server® 2003 SP2 (32-bit) SQL Server® 2008 R2 (32-bit) Windows Server® 2003 SP2 (64-bit) SQL Server® 2008 (32/64-bit) Windows Server® 2003 SP2 (64-bit) SQL Server® 2008 R2 (32/64-bit) Windows Server® 2003 R2 SP2 (32-bit) SQL Server® 2008 R2 (32-bit) Windows Server® 2003 R2 SP2 (64-bit) SQL Server® 2008 R2 (32/64-bit) Windows Server® 2008 (32-bit) SQL Server® 2005 SP2 (32-bit) Windows Server® 2008 (32-bit) SQL Server® 2008 (32-bit) Windows Server® 2008 (64-bit) SQL Server® 2005 SP2 (32/64-bit) Windows Server® 2008 (64-bit) SQL Server® 2008 (32/64-bit) Windows Server® 2008 SP2 (32-bit) SQL Server® 2008 R2 (32-bit) Windows Server® 2008 SP2 (32-bit) SQL Server® 2012 (32-bit) Windows Server® 2008 SP2 (32-bit) SQL Server® 2014 (32-bit) Windows Server® 2008 SP2 (64-bit) SQL Server® 2008 R2 (32/64-bit) Windows Server® 2008 SP2 (64-bit) SQL Server® 2012 (32/64-bit) Windows Server® 2008 SP2 (64-bit) SQL Server® 2014 (32/64-bit) Windows Server® 2008 R2 (64-bit) SQL Server® 2008 (32/64-bit) Windows Server® 2008 R2 (64-bit) SQL Server® 2008 R2 (32/64-bit) Windows Server® 2008 R2 SP1 (64-bit) SQL Server® 2012 (32/64-bit) Windows Server® 2008 R2 SP1 (64-bit) SQL Server® 2014 (32/64-bit) Windows Server® 2012 Full Server and Server Core (64-bit) SQL Server® 2008 (32/64-bit) Windows Server® 2012 Full Server and Server Core (64-bit) SQL Server® 2008 R2 (32/64-bit) Windows Server® 2012 Full Server and Server Core (64-bit) SQL Server® 2012 (32/64-bit) Windows Server® 2012 Full Server and Server Core (64-bit) SQL Server® 2014 (32/64-bit) Windows Server® 2012 R2 Full Server and Server Core (64-bit) SQL Server® 2008 (32/64-bit) Windows Server® 2012 R2 Full Server and Server Core (64-bit) SQL Server® 2008 R2 (32/64-bit) Windows Server® 2012 R2 Full Server and Server Core (64-bit) SQL Server® 2012 (32/64-bit) Windows Server® 2012 R2 Full Server and Server Core (64-bit) SQL Server® 2014 (32/64-bit)
Plug‑in for SQL Server® 10.0.6 requires NetVault Backup 9.0 or later. For complete supported-platform information, see the Dell NetVault Backup Compatibility Guide.Starting with NetVault Backup 8.6, a new build type named “LinuxX86Pure64” has been added, while the pure 32-bit Linux® version has been retired. To understand the impact of this change, review the following:
• Hybrid 32/64-bit Build: The hybrid 32/64-bit build has been retained. However, the platform type has been renamed from “LinuxX8664” to “LinuxX86Hybrid.” This build functions as the standard build for Linux users who do not have a pure 64-bit-only requirement. This build lets you upgrade from pure 32-bit as well as from hybrid builds of NetVault Backup.
• Pure 64-bit Build: A new type of build named “LinuxX86Pure64” has been introduced for pure 64-bit Linux distributions. If you have a specific reason that you cannot use any 32-bit components (for example, you are using a Linux distribution that does not run 32-bit code), use this type. You cannot use this new type to upgrade existing NetVault Backup installations; remove the existing version and install the pure 64-bit version separately. To reduce confusion, warning messages have been added to both the upgrade and installation packages to ensure that you understand that they are not compatible.
Table 6. Pure64 builds
NOTE: X = Compatible
To obtain the license key for your NetVault Backup Server environment, determine the NetVault Machine ID of your main NetVault Backup Server. Also identify the machine IDs of any clients running application plug-ins, such as Oracle®, MySQL, PostgreSQL, SQL Server®, and Exchange.
2 In the Navigation pane, click Manage Clients.
3
4
1
2
3
4
1
2
3
4
5
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center