That's not really a DPM limitation per se - it's the way that the SQL Server VSS writer works (i.e. the SQL Server VSS writer runs as LocalSystem).
The client I was at had an internal enterprise SQL Server infrastructure whose services that could be "purchased" by other people within the company. Depending on the application it might have its own instance. Each instance ran as its own service account, and LocalSystem is not permitted access to SQL Server (to prevent Windows administrators being able to get access to database content). This is per Microsoft's guidance on building shared SQL Server infrastructure. Unfortunately, it doesn't help DPM backup SQL Server databases. Cheers Ken -----Original Message----- From: Ben Scott [mailto:mailvor...@gmail.com] Sent: Friday, 9 October 2009 10:31 PM To: NT System Admin Issues Subject: Re: Backup/Restore best practices for Sharepoint 2007 On Fri, Oct 9, 2009 at 9:47 AM, Ken Schaefer <k...@adopenstatic.com> wrote: > If you're looking at a more enterprise level setup, then here's a few > things I ran into... Yikes! Thanks for that info. /me crosses DPM off my list of backup solutions to evaluate for next year's server upgrades. I particularly like how Microsoft's own backup solution doesn't comply with Microsoft's own best practices recommendations for their own database solution. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
