Downtime in the afternoon
may affect no one. Downtime while the manifests are being generated may result in, at
best, customer dissatisfaction with late deliveries. It could result in a quantifiable monetary
loss if the deliveries aren??™t made at all.
Potential Approach
Frequent, short backups are generally the key to ensuring that a fast restore is possible.
The use of frequent differential backups is a must. This assumes that the database is
small- to medium-sized (up to about 150GB maximum). The full restore operation
should really be the only truly lengthy operation, and it should be reasonably predictable
(the size increases at a steady rate). Without using file or filegroup backups, large databases
aren??™t applicable in this scenario, as the full backup time will be prohibitive.
The critical elements in the approach I??™m describing are the number of backups in
between full backups and the use of differential backups. Yes, you could perform a full
backup nightly and transaction logs every 30 minutes, but restoring a transaction log is
a relatively slow process; the transactions are literally replayed.
Pages:
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262