Automating replication in LotusScript

Hi,

I want to automate replication with 5 different servers through LotusScript.

I am using code which contains the following:
Call Database.Replicate( "Server1" )
Call Database.Replicate( "Server2" )
Call Database.Replicate( "Server3" ) ans so on.

I have also tried flag= Database.Replicate( "Server1" ) and the flag always
returns true.

This is working only in the following case.

1)if Database is a stub and has never been replicated before it replicates
successfully with server1.
it then appears to do something but it does not replicate with the other
servers.

2)if I add, remove or modify a document on the local replica and call the
agent it replicates with the first server but as above not the others

I'm new to Notes and I am baffled, does the Replicate method only work if
the database has been modified since it was last replicated?


Any advice on automating replicating with servers appreciated.


Richard

Hi Richard,
I assume you are using a Notes client and trying to replicate the same
database replica with three different servers.
If this is so then it is performing as intended.
Have a look at the replication history of the local Database. It will only
replicate from the Date/Time of the previous replication.
So server1 replicates OK, then server2 will only look for changes since the
last date/time stamp in its local rep history.
If you had of tried this manually it would be doing exactly the same thing
with the same "failure".
Why can't you replicate with a server and then let the servers replicate
together?
A high maintenance workaround would be to nominate each Database you wish to
replicate in a list and then replicate each individual database.
Of course you need to clear the replication history (local) of each Database
before replicating.
get first replica in list
clear its replication history (local)
replicate thisDB with server 1
clear its replication history (local)
replicate thisDB with server 2
clear its replication history (local)
replicate thisDB with server 3
go back and get the next replica
The rep history will only clear if you have Manager access. So if "Enforce
a consistent ACL" is set, You will need to be Manager as stated in the ACL
of each database.
You are fighting the Notes language. Sometimes you have to and it is not
pleasant. You probably don't need to fight, is there another native way?
John Aylmer

"Richard Annison" wrote in message
news:c6s25v$j2p$1-at-sparta.btinternet.com...
> Hi,
>
> I want to automate replication with 5 different servers through
LotusScript.
>
> I am using code which contains the following:
> Call Database.Replicate( "Server1" )
> Call Database.Replicate( "Server2" )
> Call Database.Replicate( "Server3" ) ans so on.
>
> I have also tried flag= Database.Replicate( "Server1" ) and the flag always
> returns true.
>
> This is working only in the following case.
>
> 1)if Database is a stub and has never been replicated before it replicates
> successfully with server1.
> it then appears to do something but it does not replicate with the other
> servers.
>
> 2)if I add, remove or modify a document on the local replica and call the
> agent it replicates with the first server but as above not the others
>
> I'm new to Notes and I am baffled, does the Replicate method only work if
> the database has been modified since it was last replicated?
>
>
> Any advice on automating replicating with servers appreciated.
>
>
> Richard
>
>

Hi Richard,
I assume you are using a Notes client and trying to replicate the same
database replica with three different servers.
If this is so then it is performing as intended.
Have a look at the replication history of the local Database. It will only
replicate from the Date/Time of the previous replication.
So server1 replicates OK, then server2 will only look for changes since the
last date/time stamp in its local rep history.
If you had of tried this manually it would be doing exactly the same thing
with the same "failure".
Why can't you replicate with a server and then let the servers replicate
together?
A high maintenance workaround would be to nominate each Database you wish to
replicate in a list and then replicate each individual database.
Of course you need to clear the replication history (local) of each Database
before replicating.
get first replica in list
clear its replication history (local)
replicate thisDB with server 1
clear its replication history (local)
replicate thisDB with server 2
clear its replication history (local)
replicate thisDB with server 3
go back and get the next replica
The rep history will only clear if you have Manager access. So if "Enforce
a consistent ACL" is set, You will need to be Manager as stated in the ACL
of each database.
You are fighting the Notes language. Sometimes you have to and it is not
pleasant. You probably don't need to fight, is there another native way?
John Aylmer

"Richard Annison" wrote in message
news:c6s25v$j2p$1-at-sparta.btinternet.com...
> Hi,
>
> I want to automate replication with 5 different servers through
LotusScript.
>
> I am using code which contains the following:
> Call Database.Replicate( "Server1" )
> Call Database.Replicate( "Server2" )
> Call Database.Replicate( "Server3" ) ans so on.
>
> I have also tried flag= Database.Replicate( "Server1" ) and the flag always
> returns true.
>
> This is working only in the following case.
>
> 1)if Database is a stub and has never been replicated before it replicates
> successfully with server1.
> it then appears to do something but it does not replicate with the other
> servers.
>
> 2)if I add, remove or modify a document on the local replica and call the
> agent it replicates with the first server but as above not the others
>
> I'm new to Notes and I am baffled, does the Replicate method only work if
> the database has been modified since it was last replicated?
>
>
> Any advice on automating replicating with servers appreciated.
>
>
> Richard
>
>

