Re: Trend Scanmail and replication

My SMD experience.

I would replicate all databases. This way it's easy to replicate also design changes when service packs and fixes are released.

Run a compact on the smency.nsf every once a week. As updating occurs every 15 min. Schedule the compact NOT at for example: 00:00 or 00:15 and 00:30 and so on. Schedule it for example at 00:20. When you do you compact error is generated.

Replication or save conflicts were a bug in SMD earlier versions. Do not use program docs for SMDupd and just use the internal rules and policies in SMD.


When I worked on this I noticed that Trend puts templates in domdata but also in c:\program files\trend micro\.......\.. So if you are using modified design then make sure you delete these before starting the services after upgrade.

Hth

Mo
-----------------------------------------
Sent using my BlackBerry Bold



---

-----Original Message-----
From: rob@xxxxxxxxx

Date: Mon, 18 Aug 2008 10:08:13
To: Lotus Domino on the iSeries / AS400<domino400@xxxxxxxxxxxx>
Subject: Re: Trend Scanmail and replication


It boils down to this: How are you updating your virus pattern files?
Does each server go to Trend's Active Update server, or are you
replicating the pattern files around?
We have it set up that each server goes to Trend's Active Update server
and get the pattern file. We discovered that Trend's update database was
also set to replicate. We found the files getting HUGE. Then trend
taught us to Right Click on the database icon in Workspace. Select
Database, Go To, All Docs. Once there we noticed numerous replication and
save conflicts. (Some sort of special view that allowed us to see those.)
Blasting the conflicts took awhile BECAUSE OF ALL THE DISK SPACE BEING
CLEARED. After repeating this gyration several times, on multiple
servers, I contacted Trend and asked them if I could turn off replication
on these, and, since I was using direct to Active Update for all they said
yes.
Now, I just have to figure out the size growth, on these 6 servers,
without the replication or save conflicts...
GROWTH Size Size File name
Directory name
20080801 20080815
1,333,526,528- 2,067,791,872 3,401,318,400 smency.nsf
/GDDATA/NOTES/DATA/smd
4,580,966,400- 2,748,055,552 7,329,021,952 smency.nsf
/GDSHELP/notes/data/smd
1,381,498,880- 2,089,025,536 3,470,524,416 smency.nsf
/GDSSALES/notes/data/smd
4,394,844,160- 2,776,629,248 7,171,473,408 smency.nsf
/INTERNOTES/smd
2,526,019,584- 2,724,724,736 5,250,744,320 smency.nsf
/NOTES01/NOTES/DATA/smd
1,404,567,552- 1,999,896,576 3,404,464,128 smency.nsf
/QUALITY/NOTES/DATA/smd
15,621,423,104- 14,406,123,520 30,027,546,624

Rob Berendt