Search the Community
Showing results for tags 'suggestions'.
Hi, Sorry if this is not in a suitable location, but I couldn't find a suggestions option. Would it be possible to implement a auto-tiering option in some way? E.g. automatically use fast storage as primary and slow storage for secondary duplicates? That way something should always come off say NVMe first, followed by SSD, SSHD and traditional HDDs. I only ask, because by default my duplication goes across HDDs and the performance is... as you would expect! Alternatively, some way of using the faster disks as "caching" drives - perhaps based on frequency of file access or just
Im currently planning to have 2 pools with a few drives each and no duplication on either. Im wondering how backup and recovery can be accomplished with this setup. Specifically, id like to answer 2 questions: 1. How can I recover only missing files (with the correct folder structure) from a backup in the event of drive failure. (programs, suggestions and/or anecdotes welcome, Im trying to find the optimal solution) 2. How long can a secondary pool made for offline backup stay without being updated/connected? WIll future updates make older pools unreadable and if so