dslabbekoorn

I'm running EaseUS Todo Backup Workstation v9.1. It was working fine even with the network discovery feature in Win 10 borked by the Nov. 2015 update, the program uses an ip address to find it's backup destination. Now it says the destination is unavailable and to retry to connect. The only thing out of normal on my server is the duplication inconstancy error from the pool, I've had times in the past where any error message from the pool seems to prevent backups from starting or completing. I think if your fix gets rid of that error, everything will be back to normal. Not sure why the after

My pool started to throw this error/warning recently. The details shows: "\System Volume Information IndexerVolumeGuid" Access is denied. Duplicating now does not resolve the issue. All drives were checked with chkdsk and no errors found. Ran the WSS troubleshooter and reset NTFS permissions on the pool to "Everybody" All were ineffective in removing the error. As long as the error on the pool exists, my backup program will not use it as a backup destination. I am currently running Beta v651, but the release version throws the same error. The pool seems to work fine in all other res

Big Ooops, I reinstalled my server OS recently and everything went well, too well. I formatted the drive before I realized I had not gotten my Scanner key off of it. I did remember the DrivePool key though. Is there a way to recover my key and what do you need from me to do it? Thanks, Feeling dumb in Michigan

Thanks Christopher, that's just what I was hoping to hear. I'll definetly take your advice on the duplication. Happy Thanksgiving.

I finally bit the bullet and got Windows Server 2012R2. I plan on using my drivepool for the client backup folder and a separate 2TB usb drive for server backups. Are there still any problems with having the client backup on the pool, I remember there being issues that prevented it from working. The new system is setup and running and I just got my pool re-attached to the server, PLEX seems to be working again as well. Now setting up the client backups is the only thing remaining. Server R2 does seem to be "snappier" than WSE, and runs much more quickly on my server hardware. WSE just st

I've seen that site, it just says that the connector out of the box (built in) should work. I can connect and download that connector fine, but when I try to install it I get the cannot connect to network - server not available error message, which is rubbish. I can see and access the server from all computers The connector uninstalled and re-installed on the other 2 computers but refuses to on the desktop and laptop I upgraded to win 10 and used the Microsoft Account PIN login. Changing back to a local login did mot help the connector install at all. I'll check the logs and pass them

Sorry but I thought I mentioned that I was running Windows Server 2012 Essentials (not R2) in my previous post. The new connector will not install on my server, I tried. I'm getting to the point where I don't have the time or energy to pursue this issue any more and I'm thinking of a different backup system using the server/pool as a giant hard drive. (I know a novel concept) Is it still an issue putting backups on the pool? I remember having problems along with others getting it to work with the in the box backup from WSE2012. Had to go with a non-pooled drive. If this is no longer a pr

Unforntunatly, my server is Windows Server 2012 Essentials (not R2) and was working flawlessly until I upgraded to Win 10 on the 2 clients. The 2 that are failing to install and run the connector are the 2 that I set up to use my Miicrosoft account to login. They really push that during install and don't give you (any obvious) way to go back to a local account. The other 2 computers in my little network use local account logins and installed and backup just fine, which is why I'm leaning to that being the at least part of the problem. Everything else dealing with the server from theses 2 c

