Files and FileGroup Backups
You can back up one or more FileGroups or individual files when the database size and performance requirements make it impractical to perform a full database backup.
If you back up an individual file instead of the full database, create procedures to ensure that all files in the database are backed up regularly, and perform separate Transaction log backups for the databases whose files or FileGroups you back up individually. After restoring a file backup, you must apply the successive Transaction log backups to roll the contents of the file forward to make it consistent with the rest of the database. For more information, see the Microsoft SQL Server documentation.
Microsoft SQL Server 2000 and later allow both Full and Differential File and FileGroup backups. If a File and FileGroup Differential backup is performed, restore of this session is dependent on the last Full backup of each file being restored. If you perform Full and Differential backups with different file sets but which contain some files in common, Arcserve will not be able to construct the correct dependency sequence to restore these backups, and you will need to do so manually.
Important! In Microsoft SQL Server 7.0 and 2000, a Database Differential backup is not dependent on any Files-and-FileGroups Full backups that might be between it and the previous Database Full backup. However, in SQL Server 2000 and later, a Database Differential or Partial Differential backup is dependent on any intervening Full backups, including Files-and-FileGroups Full and Partial Full backups. The Automatic Selection feature cannot detect this condition. If you mix Files-and-FileGroups backups with Database Differential and Partial Differential backups in SQL Server 2005, you may need to assemble the restore sequences manually.
Note: You cannot perform Database or Partial restores from a Files-and-FileGroups backup. Only a Files-and-FileGroups restore can be performed from a Files-and-FileGroups backup.
|
Copyright © 2016
|
|