If you use the catalog, you could set up a 'after documents are created or modified' agent to run with a target of 'all new or modified documents' Then you can check for each one if a replica exists, and if not, create it don't forget the loss of functionality as well.The MS environment simply can do less, and has less safety.1- If you're using the same server name, the old signature will fail and the server won't run the agent.2- Without the old server ID it'll be almost impossible to keep up with the authentication.I managed to achieve this when registering a user through Domino Policies but I would like to achieve the same results for all databases created on the server. You'll probably want to exclude say, system databases and such.
Hi, I had the same problem is an old one created date 1994 and will be valid up to 2019, they thought they do need notes just for 25 years at this time, btu we cannot certify new user. [email protected] can try my free apps for IBM (Lotus) Notes/Domino.
Unless you're preserving deletions, they are not represented.
This is why I normally enable soft deletions for a week or more -- or better yet, build my own deletion scheme.
I work with they many years and think it could be useful for somebody else. But there would be some delay in detecting the database.
The app Reports Wizard allows you to create reports using data from documents of databases IBM Lotus Notes? We need to ensure that any database created on one server is automatically created on the other server. The Notes API allows you to scan through every database looking for new databases, then replicate the database to another server.