Urgent Clarification

Lotus Domino
Platform Issues
Hi All., I would like to know what is the difference between COPYING A DATABASE FROM THE SERVER TO THE LOCAL MACHINE & REPLICATING THE DATABASE FROM THE SERVER TO THE LOCAL MACHINE - irrespective of the Domino and notes client version. 1) Will I be able to use the database from the local machine after copying? 2) If So what is the difference betweent the both, and How? 3) If Not What is the specific Reason.? Pls mail me urgently to unni.sudevan@wipro.com... awaiting your mails. Pls Frnds Help me out. I know some people will ask me y and for what.. I will explain later... But do reply me... Reg KochuBaby

Answer Wiki

Thanks. We'll let you know when a new response is added.

Yes, a File cope is the same as a new replica.

If the server replica is encrypted with the server ID, you will not be able to use it locally.

If “Enforce A Consistent ACL” is selected in the advanced ACL settings, then you may have difficulty using it locally. If you do a one way server-to-local replication, the access on the local replica may be updated and allow local access.

When you first access the database locally, your notes client will perform a consistency check, which could take a while if the database is large.

You might also want to run ncompact.exe and nupdall.exe on it before trying to open it with your client.

Discuss This Question: 4  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • Freedom
    Not to be rude, but replicating a database to your PC is not the same as copying it. When you replicate, Lotus Notes will try to update the replica each time you open it or connect to the LAN. (unless you change the settings to stop it). This takes up PC resources and slows processes until the replication is done. Unless you have a chancy LAN connection or a stand alone PC or Laptop, I would think twice before replicating any database to my PC.
    10 pointsBadges:
  • Jlnewmark
    The way I explain to users is that a copy is a snapshot: it takes the file as it is in that moment and copies it. Once done, it is never updated. A replica is dynamic -- it is updated by the server copy to keep it current either by automatic process (i.e., every 60 minutes, Monday thru Friday) by the replication settings, or manually (File --> Database -->Replication --> Replicate). You can also use the replication settings to have it automatically update when Notes is opened or shut down. A lot depends on how you want to use the information. If it's a mail database, you can't send or receive without a connection to the server, obviously. If it's another kind of database and you are working on a copy, that work never gets back to the original. It's basically on your harddrive or network drive, wherever you chose to put it, and the original on the server is independent of it. If the two are replicas, your work updates the server as you replicate. And any work that anyone ELSE has done on the server database or their OWN replica also updates YOUR replica. Have I thoroughly confused you? I hope not, and I hope this helps. We use both copies and replicas a lot in our company, so I've had a fair amount of experience with them, although mostly on mailfiles, I confess. Nonetheless, all Notes databases have the same basic workings.
    0 pointsBadges:
  • Brooklynegg
    Replication is one of the major strengths of Notes. There is almost no danger in making local replicas, unless there is relational code that that does lookups to databases that it assumes would be on the "same" server, which in the case of a local replica, would be your own machine. Of course, if replica IDs are used for these lookups, then they won't break on a local. For instance, we have about 100 users of a large fraud management database that all use local replicas. The local replicas have replication formulas that bring in only the case for their region, making the local replica much more responsive in many way. I also do a lot of development on my local replicas and replicate the changes to the server when ready.
    3,845 pointsBadges:
  • Deadleaves
    Just to be absolutely clear, there are 3 ways to get a database from a server onto your local PC: 1. Use FileReplicationNew Replica ... to create a replica of the database on your PC. This will periodically replicate with the server copy to keep it completely "in sync". To all intents and purposes the 2 copies will be identical. 2. Use FileDatabaseNew Copy ... to create a one-time copy of the database on your PC. This is NOT a replica and will only be a copy of the database at that moment in time and will NOT periodically replicate with the server copy to try to stay in sync. 3. Use Windows Explorer to make a copy of the database on your PC. This will ALSO be a replica because both files will be internally identical and will therefore have the same "replica id". However, unless you specifically set it up replication will not be automatic. This method is not the most sensible way of creating a replica. The Notes way is best if at all possible. In terms of being able to "work with" the new local database, this is completely dependant on what the database is, how it was designed, how the security has been set up for it etc. etc. In general when I want to make sure a database works exactly the same whether locally or on server I set "Enforce consistent ACL across all replicas". This makes sure the the use of ACL "roles" will still work when local and security will still function correctly for each user. However, I suspect this is getting beyond your question into designer fundamentals and if you don't know the difference between a database copy and a database replica you're a long way from these more esoteric aspects!
    0 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: