User guide

48 EMC Avamar 7.0 Release Notes
Known problems and limitations
Microsoft SQL Server plug-in
The following table lists known problems for this release of the Avamar Plug-in for SQL
Server.
Table 19 Microsoft SQL Server plug-in known problems (page 1 of 2)
ID Description
19575 Tail-log backup of a small amount of data may result in data not available
If the tail-log backup fails for any reason during a restore, then an error message
appears and the restore is aborted. However, if the amount of data added or changed
since the most recent backup is very small (less than about 25 MB) then SQL Server
may not be able to retain the information. The recovery exits with an error, and the
tail-log backup is not available.
33288 Restore with a new database name from a differential or incremental backup in an
earlier release fails
If you upgrade the Avamar server and the Avamar Plug-in for SQL Server to release 6.1
or 7.0 and then you attempt to restore a database with a new name from a differential
or incremental backup in an earlier Avamar release, then the restore fails.
To work around this issue, perform a full backup after the upgrade and restore only
from backups with release 6.1 or 7.0. If you must restore from a backup in an earlier
release, then restore only from a full backup.
35262 Subsequent restores with a new database name fail when restoring from a backup set
that includes a tail-log backup
Restore fails if the following scenario occurs:
1. You successfully perform a tail-log backup and restore a database.
2. You restore to a new database from the same backup set, which now includes the
tail-log backup, and you specify a new name for the database.
The restore to the new database fails, and the new database remains in the restoring
state. (The database that you restored in step 1 is not affected by this failed restore.)
To work around this issue, restore the backup to a file, and then use SQL Server
Management Tools to restore from the file to the new database.
49416 Restore of differential backup after database is removed from availability group may
fail
After a database is removed from an availability group, restores from differential
backups of the database may fail.
50055 FILESTREAM data restores to the database folder during redirected restore
FILESTREAM data restores to the folder with the database files, even if the FILESTREAM
data was originally in a different folder than the database files, when the following
conditions are true:
• You are restoring the database to a different location than the original location at
the time of the backup.
• You specify the new location by using the Alternate database location box on the
Restore Command Line Options dialog box.
To avoid this issue, specify the restore location for both the database files and the
FILESTREAM data in the Set Destination dialog box.
50495 Restore fails when the folder with FILESTREAM data is open
Restore of a database with FILESTREAM data fails when the folder with FILESTREAM
data is open in a program such as Windows Explorer.
To avoid this issue, close the program that is accessing the folder with the FILESTREAM
before you perform the restore. However, if the FILESTREAM folder is open and the
restore fails, then perform the restore again and select the WITH REPLACE option to
force the restore and bring the database online.