Sorry to revive an old thread, but after "upgrading" all my networked computers to win 10, 2 will not install the connector or backup. I had a failed upgrade on my main computer that left me with a black screen, a useless mouse cursor, and for a while a flashing task bar. This machine only restarted 3 times not 4 lie the other 3 did. I had my backup drive ( a 3tb standalone usb drive fail and only one good backup of each computer. It saved me, I restored the c drive and everything works, except the connector. I uninstalled it and tried to re-install. Got the connector from the server nor

I backup my 3 clients to a non-pool 3tb drive, as I could never get Windows Server 2012 to let me backup to the pool. This has worked well until I upgraded to Windows 10. Since then my backup drive has been filling up alarmingly fast. Today I only have 20gb left. My retention policy has kept it well within the 3tb for months, now it's filling up, fast. I may have found the culprit in File History, it defaults to "on" on all machines and tries to backup all the files in each computers largest folders, twice a day. I think I have it turned off again and on the server too. My ques

Oops, forgot to do that, grandkids are distracting. Here it is: https://social.technet.microsoft.com/Forums/windowsserver/en-US/4bacccb2-a1ff-4712-930b-5804bdbaade5/problem-with-dashboard-not-working?forum=winserveressentials

Fixed the problem! Google is again my brain, I found this link to Microsoft's forum where a guy had a corrupt file opening the dashboard. He deleted the file and windows re-created it error free. His dashboard and now mine work great again. Thank you for your help Drasha, I was getting frustrated with this because I knew it would be some small thing like this and take forever to hunt down.

OK, ran it in an elevated command prompt on both the server and my computer. Now what?

Yeah, I still do. Everything else works, just can't connect to the dashboard except by RDP which works fine and I can open it from there on the server. All the other clients connect just fine, only my desktop has this issue.

I have successfully upgraded all 4 of my home network computers to Windows 10. My problem is that one client, my desktop, will not open/connect to the dashboard anymore. All the other computers connect fine and none needed to have the connector re-installed. My desktop backs up fine and I have full access to the shared folders on the server. Remote desktop works fine also. I thought maybe the connector was corrupted so I un-installed and re-installed it. No change, everything works except the dashboard. I shut down both anti-malware programs on the desktop (Malwarebytes & Norton Sec

OK, I'm convinced to stay on WSE2012. Seems like a lot of hassle to gain a little. I would also like to get my client desktop to be running UEFI bios instead of legacy. I had originally installed it under legacy and now with equipment upgrades, can use the newer UEFI bios. My question is, can I change the motherboard to UEFI bios and then restore the c drive to the same SSD it's now on and have it be UEFI instead of legacy. The other types of changes I have found on TechNet and other places always fail at one step or another. I just got the desktop back running the way I want it and rea

I'm toying with the idea of upgrading my server OS to Windows Server 2012 R2 from the regular Windows Server 2012 Essentials. I have keys for both as well as the Standard and Datacenter versions. I don't need the extra capacity of the full servers but wonder if the move will be worth the hassle. Does WS2012R2 run better or faster or offer any real reason for the upgrade? I'm assuming the next version Server 10 would be somewhat compatible with either one. Things work fine on the WSE2012 box now. I have both Drivepool and Plex installed on the server. If I do this, I need to do it so

Got my new cable from Amazon today (god I love Prime) Powered the drive & server down, swapped out the cable and fired them back up. Success! The drive was found and installed on a USB3 port, all of them actually, It was the cable, nice to get a $3.57 solution once in a while. All is now good on my 12.5 TB of media.

OK, new hub arrived and 3 of 4 drives were detected fine but the 4th will not be seen by the original motherboard or hub slots as usb 3. Plug it in to a usb 2 slot and it's detected and added to the pool fine. Yes this is a seagate expansion 2tb usb 3 drive. Brand new. I don't have another usb 3 a male to micro b male that seagate uses on their drives, had to order one from amazon prime, I have had problems with cables before and it's a cheap check. Hope the enclosure is OK, no way to check that other than a new cable. Past return to amazon but should be under warranty from seagate yet if

Windows Server 2012 Essentials, Gigabyte 770TA-UD3 motherboard, Renesas USB 3.0 chipset/driver, newest driver I can find is from 2010. USB 3.0 is on-board. Would a powered usb hub make any difference? All the drives connected to it have their own power supplies so I wouldn't think so. The hubs are both from companies in China so I have no idea of their quality and only went by reviews of other users. I have a better grade hub coming from Amazon that is powered just to try. I cost more anyway. I have read on several other sites of problems when the drive spins down or sleeps that Win 8

I have 4 USB 3.0 drives attached to my server, the problem is, I only have 2 USB 3.0 ports. My video card blocks my only available pci-x port internally so I can't add an expansion card for more ports. I am therefore left with the option of using a USB 3.0 hub to add the extra 2 drives into my system at 3.0 speeds. I have enough 2.0 ports for the drives, but would like to use them in their native mode. However (there's always an however) the USB 3.0 hubs I have don't seem to play nice with WSE2012 or something. Drives attached to the hubs are not detected or show up as new even though the

It is WSE2012, and I currently have the router pointing to the server as primary DNS with itself as # 2 and comcast and google as #3 & 4. Sounds like it isn't worth the effort to put DCHP on the server, which is what I was beginning to believe. With only 4 computers, about that many Apple devices and the Rokus, it doesn't seem my network is complicated enough to warrent the more powerful server DCHP.

Got it all installed and working, DNS was nearly all set up as the clients still had the correct settings, just had to add comcast and google as forwarders on the server. Put PLEX on the server, set it up as a service and all my media is good to go and showing on all the Rokus. Was able to get rid of some old folders that were unused but locked when the new OS released them, neater. All clients reconnected and working. New SSD in as OS drive, much faster for everything. Have a new CPU coming (Quad core AMD Phenom II 965, and 4gb more memory to finish out the upgrade. Hardest part will be

Thanks, that's a load off my mind. I'll keep you posted. I do have a backup drive for the server, but it was for a 200gb drive and my SSD was only 120gb. Only 70gb was actually used, but the restore wouldn't work as the program claimed the partition was too small for the backup to fit and the original drive died before I could trim it down. Clean install and rebuild is tedious but best in the long run.

My system drive was failing and I couldn't clone it for the life of me. Put in a new 120GB SSD and installed windows clean on it. Was unable to deactivate license before I re-installed WSE2012. How can I get the activation back? Also, can I somehow still use the existing client computer backups (on a separate drive not in the pool) with the new install or am I doomed to backup all the clients all over again? (Groan)