Potential Approach
By default, the full-text catalog has its own file. All you need to do is a specific file backup.
Because the full-text data is actually stored externally to the database, you don??™t even
need transaction log backups. You might, for example, schedule the following single task:
??? Nightly backup of all full-text catalog files at 10 p.m.
That??™s it. It??™s extremely simple, but being a new feature to 2005, it should be clearly
spelled out as a possible backup/recovery approach.
CHAPTER 5 n CREATING A BACKUP/RECOVERY PLAN 136
Inherent Risks
Table 5-6 shows the risks inherent in a scenario that backs up large, full-text catalogs.
Table 5-6. Risk Breakdown for a Full-Text-Catalog Scenario
Risk Worst-Case Impact Best-Case Impact
Data loss None really, since these indexes aren??™t None really, since these indexes
permanent data aren??™t permanent data
Restore time Depends entirely on the size of the indexes Depends entirely on the size of the
indexes
Perceived Could be unavailable until the indexes are Could appear partially available if the
downtime restored, if the application relies on them application has some functionality
100% without the indexes
As with the previous scenario, this should be an extremely rare situation.
Pages:
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277