I have a massive file server (Harrier), and this is where I like to store massive files. I have another server (Ridley) that actually does things. One of the side effects of this setup is that I use networked shares and mapped drives a great deal.
I started using CrashPlan as a backup solution for my friends, but I wanted to store their files on Harrier while running the CrashPlan service on Ridley. As explained here, CrashPlan doesn’t support mapped drives, so I had to hack around it a bit. I found this workaround on the CrashPlan web site, and it worked with some fiddling and caveats. Here’s a summation of my experience using Windows XP SP3:
- Create a batch file (text file, but with extension bat instead of txt). Mine looked like this:
net use B: \\Harrier\Backup /USER:Ridley\Tremelune password
Note: Both Harrier and Ridley have a user Tremelune with the same password.
- Create a Windows task. The task should run the batch file and it should be Run as the user system or NT AUTHORITY\SYSTEM with no password. It may ask you for one, just hit OK. Don’t let it tell you how to live your life.
Now, the PDF said to have it do all this at logon…That never quite worked for me. I needed to run the task manually (and check to see if it mounted properly). You may or may not need to restart the CrashPlan Backup Service (Control Panel > Administrative Tools > Computer Management > Services).
Now when you browse for directories, you should see the mounted share in the CrashPlan interface. I have the mounting task scheduled to run every day in case I reboot the machine and forget to mount it manually.
2 Responses
Stay in touch with the conversation, subscribe to the RSS feed for comments on this post.
I still can’t make this work.
Either my Batch-file is wrong, or it just can’t attach the networkdrive properly.
my bat-file is:
net use G: \\X1server\TEST /USER:X1server/Ejer password >> logfile-stuff.
But when i restart winXP it doesn’t attach my drive (can’t reach the drive).
If i use the bat-file on startup, nothing happens.
If i use the bat-file after startup (manually) it attaches the drive. But not as the “disconnected drive” as shown in the manual.
If you made it work on your system, could you help me too? You could get access to my system via TeamViewer.com and remotely help me with the settings? ID: 235060514
Magic has happened:
If i run the bat-file manually, i just attach the networkdrive like windows normally do (as shown in link:
http://gratisupload.dk/download/50268/ )
If i use the Taks (in task manager) http://gratisupload.dk/download/50287/ to run the same bat-file, the drive get “attached” as a disconnected drive – just like the picture in the guide: http://support.crashplan.com/doku.php/recipe/back_up_windows_mapped_drives
When i set the Task to “startup with windows”, nothing happens.
AND fortunately when i run the bat-file via the Task-program, CP can detect the “disconnected” drive. Without stopping/restarting the services.
If i just run the bat-file manually, CP don’t detect the attached drive. Only Windows Explorer does.
My conclusion is: The bat-file has to be run as SYSTEM. And the only way i know (at the moment) how to do that, is through the Task. Long time ago, i used a small program called “delayrun”. It can delay the startup of any file (you choose) and delay the startup or 1 to infinity seconds. If i could direct DelayRun to the Task (that runs my bat-file) and startup with a delay of 30-60 seconds, the “disconnected” drive will be attached and CP will do the magic at any time.