Thankyou John,

I'll explain a little further what I'm trying to do. I am prepparing PCs to
be sent to remote site that use dial up connections to the servers. Part of
the preparation is to replicate all the local replicas with all our servers
so that the 'one time replication' has been completed. There are about 15
local replicas on each machine and about 5 of these are over 1.5 GB in size.

If the usual server is down or not contactable and the remote PC tries to
use a diferent server and they haven't been replicated with that server
before it can take over 24 hours for just one of these big DBs to replicate
over the dial up link.

I currently replicate with all the servers from the replicator page by
choosing other actions- replicate with server. For each server. I want to
automate this process so that it will completed over night without my
intervention.

Please help

Richard




"John Aylmer" wrote in message
news:c6soen$n98$1-at-gnamma.connect.com.au...
> Hi Richard,
> I assume you are using a Notes client and trying to replicate the same
> database replica with three different servers.
> If this is so then it is performing as intended.
> Have a look at the replication history of the local Database. It will only
> replicate from the Date/Time of the previous replication.
> So server1 replicates OK, then server2 will only look for changes since
the
> last date/time stamp in its local rep history.
> If you had of tried this manually it would be doing exactly the same thing
> with the same "failure".
> Why can't you replicate with a server and then let the servers replicate
> together?
> A high maintenance workaround would be to nominate each Database you wish to
> replicate in a list and then replicate each individual database.
> Of course you need to clear the replication history (local) of each Database
> before replicating.
> get first replica in list
> clear its replication history (local)
> replicate thisDB with server 1
> clear its replication history (local)
> replicate thisDB with server 2
> clear its replication history (local)
> replicate thisDB with server 3
> go back and get the next replica
> The rep history will only clear if you have Manager access. So if
"Enforce
> a consistent ACL" is set, You will need to be Manager as stated in the ACL
> of each database.
> You are fighting the Notes language. Sometimes you have to and it is not
> pleasant. You probably don't need to fight, is there another native way?
> John Aylmer
>

Thankyou John,

I'll explain a little further what I'm trying to do. I am prepparing PCs to
be sent to remote site that use dial up connections to the servers. Part of
the preparation is to replicate all the local replicas with all our servers
so that the 'one time replication' has been completed. There are about 15
local replicas on each machine and about 5 of these are over 1.5 GB in size.

If the usual server is down or not contactable and the remote PC tries to
use a diferent server and they haven't been replicated with that server
before it can take over 24 hours for just one of these big DBs to replicate
over the dial up link.

I currently replicate with all the servers from the replicator page by
choosing other actions- replicate with server. For each server. I want to
automate this process so that it will completed over night without my
intervention.

Please help

Richard




"John Aylmer" wrote in message
news:c6soen$n98$1-at-gnamma.connect.com.au...
> Hi Richard,
> I assume you are using a Notes client and trying to replicate the same
> database replica with three different servers.
> If this is so then it is performing as intended.
> Have a look at the replication history of the local Database. It will only
> replicate from the Date/Time of the previous replication.
> So server1 replicates OK, then server2 will only look for changes since
the
> last date/time stamp in its local rep history.
> If you had of tried this manually it would be doing exactly the same thing
> with the same "failure".
> Why can't you replicate with a server and then let the servers replicate
> together?
> A high maintenance workaround would be to nominate each Database you wish to
> replicate in a list and then replicate each individual database.
> Of course you need to clear the replication history (local) of each Database
> before replicating.
> get first replica in list
> clear its replication history (local)
> replicate thisDB with server 1
> clear its replication history (local)
> replicate thisDB with server 2
> clear its replication history (local)
> replicate thisDB with server 3
> go back and get the next replica
> The rep history will only clear if you have Manager access. So if
"Enforce
> a consistent ACL" is set, You will need to be Manager as stated in the ACL
> of each database.
> You are fighting the Notes language. Sometimes you have to and it is not
> pleasant. You probably don't need to fight, is there another native way?
> John Aylmer
>

Hi Richard,
Assumptions by me:
The same databases exist on all servers.
The servers are not Domino clustered

> If the usual server is down or not contactable and the remote PC tries to
> use a diferent server and they haven't been replicated with that server
> before it can take over 24 hours for just one of these big DBs to
replicate
> over the dial up link.
The replication history records the last replication date/time for each
server.
If there are any integrity doubts then Domino replicates the whole lot down
again.
You are fighting Domino infrastructure rules. Have a look a clustering.
Suggest you get a good admin person in to evaluate what you are doing and to
get some guidance
You will be amazed what you will learn in a few hours with such a person.
John Aylmer

