Sorry, the backups are not compatible with WHS 2011 or any of the Server Essentials variants. There is no easy workaround either. You don't give any indication in the spec of the V1 box so difficult to say whether Essentials will run on it. I beleive the limitation may possibly be RAM if you are thinking of one of the original HP Home Servers.
So I have a new WSS box arriving tomorrow. Are the backups made with V1 compatible with Essentials? Is it possible to migrate them to the new box? Any suggestions on what to do with the V1 box? It it possible to load Essentials on it (legality aside)?
Curious, I have just checked on my 2012E (not R2) and I also have a load of tmp files in C:\Windows\Temp. This is clearly a side effect of the Essentials server backup and I currently have 800 of them. The only space they will be taking up is slots in the directory files and so there is no danger of running out of disk space. I am going to see if Disk Cleanup will tidy them up without messing up the server. EDIT: Disk Cleanup doesn't seem to touch them - they are still there.
WooHoo! I can actually write to my Music folder now it's taken hours and hours and hours to apply the permissions. Whilst my IP address Default.rdp connection works with the ignore connection warnings and connect anyway settings, doing the same using "SERVER" and ignore connection warnings does not
I have WSE2012R2 doing a nightly server backup. It's just a bare metal backup on the C: drive and its System Reserved partition, and the backup target is always a dedicated 1TB drive on an add-in 2-port SATA controller. Every time Server Backup runs it creates and leaves a file named DSWXXXX.tmp in C:\Windows\Temp. The XXXX is a random 3/4 digit hex code. I know it's Server Backup doing it because they are time stamped with exactly the time the backup is scheduled to start and I've also confirmed I get a new one at the time stamp when I manually start an out-of-band backup. These are zero-byte sized files and they never seem to get deleted so the Temp folder just fills up with them. But here's the really troubling thing and the reason for my question. I have also discovered that if I manually delete these .tmp files, the server will BSOD within the next 1-2 days right at the end of the daily backup cycle. I have no trouble deleting them, they are not locked and I have done this just before a reboot with no apparent trouble at that moment. Usually the next backup goes OK, but by the next day or so, the server will restart just as the backup cycle is completing while writing the .vhdx and .xml files, and so the entire set of backup files are not written to the target drive complete. Also I usually end up with *all* the client backups being set back to "Not Set Up" in Dashboard after the restart even though this issue seems to have nothing to do with client backups. Client backups would not be active or occur until many hours later and are not kept on the server backup disk. All the previous client backups are fine though after the restart. I just have to go through and manually re-setup each client again and they will then continue to back up normally on the next cycle. So does anyone have insight as to what's going on here? The obvious answer is not to delete the tmp files. They don't really hurt anything other than the small amount of space they take up as empty files but I'm going to get thousands of them over time. And it can't be "normal".