Jump to content

Some shares drop soon after array starts


Wolfe

Recommended Posts

The usual way is to have appdata and system (and maybe domains) all on cache (or some pool) and set to stay there. If they are on the array docker/VM performance will be impacted by slower parity array, and they will keep array disks spinning since there are always open files. You have to disable Docker and VM Manager and have these shares set to cache-prefer before mover can move them to cache.

 

You can have redundancy for cache (or pool) by using multidisk btrfs raid for the pool.

 

You can schedule backups of appdata and libvirt.img using CA Backup plugin.

 

Don't know anything about Time Machine.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...