"Richard Annison" wrote in message
news:c6suip$j9i$1-at-hercules.btinternet.com...
> Thankyou John,
>
> I'll explain a little further what I'm trying to do. I am prepparing PCs
to
> be sent to remote site that use dial up connections to the servers. Part
of
> the preparation is to replicate all the local replicas with all our
servers
> so that the 'one time replication' has been completed. There are about 15
> local replicas on each machine and about 5 of these are over 1.5 GB in
size.
>
> If the usual server is down or not contactable and the remote PC tries to
> use a diferent server and they haven't been replicated with that server
> before it can take over 24 hours for just one of these big DBs to
replicate
> over the dial up link.
>
> I currently replicate with all the servers from the replicator page by
> choosing other actions- replicate with server. For each server. I want to
> automate this process so that it will completed over night without my
> intervention.
>
> Please help
>
> Richard
>
>
>
>
> "John Aylmer" wrote in message
> news:c6soen$n98$1-at-gnamma.connect.com.au...
> > Hi Richard,
> > I assume you are using a Notes client and trying to replicate the same
> > database replica with three different servers.
> > If this is so then it is performing as intended.
> > Have a look at the replication history of the local Database. It will only
> > replicate from the Date/Time of the previous replication.
> > So server1 replicates OK, then server2 will only look for changes since
> the
> > last date/time stamp in its local rep history.
> > If you had of tried this manually it would be doing exactly the same
thing
> > with the same "failure".
> > Why can't you replicate with a server and then let the servers replicate
> > together?
> > A high maintenance workaround would be to nominate each Database you wish to
> > replicate in a list and then replicate each individual database.
> > Of course you need to clear the replication history (local) of each Database
> > before replicating.
> > get first replica in list
> > clear its replication history (local)
> > replicate thisDB with server 1
> > clear its replication history (local)
> > replicate thisDB with server 2
> > clear its replication history (local)
> > replicate thisDB with server 3
> > go back and get the next replica
> > The rep history will only clear if you have Manager access. So if
> "Enforce
> > a consistent ACL" is set, You will need to be Manager as stated in the
ACL
> > of each database.
> > You are fighting the Notes language. Sometimes you have to and it is
not
> > pleasant. You probably don't need to fight, is there another native
way?
> > John Aylmer
> >
>
>

Hi Richard,
Assumptions by me:
The same databases exist on all servers.
The servers are not Domino clustered

> If the usual server is down or not contactable and the remote PC tries to
> use a diferent server and they haven't been replicated with that server
> before it can take over 24 hours for just one of these big DBs to
replicate
> over the dial up link.
The replication history records the last replication date/time for each
server.
If there are any integrity doubts then Domino replicates the whole lot down
again.
You are fighting Domino infrastructure rules. Have a look a clustering.
Suggest you get a good admin person in to evaluate what you are doing and to
get some guidance
You will be amazed what you will learn in a few hours with such a person.
John Aylmer

"Richard Annison" wrote in message
news:c6suip$j9i$1-at-hercules.btinternet.com...
> Thankyou John,
>
> I'll explain a little further what I'm trying to do. I am prepparing PCs
to
> be sent to remote site that use dial up connections to the servers. Part
of
> the preparation is to replicate all the local replicas with all our
servers
> so that the 'one time replication' has been completed. There are about 15
> local replicas on each machine and about 5 of these are over 1.5 GB in
size.
>
> If the usual server is down or not contactable and the remote PC tries to
> use a diferent server and they haven't been replicated with that server
> before it can take over 24 hours for just one of these big DBs to
replicate
> over the dial up link.
>
> I currently replicate with all the servers from the replicator page by
> choosing other actions- replicate with server. For each server. I want to
> automate this process so that it will completed over night without my
> intervention.
>
> Please help
>
> Richard
>
>
>
>
> "John Aylmer" wrote in message
> news:c6soen$n98$1-at-gnamma.connect.com.au...
> > Hi Richard,
> > I assume you are using a Notes client and trying to replicate the same
> > database replica with three different servers.
> > If this is so then it is performing as intended.
> > Have a look at the replication history of the local Database. It will only
> > replicate from the Date/Time of the previous replication.
> > So server1 replicates OK, then server2 will only look for changes since
> the
> > last date/time stamp in its local rep history.
> > If you had of tried this manually it would be doing exactly the same
thing
> > with the same "failure".
> > Why can't you replicate with a server and then let the servers replicate
> > together?
> > A high maintenance workaround would be to nominate each Database you wish to
> > replicate in a list and then replicate each individual database.
> > Of course you need to clear the replication history (local) of each Database
> > before replicating.
> > get first replica in list
> > clear its replication history (local)
> > replicate thisDB with server 1
> > clear its replication history (local)
> > replicate thisDB with server 2
> > clear its replication history (local)
> > replicate thisDB with server 3
> > go back and get the next replica
> > The rep history will only clear if you have Manager access. So if
> "Enforce
> > a consistent ACL" is set, You will need to be Manager as stated in the
ACL
> > of each database.
> > You are fighting the Notes language. Sometimes you have to and it is
not
> > pleasant. You probably don't need to fight, is there another native
way?
> > John Aylmer
> >
>
>