Migration Strategy from one DS1819+ on DSM6.2.4 to another DS1819+ on DSM7.2

[SIW1973]

Having just purchased another DS1819+ second hand I'm now going to move my current DS1819+ from DSM6.2.4, 18TB SHR based on EXT4 and 7TB Raid 0 BTFRS, to the new DS1819+ on DSM7.2 solely on BTRFS.

As the two boxes built will be in different locations, and as a SOHO I don't access to Dark Fibre I can't use High Availability, I would like to set them up as mirror images that can be switched over relatively simply using CloudFlare DNS to execute the switch.

As I'm using the new box to build from scratch I thought I would get some best practice when building the Storage Pool / Volume Structure to optimise the disks I have.
I currently have the following use cases :

1. Personal / Work Document File Storage
2. Film storage for Plex Server hosted on a separate box
3. Photo Storage (will move to Synology Photos), backing up 3 mobile phones
4. 5 camera Surveillance Station (2 with 24x7 recording)
5. Docker containers hosting Minecraft Servers using Snapshot Replication of Docker Files
6. Virtual Machine Manager hosting a vDSM with VPN traffic for Download Station
7. DNS Server for a number of non core Domains (will probably move to Cloudflare)
8. MailPlus Server which is core mail server for 4 people
9. WebStation / Wordpress hosting a low traffic / dollar website but with various plugins including eCommerce
10. Active Backup for Business backing up 5 PCs and 4 Vmware Workstation Remote Desktops
11. VPN Server used on occasion for devices, but always to link boxes between locations
12. Central Management Server linking both boxes and a couple of other DSs in the family

I was thinking of having low read / write elements (1,2,3) on one SHR1 Storage Pool and all other items split on 1 or 2 other Storage Pools with backup levels based on data criticality. Any views on whether this is the correct strategy let me know.

Connection between Active and Passive would be a 20MB Up / 250MB Down, but I could move to a 1000MB Up / 250MB Down connection.

With respect to the "Passive" box I was going to mirror the "Active" box as much as possible, and I'd like to not have to faff around in "unpacking" backups in bringing back core functionality such as items 8&9 and to an extent item 1. I'd be open to any suggestions in how to use Active Backup for Business, Snapshot Replication and HyperBackup to achieve this !

 

[Rusty]

Welcome

Not sure I got the idea in terms of the new box vs the old one. So you are not moving the drives from the old box, but rather setting up the new one with new drives? If so, what are they?

Considering the use cases it will come down to utilization and the type of drives that will be running all this. Separating volumes is a welcome move but again, depends on the drives, setup, and utilization.

While Hyper Backup is an actual backup tool it will depend what kind of RTO/RPO is acceptable when recovering. For a near zero values you will want to use Snapshot Replication but ofc it is important to note that SR unlike HB is not a backup tool, just a snap tool. Still, it has a lot of potential.

Any root folder that you want accessible on the passive side (and active for that matter) should hold data that can be reconfigured on the application end to be aware of any failover that happens. for example, Docker containers are great in those situations.

ABB while it will be used for all the cases you have listed will also benefit from SR. With it, you can replicate the ABB archive(s) to the secondary node and have it on standby in case something happens and you need to relink and active ABB on the passive.

All in all, the idea of having near HA scenario with identical devices will work, it just comes down to drive combination and service configuration on top of it.

 

[Coop777]

I may be wrong on this, but I believe you need to have the source NAS updated to DSM 7.2 to migrate....