This article explains how to migrate your Domino servers using Cloudiway.
Lotus Notes migration: how does it work?
The migration is entirely monitored and triggered from the Cloudiway SaaS platform. However, a local agent must be downloaded and executed on one of the local Lotus Notes workstations.
The local agent connects to the Domino server, dumps the mailboxes, zips them to preserve bandwidth and uploads them to Cloudiway. Cloudiway then pushes the mailboxes to the target.
Requires Lotus Notes client version 8.0 or later (it probably works on 7.0 client but has not been tested).
Requires Dotnet framework 4.0.
RAM: 4 Gb. The Notes client is a 32-bit application and is limited to 4 Gb of address space.
Hard drive: Min 50 Gb free.
The Agent should be able to reach the site apps.cloudiway.com on the port 443. No any extra IP addresses needed to be authorized.
Simply launch the agent on one Lotus Notes client configured with a notes.id that has access to all mailboxes.
Periodically, the agent wakes up and queries Cloudiway for migration jobs to launch.
When the administrator selects a user and clicks on “Start Migration”, the user gets marked as “AgentScheduled”. The agent then picks up this user and starts to migrate the user’s mailbox.
The agent is multi-threaded and can concurrently run 10 migrations by default.
You can run the agent simultaneously on different Lotus Notes clients to increase throughput.
To preserve your bandwidth, you can also limit the number of concurrent migrations
All functionalities of the Cloudiway migration platform are available, including:
- delta pass migrations;
- migration to online archives; and,
- migration between dates.
The agent uses the notes.ini to select the notes.id to use to connect to the Domino server.
All you need to do is launch your Notes client and connect to the Domino server with a notes.id of your choice. This notes.id will automatically be used by the agent.