Menu
Delete All Files Except Windows
PRE-REQUISITES
- Rsync plugin
- User Scripts plugin (if you want to schedule the jobs)
- Unassigned Devices plugin
RSYNC TO UNASSIGNED BACKUP DRIVE
I often configure rsync jobs to backup critical data to an unassigned drive outside the array. My scheduled job looks something like this:
RSYNC TO ARRAY BACKUP DRIVE
I read about a very interesting alternative backup approach with UnRAID. Instead of creating an unassigned drive to use for the backup, you actually add it to your array. Configure your shares to never use this drive. The idea here is that the backup drive will be a member of the array, but completely excluded from any and all shares. Then setup an rsync job like this:
* Where disk4 is your backup disk.
An advantage to this approach is that the backup drive is an array member, so it's protected by parity. A disadvantage is that the drive is an array member, so it's not as easy to just pull the backup drive out if necessary. One scenario that comes to mind is if you want to rotate the backup drive with another one (e.g. off-site). Physically pulling the drive would affect the array and parity would have to be rebuilt. It would be easier to use an unassigned drive in that scenario.
- Rsync plugin
- User Scripts plugin (if you want to schedule the jobs)
- Unassigned Devices plugin
RSYNC TO UNASSIGNED BACKUP DRIVE
I often configure rsync jobs to backup critical data to an unassigned drive outside the array. My scheduled job looks something like this:
rsync --archive --delete /mnt/user/SourceFolder/ /mnt/disks/TOSHIBA_MD05PBA60_1900876554/DestinationFolder/
RSYNC TO ARRAY BACKUP DRIVE
I read about a very interesting alternative backup approach with UnRAID. Instead of creating an unassigned drive to use for the backup, you actually add it to your array. Configure your shares to never use this drive. The idea here is that the backup drive will be a member of the array, but completely excluded from any and all shares. Then setup an rsync job like this:
rsync --archive --delete /mnt/user/SourceFolder/ /mnt/disk4/DestinationFolder/
* Where disk4 is your backup disk.
An advantage to this approach is that the backup drive is an array member, so it's protected by parity. A disadvantage is that the drive is an array member, so it's not as easy to just pull the backup drive out if necessary. One scenario that comes to mind is if you want to rotate the backup drive with another one (e.g. off-site). Physically pulling the drive would affect the array and parity would have to be rebuilt. It would be easier to use an unassigned drive in that scenario.
Unraid 6.8 Delete Share
Unraid Delete Share Photos
Jul 01, 2016 Here is what my default unRAID web GUI looks like I've got seven drives. Data drives 1-5, a parity drive, and a cache drive. I'm going to pretend that disk3 (located from the shell at /mnt/disk3) is the drive I want to remove. For my setup, I've got all my files located in user shares (from the shell /mnt/user. When the share is empty, go to the shares tab and you click the share and they'll be at the bottom a 'delete' checkbox Doing via Krusader should have worked. Delete the shareName from /UNRAID/user/shareName Alternatively, from the command line, rm -rf /mnt/user/shareName. Edited February 17, 2018 by Squid. Nov 27, 2018 The user shares are just the aggregate of all top level folders on cache or array, so any top level folder on cache or any array disk is automatically a user share named for the folder. If there isn't a specific.cfg file for a particular user share in config/shares, that user share will have default settings, but it will still be a user share.