For longer than I care to admit, my DPM server has had the same error every night about an auto-protection failure on one of my SQL servers. I've looked into it before but never came away with anything useful until recently. I've finally found information on how to fix this annoying issue. The Advanced Information link in the error will tell you to make sure WMI is in a good state on the machine. The error itself isn't very descriptive. It'll look something like "DPM could not enumerate SQL Server instances using Windows Management Instrumentation on the protected computer $serverFQDN."
I've been carrying a pen as part of my (mostly) every-day-carry, or EDC, for a couple years now. I bought the Zebra F-701 and after a few other pen purchases, the 701 is still my favorite of all. At first, I just wanted a pen that looked nice and for the moments I needed to sign something. I recall attending meetings when I worked at the university where the attendees were asked to sign-in on the attendance sheet: I tended to be the only one that didn't have a pen so I felt unprepared when I had to ask one of the other attendees if I could borrow theirs. Once I started college, I found myself using a pen much more often, so it had to be comfortable, relatively inexpensive (nice pens can cost hundreds of dollars), and still stylish enough to live in the pocket of a dress shirt.
Inconsistent replicas. Studies show that nearly half of all backup admins suffer from inconsistent replicas. But backups don't have to be this way. With Chkdsk, you too can reduce replica inconsistencies. (Please see a Sr Admin if your replicas are consistent for more than 4 incremental jobs.) Joking aside, as far as DPM is concerned, an inconsistent replica is a deal-breaker and that means other backup jobs won't run until you fix it. A common issue with file-level backups in DPM is that it'll get tripped up on s corrupt file, usually one in a shadowcopy volume. I'd like to discuss how to get around it.
Comments
Post a Comment