3.3

5 Backing Up the iNEWS System
80
At this message, dbserver is finished and you may proceed. You can run dbfree again to
verify that you have enough space.
Restoring the Database
When a story being restored has more than 1,000 lines, the following message is displayed:
Warning: Large story being restored.
Queue: FUTURES.FEBRUARY
Title: "Senate Hearing"
Size: 1004 lines (approximate)
Press <del> to skip this story.
If the story size continues to grow, the following message prints every 1500 lines:
Large story continuing: 1500 lines
Press <del> to skip this story.
To skip the large story, press Delete while it is being restored.
Disaster Recovery Planning
Having a complete dbdump of the database ensures that you can restore your data in case of
calamity; however, restoring a complete dbdump to a freshly initialized database can be very
time-consuming and leave the newsroom without access to the system until the full database
dbrestore finishes. On very large databases, the full database dbrestore can take from 12 to
36 hours.
Planning a separate, efficient disaster recovery dbdump/dbrestore procedure can
significantly speed up the time before the system becomes functional to users.
Disaster Recovery Dbdump
The first step is to create a stripped down dbdump that contains the directory structure and
minimal amount of queues and directories needed to bring the system online. After the
minimal dbdump was restored, users can start working while the remainder of the database
is restored from the last full database dbdump tape.