From: esquel@sommarskog.se   
      
   Anton Shepelev (anton.txt@g{oogle}mail.com) writes:   
   > While setting up backup via maintenance plans,   
   > we have found that we cannot specify a Windows network   
   > directory as backup target, because the MSSQL   
   > service runs as the standard local user MSSQL$ ,   
   > which (naturally) has no access to it.   
   >   
   > Our administator suggests re-configuring it   
   > to run as domain-level user   
   > (with access to the requrired network share),   
   > or even use a two-stage backup,   
   > with a separate step of moving the backup files   
   > from the local machine to the network.   
   >   
   > The only other way we know to make that share   
   > accessible to MSSQL is to give it permissions   
   > for /everyone/, which we should rather avoid.   
   >   
   > What are some best (or least tolearable) practices   
   > of backing up MSSQL to a network share on Windows?   
      
   Run with a gMSA, I guess. That is, rather a machine-local MSA,   
   an MSA that exists in the AD and therefore can be granted access   
   to the network share.   
      
   One more alternative to the list above is to grant access to   
   the machine account, that is DOMAIN\MACHINE$, but that is   
   less secure.   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)