Jump to content

dslabbekoorn

Members
  • Posts

    59
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by dslabbekoorn

  1. Well after 18 hours the folder is back on its own drive and working as it should again. I thought the size had ballooned from 575 gb to 1.25 tb but that was operator error and late night math. It's still the same size, just confused used and free space, windows = used, drivepool = free in their display.. I still can't figure out why it fails but its getting further now than before. Come on MS, WHS2011 worked in the pool for years (until an update busted it) why can't WSE2012? Well, as Microsoft "famously" said "large hard drives are cheap". (unless the factory floods )
  2. OK, client backup folder is now back in the pool and a backup started. Lo and behold, it has reached 7% and climbing as I type. Never even got started before. Seems like, just maybe, perhaps, fingers crossed, this problem may be fixed with the latest beta v312. I realize I'm probably jinxing myself, but I think we have a winner here. I'll know for sure in about an hour or so. Backup is now at 12%, yea! I knew I'd jinx it, backup failed at about 15%, with "Backup did not complete because a problem interrupted the connection to the server" I'll pull the server and client logs and see if I can find an error to explain this. I'll let it go overnight to see if the automatic backup works at midnight. It was a manual backup that failed. Dave
  3. Updated to the most recent version and hope to try the client backup folder in the pool thing again to see if there is any change. Just wish the move folder did not take so long. Backups in it are around 675 GB. Takes the dashboard routine a while (up to 12 hours) to move it all.
  4. Just to bring up our previous comments on storage spaces and MS's half baked release of it, you might like to check out this (painfully) humorous exchange on Technet's WSE2012 forum. Poor guy seems to have lost 11TB & his server on belief of MS advertising claims. The we buried the approved hardware list part was especially wince inducing. Seems the official approved hardware to work with it is 1) large and 2) expensive. So much for the SOHO market. Link: http://social.technet.microsoft.com/Forums/windowsserver/en-US/12d63e5b-84a4-4efe-8951-2274d1a3b6c9/storage-spacesthe-perfect-stormhardware-failure-on-servermove-the-7-disks-to-a-new
  5. Good news always makes me feel better, and thank you Alex (and others) for your time and help with this.
  6. The end user gets it again, in the end. My "fix" of using the non-pool drive is working fine. I await word from those who know more than me, good luck with the bug hunting.
  7. Moved client backup folder back to pool, instant fail. Moved it back to non-pooled usb drive, success. Tracer logs and windows client & server logs sent to support. This is weird and seems to be related to the known bug in WSE2012 that it can not backup to a storage space pool and now seems to be exhibiting that problem with drivepool pools and drivebender pools as well. MS is "aware of the problem and is working on it", since November, according to post all over Technet forums. Bad QA on a $500 commercial OS that touted storage space as a premium feature. OK, off soapbox now, hope support can track this down. I'm stumped.
  8. Client and Server logs sent to support as requested. They want me to activate tracer in drivepool and move the client backup folder back to the pool, run a backup, let it fail, and send logs from all to them again. I will try to do this tonight, been a little busy. Backups to the external usb drive have been proceeding without fail for 4 days now. Hope we can figure this out. More later. Dave
  9. I have a rock solid setup with WSE2012 using drivepool. Only problem is if the client backup folder is in the pool, all backups fail within seconds with the WSS service shuting down and restarting. Obviously this kills any backup running. I have read in numerouis forums that storage spaces has a "bug" that will not allow the client backup folder to be in the pool or all backups will fail to start. The reported error logs, while not very helpful, are exactly what I am seeing.. Except that I am not uising storage spaces, I am running the latest drivepool version. To test this out, I moved the client backup folder off the pool to a usb drive I just acquired and bam, all backups work first time I click start. No errors or problems. I moved the folder back to the pool and instant fail. I have read her and on the old forum of others running with the folder in the pool and having no problems. I am not sure if anyone is running Windows Server 2012 Essentials or not, maybe they are all on WHS2011. But i Thought that Drivepool was compatible with WSE2012. Has anyone else had this issue? Any info or ideas would be appreciated, I am backing up 4 computers and the capacity of the pool is much desired. If I have to get a dedicated 3TB drive to hold my backups and keep it off the pool that will be a drag. DP works fine for all other uses, media library, photo storage and such, but the backups would be a swwet icing to the cake. I had the folder in the pool for years with WHS2011. Help please?
×
×
  • Create New...