286 Lotus Discovery Server 2.0
For a distributed server implementation, the backup strategy is complicated by
the fact that you have to identify what Discovery services have been installed on
your secondary servers. You also have to decide whether you want to perform full
system backups of your servers (the simplest option), or selective backups to
minimize downtime and storage costs of your backup media.
A key issue to keep in mind when developing your backup strategy is the amount
of time the primary Lotus Discovery Server will be down. This is important
because many of the Discovery Server secondary servers will not happily
tolerate the loss of access to the primary server. The rule of thumb to apply in
any strategy is
primary server down last and back up first.
9.2.1 Developing a backup strategy
To establish what type of backup strategy is most suitable for your Discovery
Server infrastructure, try answering the following questions about the status of
your current backup strategy and its capacity to meet your Discovery Server
backup requirements. Your answers to these questions should help you identify
issues that need to be addressed before you start deploying Discovery Server as
a strategic component in your IT environment.
What backup software are you currently using?
What does your current software license permit you to do?
Does your backup software support backing up open DB2 and Domino files?
What backup hardware do you have available?
What will be the downtime policy for your Discovery Server servers?
What impact will the scheduled downtime have on each of the Discovery
Services (spidering, indexing, and so forth)?
What backup, recovery, and disaster recovery policies does your company
currently have in place?
How much data do you expect to back up, and at what speed?
What is the anticipated growth of your data?
9.2.2 The importance of backing up the primary server
It is important to note that regardless of your Discovery Server infrastructure and
design, the primary server must always be backed up completely. The new
K-map replication features of Discovery Server 2.0 do not allow you to simply
replicate the K-map to a secondary server, and then perform the backup via that