This also
means understanding fully the impact of either backing up the catalogs (additional
size and backup time) or not being able to restore them (impact to the applications
using them).
Summary
You??™ve seen how file and filegroup backups have the potential to either improve your
backup/restore process, or, if implemented in an awkwardly complex manner, complicate
it. File and filegroup restores can speed up the restore process or reduce the
backup time required for large databases by spreading each backup across a longer
period of time.
Including full-text catalogs in the SQL Server backup process adds another dimension
to the requirements and restrictions on any given backup recovery plan. It can either
be a benefit or another gotcha, depending on the environment.
I??™ve now covered the tools used in a backup/recovery process. In the next chapter, I??™ll
show you how you can put these various tools to use.
CHAPTER 4 n BACKING UP AND RESTORING FILES AND FILEGROUPS 97
Creating a Backup/
Recovery Plan
Now that I??™ve explained the options available to you to back up and restore a database,
the next step is to put those features to use, combining them in a way to create a coherent,
viable backup plan.
Pages:
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208