We’re trying to figure out a way to ensure personal contacts get backed up each night on the server without user intervention.
We’d prefer not to make every single user in the organization Roaming. Surely there’s another way to allow them to keep their personal NAB on the server and to access it that way without always having to replicate.
When installing Notes, choose the C: Drive for the Application but a Network drive for data. This was how we did roaming in the old days. The potential drawbacks… The connection needs to be fast enough to support the number of concurrent users.
Have your login script copy names.nsf to the user’s home drive daily. The drawback - sometimes these files can be large and may delay the logon process.
Replicate the user’s address books to the server. You might encounter some rights issues, (temporarily allow them to create new replicas on the server).
We decided on option 3. - we had to (temporarily)change the server document to allow users to create new databases and create replica databases.
Then we created a new copy of the data base (the local address book) on the server. We deleted the curent address book icon on the bookmark bar and created a new one that points to the server address book.
user “synchronizes” their personal directory by use of the agent called “Synchronize Address Book” …. the result of this action will be the personal directory contact entries will be written to the user’s server based mail database to a hidden view ($Contacts) ……
in reverse motion, contact entries made under DWA will also be written to the user personal directory on their local workstation…
hence the term “synchronization” …
assuming you are backing up the server based mail databases with regularity, there is the backup copy you seek.
if you ever have to recover a user mail database from backup, re-instate the file to Domino, then have the user access it with their Notes client and re-run the agent “Synchronize Address Book” …