Reducing backup size and time by using read-only filegroups
Many applications contain a substantial amount of data that does not change. For example, under time-based partitioning, historical data may be preserved indefinitely. Only a fraction of the database is subject to change at any given time. Static filegroups can be classified as read-only. NetBackup uses the filegroup read-only designation to optimize the total backup volume speed of recovery.
For backups, the advantage in using read-only filegroups is that you can reduce total media usage. You back up the read-only filegroups one time and retain the backup image indefinitely. This strategy reduces the total time you spend on backup operations because only read-write data is backed up periodically.
For recovery, the advantage is that you can bring your database online more quickly. Read-only filegroups do not need to be restored from backup media unless they are corrupted due to disk error or other hardware failure.
For Intelligent Policy configuration, see the following topics:
See Backing up read-only filegroups (SQL Server Intelligent Policies).
See Backing up read-write filegroups (SQL Server Intelligent Policies).
For legacy policy configuration, see the following topics:
See Backing up read-only filegroups (legacy SQL Server backup policies).
See Backing up read-write filegroups (legacy SQL Server backup policies).