|
Corrected an issue that caused VDI Backup Jobs to fail with a Job Manager lost message channel unexpectedly error for very large databases when High compression was selected. |
|
|
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. |
|
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center
