🔍 Read the full analysis: Choosing Storage For AI: Why We Picked The UGREEN NASync DXP6800 Pro on ThorstenMeyerAI.com
Get business pricing on monitors, keyboards and dev gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
ThorstenMeyerAI.com says it bought a UGREEN NASync DXP6800 Pro after duplicate files in an iCloud sync folder nearly filled a database server. The NAS has been equipped with four hard drives and an NVMe SSD, but is not yet connected or configured; its planned backup setup still needs to pass two tests.
ThorstenMeyerAI.com says it has bought a UGREEN NASync DXP6800 Pro to add local storage and a separate backup destination for its small AI and publishing operation, after duplicate files in an iCloud sync folder left one server with 2% free disk space. The NAS has been delivered and fitted with drives, but as of November 1, 2026, it is not connected to the network, and the planned backup system has not been tested.
The operator says the immediate trigger came on September 17, when two machines sent database dumps with the same filename to one iCloud folder. It reports that iCloud retained repeated conflict copies, eventually producing 29 duplicate files and leaving the database server nearly full. A separate backup cleanup job then timed out on October 29 while trying to remove old copies. The account describes these as problems with how copies were synchronized and managed, not evidence that the underlying database dump failed.
The NAS was bought with four Seagate IronWolf Pro 16 TB hard drives and one NVMe SSD. The planned arrangement puts the hard drives in RAID 6 for backups, with about 32 TB of nominal usable capacity before formatting and other overhead. The SSD would be a separate pool for containers and test databases. The publisher says it chose the six-bay model over a cheaper four-bay alternative mainly to leave room to add drives without replacing the existing ones.
According to UGREEN’s published specifications, the DXP6800 Pro has six SATA bays, two M.2 slots, a 10-core Intel Core i5-1235U, two 10GbE ports and 8 GB of DDR5 memory expandable to 64 GB. Those are manufacturer specifications, not performance results from the publisher’s own testing. The article says the NAS was bought with the publisher’s own money, was not supplied or sponsored by UGREEN, and is not being presented as a completed review or long-term test.
Infographic 01 · The box
Six bays, two fast slots, two 10GbE ports
What UGREEN lists for the NASync DXP6800 Pro, and how we plan to fill it.
How we fill it
Delivered and equipped; the setup is our plan (1 Nov 2026)
Bays 1–4: Seagate IronWolf Pro 16 TB, RAID 6, Btrfs → ≈ 32 TB usable, any two drives may fail. Bays 5–6: free for growth. M.2 slot 1: the NVMe SSD (ordered: Samsung 990 Pro 1 TB) as its own fast pool. Slot 2: free. Six 16 TB drives in RAID 6 would give ≈ 64 TB.
What else UGREEN lists
From the product page, not measured by us
- Separate 128 GB SSD for the operating system, UGOS
- RAID: JBOD, Basic, 0, 1, 5, 6, 10
- 1× PCIe x4 · 2× Thunderbolt 4 · 8K HDMI · SD card reader
- Power: 43.07 W drives in use · 24.91 W drives in hibernation
- Stated maximum: 208 TB with 32 TB drives · 3-year warranty
Why six bays: with RAID 6, two drives always hold parity. In four bays that leaves half the raw space usable; with all six bays filled it becomes two thirds.
Sources: UGREEN DXP6800 Pro product page, checked 1 Nov 2026; Seagate IronWolf Pro data sheet DS2129.4; our setup plan, 6 Oct 2026.
Powered by Thorsten Meyer AI
A Local Copy for Faster Recovery
The purchase addresses a practical distinction between file synchronization and independent backup. A sync service can replicate changes, including unwanted changes or duplicate files; it does not automatically provide a protected recovery point. UGREEN’s help material, as cited by the publisher, says deletion in one location can also delete a file in the other during two-way sync.
A local NAS could give the operation a separate place to store backups and restore large volumes without first downloading them over its internet connection. The publisher reports a current backup requirement of roughly 6 to 8 TB, based on measurements of its computers and data. It also describes recurring kernel panics on its database Mac; a NAS would not prevent a crash, but a nearby copy could make recovery quicker. Whether it does so reliably remains untested.
The planned safeguards also reflect the risk of putting essential data and backup controls on one networked device. Separate accounts and quotas, snapshots that ordinary backup accounts cannot manage, and an encrypted offsite copy are intended to reduce the chance that routine errors or compromised credentials can remove every copy. These are design goals, not protections the publisher has yet verified in operation.
Popular right now
Bose QuietComfort True Wireless Noise-Cancelling Earbuds, Black
Shark Rocket Ultra-Light Corded Stick Vacuum, HV301, Gray/Orange
Dyson Car+Boat Cordless Handheld Vacuum
As an affiliate, we earn on qualifying purchases.
How the Backup Plan Developed
The publisher describes a small fleet of Macs rather than a data-center environment: one machine hosts its main Postgres database, another serves local AI models, and others run publishing pipelines and tests. Measurements taken on October 6 put data use at about 2.6 TB on the main desk machine, 744 GB on the database server, and 3.2 TB on the model server. The database itself was about 293 GB; much of the model storage consists of files that can be downloaded again.
That distinction shapes the proposed layout. The publisher says its immediate backup requirement is about 6 to 8 TB, while model files that can be replaced are not the same priority as publishing data and databases. It also wants test databases off its work laptop, where a Docker virtual disk had grown to around 30 GB, according to its account.
The article invokes the 3-2-1 backup rule, described in a US-CERT guide as keeping three copies of important data, on two types of media, with one copy offsite. Under the proposed plan, each Mac would back up using a separate non-admin account with a quota; daily snapshots would be inaccessible to those accounts; and an encrypted copy would go to Backblaze B2 using restic, with Object Lock intended to prevent deletion. The existing arrangement remains in place until rollout: local Time Machine disks on two Macs and an iCloud copy of the nightly database dump.
“That was the day I stopped treating a sync service as a backup.”
— Thorsten Meyer, ThorstenMeyerAI.com
Deployment Tests Still Pending
The NAS has not yet been placed on the network or configured, and the two stated acceptance tests have not run. It is therefore not known whether the device will accept Time Machine backups under the intended account restrictions or keep snapshots protected from those accounts. The publisher says it will return the NAS if either test fails.
Other operational details also remain unverified. The planned RAID 6 capacity is an estimate; real available space will depend on formatting and system overhead. No measured restore times, noise levels, power use, or sustained network speeds are available. The publisher also has not reported how the proposed snapshot schedule and Backblaze Object Lock configuration will perform in practice.
The article says the NAS will not host a live database change log on spinning disks, give admin credentials to AI agents, be exposed to remote internet access, or use UGREEN’s cloud mirror as its offsite backup. Those are stated limits of the plan, not independently confirmed configuration outcomes. Until setup and testing are complete, the publisher’s current backups still rely on its existing local Time Machine disks and iCloud copy.
Acceptance Tests Before Rollout
The next step is to connect and configure the NAS, then test whether a Mac can use Time Machine with a non-admin account and whether daily snapshots remain inaccessible to that account. The publisher says both tests must pass before it keeps the device. It has not given a date for those tests or for the start of routine backups.
If the checks pass, the proposed rollout would assign the four hard drives to a RAID 6 backup pool and use the NVMe SSD separately for containers and test databases. Disk-heavy work is planned for 8 p.m. to 6 a.m., with the aim of letting the drives sleep during office hours. The publisher says it will report real-world results after the NAS is running; until then, performance and recovery benefits remain expectations rather than findings.
Key Questions
Why did ThorstenMeyerAI.com buy the UGREEN DXP6800 Pro?
The publisher says repeated conflict copies in an iCloud folder nearly filled its database server. It wants a local backup destination and additional storage for containers and test databases.
Is the NAS already backing up the company’s computers?
No. As of November 1, 2026, it had been delivered and equipped but was not connected or configured. The publisher says its existing Time Machine and iCloud backups remain in use.
What storage setup is planned?
The plan is to use four 16 TB hard drives in RAID 6 for backups, with an NVMe SSD as a separate pool for containers and test databases. The estimated usable hard-drive capacity is about 32 TB before formatting and overhead.
What must happen before the publisher keeps the NAS?
It says the device must pass two checks: Time Machine must work with a non-admin account, and snapshots must remain protected from that account. Neither test has run yet, and the publisher says it will return the NAS if either fails.
Does this report establish how well the NAS performs?
No. The publisher says this is not a review or long-term test. It has not reported measured transfer speeds, restore times, noise, or power use, and says it will report results after setup.
Source: ThorstenMeyerAI.com
