How can I prevent corrupted domino database being replicated

How can I prevent corrupted domino database being replicated to other replica in another server in a domino cluster.
jobby1Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

mbonaciCommented:
AFAIK, you cannot.
0
DominoGCommented:
Run fixup as a scheduled task periodically to fix corrupt databases.  This won't prevent corrupt data replicating but it should fix most data corruptions.
0
LotusDaveCommented:
If you are talking about document level corruption then you don't need to worry about it because Domino only replicates documents it sees as "good". Here is a link to an article that re-inforces my view and uses replication to repair databases containg corrupt documents -
http://my.advisor.com/Articles.nsf/nl/SCHWK68-02

However, as DominoG has suggested regular housekeeping on all servers involving fixup should minimize document corruption.

good luck,
Dave

0
CompTIA Security+

Learn the essential functions of CompTIA Security+, which establishes the core knowledge required of any cybersecurity role and leads professionals into intermediate-level cybersecurity jobs.

jobby1Author Commented:
I am worried if the compact command corrupt the database it will get replicated to other server
0
DominoGCommented:
There should be no more chance of a compact command. causing corruption than any other action against a database.

Would you consider running a scheduled fixup, followed by a compact>  Perhaps on a weekly basis over the weekend.

As Dave mentioned, corrup documents would not normally be replicated.
0
mbonaciCommented:
Corrupt documents is one thing and corrupt database another.
If e.g. ACL becomes corrupt it will be replicated to other replicas.

There's no method on design element that can tell replicator whether the design element is corrupt.
The underlying document can be fine while, at the same time, design element is corrupt.

That's because LN wont discover the fact that design element is corrupt until it tries to interpret it (which, for most of them means - opened in UI).
And that, AFAIK, doesn't happen during replication.
0
mbonaciCommented:
OK, maybe ACL is a bad example, cuz db must be able to interpret it in order to replicate a db.
Form, View, Icon, ScriptLibrary, ...
0
DominoGCommented:
Corrupt design elements comes back to housekeeping again, make sure your templates are up-to-date and there is a scheduled "Design" task setup.
0
LotusDaveCommented:
Agree that corrupt documents is one thing and corrupt design elements is another. In my experience these days corrupt design elements are rarely a problem especially with the good housekeeping methods DominoG has described.
If it is a problem then maybe your server, Domino installation and maintainence proutines needs a good health check.
If it is still a problem then for a particular database you can disable cluster replication for that database and use the replication settings to ensure that design elemetns are not replicated. You will maybe need to increase the rate at which this database replicates otherwise users may experience problems as the databases may be out of sync.

But, in my experience, if you have a good server setup supported by good housekeeping then corruption of design elemnts is rare.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sjef BosmanGroupware ConsultantCommented:
IMHO preventive Fixup tasks are a waste of time and processing power. Regular inspection and monitoring of the log database and proper use of the alarms can help to solve 99% of all problems. Document corruptions don't replicate, and corrupted databases cannot even be opened, sometimes not even after a Fixup.

If you search the Internet, you'll find many pages with: Use Notes replication to rebuild a corrupted database and restore damaged documents.

So I agree with the first response given: you don't prevent it in Domino, and you solve it when it happens. The very best way of prevention is to install good server hardware, use a proper O/S (Linux, AIX, Unix) and install a good UPS.
0
mbonaciCommented:
IMO, you should've accepted my first post as an answer to your question and all others as assisted answers.
Simply because it is an answer to your question. See here:

    http://www.experts-exchange.com/help.jsp#hs=29&hi=405
0
LotusDaveCommented:
Mbonaci IMO I disagree, you're post is not exact, corruption does not replicate. Your answer implies that it does replicate and you cannot do anything to stop it which is not correct.
0
mbonaciCommented:
No, you're wrong, read my comment 32334362.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Lotus IBM

From novice to tech pro — start learning today.