Current Constraint and Migration Goal
eSync currently runs on a laptop, and local disk capacity is becoming the limiting factor. The proposed migration would move database storage to MySQL in Azure and use an Azure Web Job to pull data from DataMailbox. The evidence does not confirm that eSync supports either deployment model.
Separate the Two Architecture Decisions
| Decision | Confirmed | Unknown |
|---|---|---|
| Move eSync data to MySQL in Azure | MySQL in Azure is the proposed storage target. | Whether eSync supports a remote MySQL database, which schema it requires, and whether latency or connectivity constraints apply. |
| Replace eSync with an Azure Web Job | The intended function is pulling data from DataMailbox. | Whether DataMailbox exposes a supported interface for this design and whether the Web Job can reproduce all required eSync behavior. |
| Run eSync itself in Azure | eSync currently runs on a laptop. | Whether its runtime, storage, scheduling, and operating-system requirements are compatible with the selected Azure service. |
Do not treat these options as interchangeable. Redirecting eSync storage, hosting eSync remotely, and implementing a new DataMailbox client are three different designs with separate support and validation requirements.
Qualification Procedure
- Record the laptop's current eSync storage location, database type, data growth, and required retention. This establishes whether storage expansion alone solves the immediate problem.
- Confirm through official product documentation or the manufacturer's support channel whether eSync can use a remote MySQL database. Do not create or modify a production schema until the required database structure and connection method are confirmed.
- Confirm whether eSync can run unattended in the intended Azure hosting environment, including its runtime, scheduling, persistent-storage, and network requirements.
- If building an Azure Web Job instead, obtain the supported DataMailbox interface requirements and identify every eSync function that the replacement must preserve.
- Validate the selected design with non-production data. Verify successful retrieval, duplicate handling, restart recovery, database growth, and agreement with the laptop's results before cutover.
Engineering Decision
The available evidence contains only an unverified opinion that the Azure approach may not be possible; it does not establish a product limitation. Keep the laptop installation in service until the manufacturer confirms the intended architecture and a controlled test proves equivalent data retrieval and storage.
If remote MySQL or Azure hosting is unsupported, address the immediate disk constraint by changing the local storage arrangement only through documented eSync configuration. Do not move database files manually unless the product documentation explicitly supports that procedure.
FAQ
Can eSync use a MySQL database in Azure?
The evidence does not confirm remote MySQL support. Verify the supported database type, schema ownership, and remote connection method through official eSync documentation or the manufacturer's support channel.
Can an Azure Web Job pull data from DataMailbox?
That architecture is proposed but not validated by the evidence. Confirm the supported DataMailbox interface, authentication requirements, and required eSync-equivalent functions before implementation.
How should I move eSync off a laptop with low disk space?
First measure storage growth and retention needs, then qualify remote database support, Azure runtime compatibility, or a replacement DataMailbox client as separate options. Cut over only after non-production testing verifies retrieval, duplicate handling, restart recovery, and database growth.