×
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.
We do clustering. ServerA1 will be in a cluster with ServerA2 and
ServerA3. There will be a B, C, D... for different functions.
We only backup ServerA1 once a quarter. We backup ServerA2 nightly, after
dropping it.
User (from our department, luckily) opened a file on ServerA2 and noticed
that it didn't have any documents. So I went into it, saw the same thing
and did a File, Replication with ServerA1. Ran quick but no documents. So
I did a File, Replication, Clear history. Reran the replication and got
all the documents. Took a lot longer too.
So how does one handle this, operationally? Is there a tool in
Administrator that says these databases don't match and you need to handle
it, perhaps clear replication history? I'd hate to setup an agent to just
clear replication history on all databases on a periodic basis. I can see
it taking days to check this, bottleneck the network, play havoc with
backup and generally making my life unpleasant.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
