{"id":1891,"date":"2016-10-31T09:00:32","date_gmt":"2016-10-31T09:00:32","guid":{"rendered":"http:\/\/update.prominic.net\/?p=1891"},"modified":"2023-03-28T18:34:56","modified_gmt":"2023-03-28T18:34:56","slug":"cross-domain-database-migration-using-adminp-2","status":"publish","type":"post","link":"https:\/\/wordpress.prominic.net\/cross-domain-database-migration-using-adminp-2\/","title":{"rendered":"Cross-Domain Database Migration Using AdminP"},"content":{"rendered":"
When migrating from one domain into a new one or joining multiple domains together, it can happen that a large number of databases need to be migrated across. For more than ten or so databases it can become very time-consuming to manually create all the replica stubs, even with a scheduled replication taking care of the database population. Fortunately, the Create Replica<\/strong> function can be configured to work as well cross-domain as it does internally to one.<\/p>\n There are a number of higher-level server communication-related items to verify prior to configuring the AdminP or individual databases:<\/p>\n Part 2: Setting up outbound<\/strong><\/p><\/blockquote>\n Open the admin4.nsf<\/strong> on the origin server, then open the Cross Domain folder, then open Configuration. Click add configuration to create a new outbound admin4 config doc. On the Configuration Type<\/em>, set the type of cross-domain configuration to Outbound. On the Outbound Request Configuration<\/em> tab, enter the destination\u2019s Domino domain, check Create Replica<\/em> in the drop-down for List of AdminP requests to submit, specify the destination server name and domain, and enter the origin server in the List of approved signers. Then save and close the configuration document.<\/p>\n<\/div>\n<\/div>\n<\/div>\n Part 3: Setting up inbound<\/strong><\/p><\/blockquote>\n Open the admin4 on the destination server, then again open the Cross Domain folder, open Configuration, and click to add configuration. On the Configuration Type<\/em> tab this should now be set as Inbound. On the Inbound Request Configuration<\/em>, enter the origin server\u2019s domain into the Receive AdminP requests from domains<\/em> field, check Create Replica<\/em> in the List of AdminP requests allowed from other domains<\/em>, enter the destination server name as the intended server, and then enter the origin server in the List of approved signers<\/em>. Save and close this document.<\/p>\n Part 4: Generate the requests<\/strong><\/p><\/blockquote>\n Generate the create replica requests on the origin server as as you normally would. Be certain to specify the full name (including org) of the destination server. Run a \u201ctell adminp process all\u201d on the origin server and you should see the processes handled and then routed to the destination server. Check the admin4.nsf<\/strong> Errors -> All Errors by Date, Cross Domain -> Delivery Failures<\/em> views and the mail.box<\/strong> for adminp or delivery failures.<\/p>\n Part 5: Finish generating DBs<\/strong><\/p><\/blockquote>\n Open the destination server\u2019s admin4.nsf<\/strong> (or replicate with the server to which they\u2019d delivered then open) and you should now see the requests under Requests – > All Requests by Action<\/em>. Run a tell adminp process all on the destination server, then check that admin4\u2019s Errors -> All Errors by Date<\/em> and, if there\u2019s nothing problematic, you should then be able to start replicating immediately, after which you can remove any ACL entries added in part 1 if\/as needed.<\/p>\n<\/div>\n<\/div>\n<\/div>\n\n