If CrashPlan is installed for All Users-the default-then it cannot see the network drives mapped by a specific user, since it is running as a “system” application. If it does not work for you, continue with the following steps. I did not get a chance to verify that this works.
DROBO CRASHPLAN WINDOWS
According to CrashPlan’s own document, “ Backing Up A Windows Network Drive,” CrashPlan can be reinstalled per-user rather than for all users, system-wide then the CrashPlan application will recognize the users’ network drive mappings. Thus, network “shares” need to be mapped as local drive letters in order for the Windows version of CrashPlan to recognize them.Īfter getting my system working, I realized that I did not have to do any of the steps I documented below. Allow CrashPlan to backup NAS volumesĬrashPlan requires that files and directories being backed up, in Windows, be accessible via drive letters. Now that we have a way to see all the NAS’s content via a single share, we can configure CrashPlan to back it up. And/or you may need to reboot Windows or restart Workstation in order for Windows to not be confused about user permissions (if you changed any).You may need to reboot the Drobo for this to work correctly.Replace Drobo’s expected directory with a symbolic link to the pointing to the parent directory of all the directories that are the source of each share:.
![drobo crashplan drobo crashplan](https://prometheus.med.utah.edu/~bwjones/wp-content/uploads/2010/10/Wall-o-Drobo.jpg)
![drobo crashplan drobo crashplan](http://thephotobrigade.com/wp-content/uploads/2015/03/Brady_Oshiro_in_my_bag_7.jpg)
One of the advantages of online backup service, CrashPlan, is their ability backup NAS (i.e., network) drives to their cloud.