JKLINT is the system that JKL uses for their website and e-mail. While this data is critical to their business, it is fairly static-- they don't make a lot of changes to the user profiles or configuration data on the system.
They need continuous availability for the critical data on this system, and they accomplish that by having a second system, JKLINT2, that shadows JKLINT. They use a high availability replication solution to copy the data from JKLINT to JKLINT2. Then, if JKLINT goes down, they can switch to JKLINT2.
There is no time to bring JKLINT down for a full backup, so Sharon instead backs up JKLINT2, since it is a replication of JKLINT. She does a full backup of JKLINT2 every weekend using the *System backup policy that came with BRMS. She uses the Lotus® server policy (QLTSSVR) to do an online backup of their Lotus Notes® mail databases every night except the night of the full backup.
Another possible setup: Sharon investigated using logical partitions on JKLINT and JKLINT2 to increase the security of these systems. They could use the a firewall to filter all but e-mail on one partition and all but web traffic on the other partition. Then, the web partition would be protected from any security threats that might come through e-mail, which is a common route of attack. While this setup would have allowed for greater security, it also increased the level of complexity in their network, and Sharon decided that at this point they would stay with the simpler setup.