Willem

Gentle bump, still waiting for webdav support.

Is it possible to enable a low temperature warning? I don't worry to much about high temps, but in the wintertime my shed-storage can become quite cool

Works like a charm. Thanks for the quick fix.

Some more odd behaviour I'm seeing. I tested with move to try and rename a file. As before #vers is a symlink \\homeserver\videos\#Vers\testing>dir Directory of \\homeserver\videos\#Vers\testing 14-05-2014 21:43 <DIR> . 14-05-2014 21:43 <DIR> .. 14-05-2014 21:43 3 test.txt 1 File(s) 3 bytes \\homeserver\videos\#Vers\testing>move test.txt test2.txt Overwrite \\homeserver\videos\Vers\testing\test2.txt? (Yes/No/All): n 0 file(s) moved. Why does it warn of overwriting a non-existing file? Second test the real path \\homeserver\public\testing>dir Directory of \\homeserver\public\testing 14-05-2014 21:43 <DIR> . 14-05-2014 21:43 <DIR> .. 14-05-2014 21:43 3 test.txt 1 File(s) 3 bytes \\homeserver\public\testing>move test.txt test2.txt 1 file(s) moved. \\homeserver\public\testing>dir Directory of \\homeserver\public\testing 14-05-2014 21:44 <DIR> . 14-05-2014 21:44 <DIR> .. 14-05-2014 21:43 3 test2.txt 1 File(s) 3 bytes

Creating a new file ain't the problem, after creating windows asks for a filename which equals a rename and therein lies the problem. When creating a new textfile seems to fail, a newly created "New Text Document.txt" exists.

Server 2012 R2 Standard x64

Logfiles uploaded. I'm using version 2.1.0.528 but have seen the behaviour since 2.1.0.432

I'm happily using symbolic links but i cannot rename a file or folder through the symlink. Example: In folder D:\ServerFolder\Videos i've got a symlink called '#Vers' pointing to D:\ServerFolders\Public >ren d:\ServerFolders\Videos\#Vers\test.txt test2.txt A duplicate file name exists, or the file cannot be found. When I work through the gui, windows gives me the following error:

You can change the drive letter through windows disk management.

Thank you for the explanation. I hadn't expected that the dp v1 manual would contain the answer, I had only read the v2 manual.

Backup from physical drives works as expected. I understand why a baremetal restore wouldn't work but for individual files the drivepool behaviour isn't as straightforward as I would have thought. Maybe something for the faq, or am i the first to do backups?

Changed the backup to the physical drives, will report back the result tomorrow. It isn't a really intuitive way to do backup. Can you explain why you can't point to the pooldrive?

Hello, I'm using drivepool on my 2012 R2 server with Essentials Experience role enabled and having difficulty with systembackup. I see the following messages in eventviewer when the backup is supposed to start: Event12289, VSS: Volume Shadow Copy Service error: Unexpected error DeviceIoControl(\\?\Volume{077cfcbb-1ed5-44c5-b960-5ff569f2e170} - 0000000000000170,0x0053c008,0000008D8BF10080,0,0000008D8B87D1D0,4096,[0]). hr = 0x80820001, The bootfile is too small to support persistent snapshots. The mentioned volume is my pooldrive. On other volumes i'm having no problems with the VSS. Drivepool ver 2.0.0.420