On one i lpar we have 11 dpars. One of these dpar's sole purpose is to
run Domino Fax for iSeries. No user mail files, etc are stored on this
dpar. It supports 1 outbound line and 3 inbound DID lines for fax.
Currently we bring the server down 5 nights a week and back it up. We
want to stop bringing it down so often. We are mulling over several
strategies.
- BRMS. Heck, we purchased it and it sits on a shelf (one of those
package deals awhile back). We don't think it fits our current backup
strategy for the rest of our system. Sounds a little complicated for just
this. And according to
http://www.redbooks.ibm.com/redbooks/pdfs/sg247311.pdf
(section 9.1.3) you have to drop the server anyway to save the notes.ini
and stuff.
- Replicate a few databases around to another server and back them up
there.
I tried using iNav and sorted the files in that server's data directory by
changed date descending. Rather stunned by the number of files changed
within the last hour. And nothing in the log.nsf seems indicative of what
might have changed them. Sure, there's your typical log.nsf and stuff.
And notes.ini. But there's a whole plethora of .xml, .ntf, .nbf, .DTF
changed within the last hour also.
Gut was initially thinking that if I replicated nfxadmin.nsf and
nfxcover.nsf I should be able to rebuild it from a weekly backup or
something. I'm not too hung up on nfxlog or the stuff in
IBM_TECHNICAL_SUPPORT. I am still thinking I probably could do it this
way.
Any thoughts?
Rob Berendt
midrange.com
