hey there!

 

how smart is the mover script (and/or it's accompanied helper tools)?

i couldn't find a thread/answer in the forums, therefore i started a new one.

 

this is my situation, where it is of relevance, when files are moved into the array: CBR/DVR recordings (better said: running ones). at the moment i do use a cache only share, so all is well. but, for example when going on vacation, the cache drive would fill up quickly and boom, no more recordings.

 

now, when a recording is running, it's corresponding file will continually be written too (and so expands in size). these recordings will run equally long to the shows length (sometimes several hours) and so it'll hit the mover scripts time slot nearly every day. what does happen then?

 

1) it does recognized active files and simply doesn't move them then

2) it doesn't check for activity, starts moving it (and we'll not know if – because of live-recording and it's sensitivity to write cycles – have damages inside the file afterwards)

 

does someone do this kind of tv-recordings on share (via enabled cache in between)?

 

thx.

Blacky

 

mover cannot move any open files.

 

 

if you have your issue mainly when beiing out of reach of the system, the easiest solution would be to simply switch of the "use cache drive"option for those timeframes..

I run into this as well at times.  As stated, the mover will not move any file that is open.  So on the next run, if that file is not open, it will get moved.

 

So you have the possibility to have a unprotected file on your cache drive for almost 48 hrs

 

I have not run into a problem with this possible delay, so far and have been happy

 

Myk

 

if you add another drive into the cache pool that means the data is as-protected as your whole array.. Only issue then is the limit of the space..

True for dual cache drives, mine is dual but in raid0 mode because of 2 smaller ones and Plex's HUGE library

 

Myk

 

True for dual cache drives, mine is dual but in raid0 mode because of 2 smaller ones and Plex's HUGE library

 

Myk

 

Thats different indeed... In that case your data is even less safe then if hosted on one ssd... so do not put important stuff on there..

True for dual cache drives, mine is dual but in raid0 mode because of 2 smaller ones and Plex's HUGE library

 

Myk

 

i'm using plex quite heavily and also would recommend to use (at least) a bigger cache (ssd) and not using raid 0. speed shouldn't be an issue anyway on ssd and as you stated it's for combined total space (but at a cost of data protection). i would get a bigger one and do regular backups to the array (i do that manually now, but as i find time, will look up a automated solution: could be rsync script, docker [then being used for other backup tasks as well] or any other fitting solution).

 

Bigger SSD is on the horizon - but I had these 2 240g ones here and decided to use them in raid0 - I know the risks - which is why data from them is backed up every 24 hrs - so at the most I would loose 1 days worth of plex data or any other docker/vm stuff stored on the pool

 

Myk

 

thanks for all replies.

 

data protection is not the main concern here, these are just recordings 

 

there are several recordings at times in parallel and taking hours and hours of time (combined over the day); so i like to have the cache as (1st) storage (and that keeps the parity and at least one array drive in standby until the mover kicks in). mostly i'll finish the post-work (cropping pre- and after recording time, and do at times quite challenging cuts/blends to get rid of commercials) in time and before the mover would move them – and so use once more the advances of the sdd (cache) drive.