When making a new copy of a database from one directory to another, the db only partially copies and I get error “Session to Server Lost while Replicating or Copying” -
The failure occures approx 1/3 through file copy. Drive space is abundant as are system resources. File size being copied is around 270mb.
Trying to make a copy of a server database that is only 447k, I got the same problem. I was trying to copy the db to the same server, same directory. The server is a Windows 2000 server, and I was using File, Database, New Copy in the Notes client 6.0.1 on a Windows XP machine.
Not a real connectivity problem, as I was immediately able to access the server.
Once server was restarted, the File, Database, New Copy worked.
Anyone figure out what causes this problem to occur?
I’ve run in to this with no real solution. I have also had problems with connectivity when trying to move databases from one directory to another on the same server. I can do it manually with replication, but adminP refuses to do it.
Are you copying from a Lotus Notes client? You have this as a Domino Server with RedHat, but how are you copying (the medium)?
If you are copying using a client have you check to make sure you are not having problems with connectivity within that computer/client/id. I have seen a server drop an user because the client/machine had problems with idle response time. {The server was setup to stop sessions at a specific idle response time.)
I understand the server is remote, but there is not a Lotus Notes client for Linux. I am assumping you are mentioning the client from you (or his pc).
If that is correct, then yes it using the client pc to move it from the server, which is slower than a server-to-server movement.
When the LAN/WAN is slow or the database is big in size, this is not a good way to move the database. If you ssh and copy over to the other server, it is similar to doing a new replica. So if you were not wanting to do a replica I would make sure you could change the replica id of the database.
The biggest hangup here is if Lotus Notes client pc has any problems, it will result in an error.
Make a new replica instead of a copy. After about 10 seconds after creating the replica use Pause/Break to stop the replica process in your client. Now go to the server console and push the replica update with Pull servername filename. Yes, this can be the same server. After the replica is built (much faster), use Antrid to give the new replica a NEW repid. Much faster than client-based new copy. Plus you avoid this unknown issue where you “loose” connection.