Hi,

I have setup a cache SSD as \primary_cache and created a share called laptopA-documents.  I'm copying files from Laptop A into the primary_cache\laptopA-documents\ and let mover (Unraid 7.0.0 2025-01-09 version) run overnight to move them into the Array; however, mover is moving the directory and files to the array leaving \primary_cache totally empty.  This poses a problem as my backup software is looking specifically for \primary_cache\laptopA-documents\ and fails the next day.

 

In researching a bit, I 'think' v6.12 has mover actions for 'files only', or something like that.  Has that been removed from v7.0.0 or am I missing a configuration?

 

NOTE:  I am NOT using the Mover Tuner plugin.

 

Thanks,

Glen

 

 

Mover has always worked that way and almost everyone would complain if it didn't

2 hours ago, trurl said:

Mover has always worked that way and almost everyone would complain if it didn't

Understood - I'm very new to Unraid (coming from Synology) and was trying to setup writes from multiple laptops to the SSD cache pool and then move them to the HDD array later.  But I need to keep the laptop files 'segregated' by laptop, obviously.  Don't think the SSD cache w/mover will help me here, but again - learning.

if that is the case why not map the backup to /mnt/user/laptopA or something similar instead of directly to the cache? if "laptopA-documents" is a share configured in unraid to write to cache then move to the array, it will behave the way you expect and write to the SSD, then move later to the array, but the file location you hit never actually changes so the directory is always there.

 

Also why not just configure one "backups" share then have subfolders within that for your devices? that keeps it all cleaner and lets you change settings on one master share instead of a bunch of separate shares for each device.

I think I have read in the forum that if you create a dot file (e.g. '.DoNotRemove') on the pool in the share folder that mover will ignore that file and the folder and the share folder then remain present.   Not tried it myself so would like confirmation if I am correct.

@Faceman - I only sort of follow what you are saying.  Creating a 'backup' folder with 'laptop A' and 'PC B' in side can certainly be done; however, my PC has all my raw video footage and created videos, which include raw photos and music files.  The idea was to utilize the SSD cache pool to write new raw video files (very large) as I get speed gains and write to the HDD array later.  Using backup software like EaseUS, Macrium, Bvckup 2, etc. (not picked one yet), they can be used to copy a full library over initially and on next runs copy new/updated/deleted files.  If the files are moved off the SSDs to the array, as expected, I'm not sure how the backup software would make that determination - it would merely copy everything to the SSD on every run.  Of note, the SSDs are 2TBx2 (redundancy) but writing to a 18TB array, so the SSDs have limited space and couldn't hold a full copy of existing raw video files.

 

The 'laptop A' would contain the normal Windows created folders, Desktop, Pictures, Videos, Documents, and Downloads and don't have to write to the SSDs first, so the backup software will be able to copy new/updated/deleted files.

 

Thoughts?

Glen

Actually I want mover to also remove the source folder from cache, which it normally did and now it doesn't and I don't know why.

 

Just now, NLS said:

Actually I want mover to also remove the source folder from cache, which it normally did and now it doesn't and I don't know why.

 

You should start your own thread with your Diagnostics.

I finally figured out the issue.  On my backup program I was entering mynas.local\primary_cache\laptopA-documents\.  I changed that to the share name of mynas.local\laptopA-documents so the Unraid process can do its magic between the cache SSD drive and the HDD drives.