![]() Choose how large you want the LUN to be.I recommend an “Advanced file LUN”, but the regular should work fine.Choose which volume the LUN data should be stored on.Select “iSCSI LUN (File-Level)” and click “Next”.Navigate to “iSCSI LUN” and click “Create”.A computer that will be always on which has a connection to the NAS and the internet for incoming backups.A Synology NAS (or other iSCSI target, but I will not cover the setup).Unfortunately, CrashPlan was smart enough to not allow backing up to network drives using any of those techniques.įeeling a bit adventurous, I looked into iSCSI as a solution and found my answers. I tried all the tricks you might find when Googling for “CrashPlan backup to network drive”, or similar. Therefore, I endeavored on a way to use CrashPlan to backup to my Synology in a different way. So, I promptly gave up and used Synology’s Cloud Station Backup for 6 months.Ĭloud Station Backup worked well, but I always got the feeling that CrashPlan had always worked better, especially when handling deleted files. ![]() Using CrashPlan installed on the Synology required modifying configuration files on all of the computers that I wanted to backup, instead of simply logging into my CrashPlan account as I had done before. Unfortunately, I soon found out that while the Synology can run CrashPlan after reading the tutorial from PCLoadLetter, it was not anything like I was used to for administration. When I first got my Synology DS1815+ to replace my existing file server that was using Windows Storage Spaces on Windows 10, I was excited to continue using CrashPlan to backup my family’s computers.
0 Comments
Leave a Reply. |