Is there a process where I can move my appdata, domains, isos, system, and temp from my first cache pool to a new cache pool? 

 

My first cache pool is btrfs and only 1.6TB.

My new cache pool is zfs and 2.8TB.

 

I'm having problems with Sonarr's sqlite DB getting corrupt, and the answers I keep finding at to move it to a zfs cache pool. 

 

I found this that explains it for 6.2, dated way back in 2016, and I'm fairly certain there is a better way. I just don't want to screw up. 

 

If you are using v7 you can move directly from one pool to another, with v6 that link is still a good way

Do I change "Primary storage" from my 1st cache pool to my new cache pool and click 'done', followed by manually running mover? or do I have to do some blood ritual (aka whatever obviously easy way you are referencing). 

One pool as the primary storage, the other as secondary, and the mover action set to the direction you want.

 

Also, don't forget to disable VM and Docker services before moving.

I appreciate the responses. To make sure I have it correct, I'm going to do the following:

 

• isos share (test)
  • currently 'cache' is primary, array is secondary. 
  • set 'cache2' as secondary
  • mover action cache -> cache2
  • run mover
  • confirm /iso is empty on cache pool
  • configure cache2 as primary and array as secondary
  • run mover (I suppose I don't have to do this step)

the only difference being when I go to move appdata/etc that I disable docker services. 

 

Anything I'm missing in that plan?

10 minutes ago, Ozbarge said:

configure cache2 as primary and array as secondary

If you do that, isos will be moved to the array later, is that what you want?

That's the way it's configured now, I suppose I don't need to do that step for isos and could just leave it on cache2 (actually called 'samsungevocache'; was just trying to leave it generic for the next poor soul who finds this searching)

 

Looking at appdata I would do my same steps above, only making sure my mover action went from array->cache to cache->cache2 to do the move and then change primary to cache2, secondary to array, mover action as array->cache2. 

 

21 minutes ago, Ozbarge said:

the only difference being when I go to move appdata/etc that I disable docker services. 

appdata and system shares need Docker disabled. domains and system shares need VM Manager disabled. Assuming you are using the default storage locations in your Docker and VM setups.

Just now, trurl said:

appdata and system shares need Docker disabled. domains and system shares need VM Manager disabled. Assuming you are using the default storage locations in your Docker and VM setups.

I don't have any VMs at the moment, but understood about Docker. My only container not using the default location is Plex, as I followed a recommendation from the forums to point it's appdata to "/mnt/cache/appdata/plex" instead of "/mnt/user/appdata/plex/". Once mover copies the data to cache2 then I'd have to edit my Plex container to point to the new location before starting it. 

10 minutes ago, Ozbarge said:

That's the way it's configured now,

By default it's cache prefer, meaning mover action, array to pool, you likely only want to use a pool, but if you select the array as secondary, make sure to set mover action array -> pool