Moving .appdata from cache to new pool

[Omid]

Unraid 6.11.5

Docker ✅

VMs ❌

 

I'm still using the /mnt/cache/.appdata approach for my appdata (rather than using a Share) and am happy to continue with this, but I'd like to move my appdata to a new NVMe-backed pool that I'll be creating. My appdata includes my Docker image. If I recall correctly, some folks had experienced permissions related issues when doing something similar. I'd like to avoid such a situation and am evaluating my options.

My structure is:

---- /mnt/cache/
---- ---- .appdata/
---- ---- ---- apps/
---- ---- ---- docker.img
---- ---- Share1/
---- ---- Share2/

 

Am I okay to just stop Docker, rync the entire appdata directory, update configs and start the array? I could actually start the copy with rsync (excluding image) whilst everything is still running, just to get the bulk of it copied, and then switch off Docker and repeat the command (including image) to get the delta copied over [Option 1].

 

My appdata is only ~90GB but there are lots of small files which makes these operations slow.

 

I am aware of the Share and Mover approach to do this, but wanted to avoid any risks (to system/share config) that might come if I convert this dot-folder to a Share folder on the cache drive. This incurs more downtime of Docker, as you'd have to wait for Mover to fully complete the move in one shot before starting everything up again. It's also a move and not a copy [Option 2].

 

EDIT: Use CA backup and restore and manually move my Docker image [Option 3].

 

EDIT: Could I convert my single 500GB SATA SSD Cache pool into a new AppData pool of two drives, with one 1TB NVMe? Let Unraid do its thing to mirror the data, then replace the 500GB SATA SSD with the second 1TB NVMe. [Option 4] Doh! My current Cache drive is xfs.

 

Thanks in advance for any thoughts and inputs!

Edited May 7, 2023 by Omid
Added Option 4

[Omid]

Bump 🙂