jmwills 284 Posted March 12, 2015 Share Posted March 12, 2015 No kidding. Reliability is the first or second most important thing when it comes to backups. We're about to find out how reliable a BMR from Essentials R2 is, PXE boot and all. Link to post Share on other sites
ikon 439 Posted March 12, 2015 Share Posted March 12, 2015 Never did trust them pixies Link to post Share on other sites
jmwills 284 Posted March 12, 2015 Share Posted March 12, 2015 About 35 minutes and all was good. No bumps in the road. Link to post Share on other sites
Drashna Jaelre 159 Posted March 12, 2015 Share Posted March 12, 2015 Thanks for posting back. I suspect you have got it fixed and the issue is resolved. Now, you just have to get over the idea that Client Computer Backups are fragile or unreliable. After all, it really appears that faulty hardware was the problem — WSE2012R2 can hardly be blamed for that Software is only as reliable as the hardware it's running on. : ) And since the hardware ... well, wasn't reliable. : ) Never did trust them pixies Pixies are awesome, I don't know what you're talking about. : ) And PXE booting is fantastic. I still say that Microsoft "stole" my idea with the client restore disk via PXE. I'm totally not complaining though. Link to post Share on other sites
ikon 439 Posted March 12, 2015 Share Posted March 12, 2015 Software is only as reliable as the hardware it's running on. : ) And since the hardware ... well, wasn't reliable. : ) Ain't that da truth. Link to post Share on other sites
msawyer91 16 Posted April 14, 2015 Share Posted April 14, 2015 I've been lucky I've never had application corruption issues with bad RAM, like the backup database corruption. Usually my experience with bad RAM results in a blue screen of death with an ugly error like "NMA parity check / memory parity error. The system has halted." Maybe Windows is more tolerant of bad memory, rather than bringing the whole system grinding to a halt. Link to post Share on other sites
ikon 439 Posted April 14, 2015 Share Posted April 14, 2015 I suspect it might have something to do with the backup database being open while all this RAM is being used. Bad RAM leads to system crash or hiccups and, boom, database gets hosed. Link to post Share on other sites
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now