× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Now that the dust has settled after our upgrade to 6.5.4, I've been
studying the changes in the file structure for the server to support
multi-versioning.  I want to make sure that I'm still backing up all of the
necessary files.

I'm sure there are much more sophisticated backup strategies available, but
I'm using a simple CL to end the server, write the files to savefile,
restart the server, then write the savefile to tape.

Currently, I'm saving the data directory from my server (where the
databases are stored), /QIBM/UserData/Lotus/*, and the QNOTES and QUSRNOTES
libraries.  In the redbook Installing and Managing Domino for 6.5 for
iSeries, it indicates that "backing up all Domino databases" simply
requires the data directory and /QIBM/UserData/Lotus/Notes/*.  Apparently,
QNOTES and QUSRNOTES are part of the "program libraries" -- so should I
drop them from my backup?

I'm looking on pages 133 - 135 if anyone wants to see what I'm talking
about.

Also, my iSeries resource guy indicated that if we had a disaster and
needed to recover the entire Domino server (but not the iSeries) that we
could delete the Domino libraries and folders, re-install the server
software, and restore our backup.  By Domino libraries, I'm expecting it to
be all those listed on page 133 of the redbook stated above.  Is this a
wise approach or are we asking for trouble?

Thanks,
Patrick


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.