It's also worth noting that -exclude accepts expressions. Therefore we have to cut the leading slash (/) from the exclude tar -cvf /tmp/foo.tar -exclude="foo/baz" foo Oh, what the he., why this? Because we supplied a relative path to tar to archive, not an absolute one.
#MOVE SABNZBD TO NEW COMPUTER ARCHIVE#
Now we want to archive foo without the baz cd tar -cvf /tmp/foo.tar -exclude="/foo/baz" foo A simple example to what's the deal with exclude-option in tar, let's assume the ls Tar -cvzf /mnt/v1/backup/Plex/ -exclude="Cache/*" plexdata Second, as in your command line, if you supply a relative path to tar, the exclude parameter also works on relative paths. Always - read again: ALWAYS - supply -f as the last option to tar, because the following parameter will be the resulting file name. First, the posted command line will result in an archive called z. tar is really picky when it comes down to options and parameters. The error above occurs because your tar options are in the wrong order. That's really it?Īre cron jobs really only 1 line only? So if you'd want to automate it you need 6 + lines?įreenas cron: _secure_path: /mnt/v1/media/.login_conf is not owned by uid 816Ĩ16 is just my media user. I didn't realize Sickrage only needed a config.ini backed up.
tar xvfz /mnt/VolumeData/Backup/FreeNAS/Plex/ /mnt/VolumeData/jails/plexmediaserver_1/var/db/.tar -cvfz /mnt/VolumeData/Backup/FreeNAS/Plex/ /mnt/VolumeData/jails/plexmediaserver_1/var/db/plexdata/.cp /mnt/VolumeData/Backup/FreeNAS/SickRage/config.ini /mnt/VolumeData/jails/sickrage_1/var/db/sickrage/.cp /mnt/VolumeData/jails/sickrage_1/var/db/sickrage/config.ini /mnt/VolumeData/Backup/FreeNAS/SickRage/.cp /mnt/VolumeData/Backup/FreeNAS/CouchPotato/nf /mnt/VolumeData/jails/couchpotato_1/var/db/couchpotato/.cp /mnt/VolumeData/jails/couchpotato_1/var/db/couchpotato/nf /mnt/VolumeData/Backup/FreeNAS/CouchPotato/.
Tar xvfz /mnt/VolumeData/Backup/FreeNAS/Plex/ Tar cvfz /mnt/VolumeData/Backup/FreeNAS/Plex/ plexdata This quick guide is not intended for "noobs", but is for at least Tier 2 level skilled technicians.ġ ) In the FreeNAS GUI create a dataset for backupsĢ ) In the FreeNAS GUI create a Share linked to the Backup dataset you just createdĪssuming you already have CouchPotato, SABnzbd, SickRage, & Plex installed and configured.ģ ) Create the following folder structure in your "Backups" datasetĤ ) In the FreeNAS Shell, run the following comands:Ĭp /mnt/VolumeData/jails/couchpotato_1/var/db/couchpotato/nf /mnt/VolumeData/Backup/FreeNAS/CouchPotato/Ĭp /mnt/VolumeData/Backup/FreeNAS/CouchPotato/nf /mnt/VolumeData/jails/couchpotato_1/var/db/couchpotato/Ĭp /mnt/VolumeData/jails/sabnzbd_1/var/db/sabnzbd/sabnzbd.ini /mnt/VolumeData/Backup/FreeNAS/SABnzbd/Ĭp /mnt/VolumeData/Backup/FreeNAS/SABnzbd/sabnzbd.ini /mnt/VolumeData/jails/sabnzbd_1/var/db/sabnzbd/Ĭp /mnt/VolumeData/jails/sickrage_1/var/db/sickrage/config.ini /mnt/VolumeData/Backup/FreeNAS/SickRage/Ĭp /mnt/VolumeData/Backup/FreeNAS/SickRage/config.ini /mnt/VolumeData/jails/sickrage_1/var/db/sickrage/Ĭd /mnt/VolumeData/jails/plexmediaserver_1/var/db/ Obviously you can change any of the datasets or folder names are you please, below is what I did.
#MOVE SABNZBD TO NEW COMPUTER TV#
I have 1k+ movies and 30+ tv shows on my plex and it took about twenty minutes making the backup 9Gb. Be warned, depending on how many multimedia items you have added to Plex will affect how long it will take to backup. The following commands will backup the configs/settings for CouchPotato, SABnzbd, SickRage and the configs and database for Plex. I spent too many hours gathering this information, so why not share it to help you.
0 kommentar(er)
