I never could get it to work right so what I did was created a scheduled task to map a network drive (X:) under the SYSTEM account on startup on the SQL server (I have 4 of them each with 26 instances). Then SQL is set (we had to change it in the registry after each instance is installed) to use the X: drive, and assigned folder on that drive that's specific to that instance, as the default location for all backups. So then our LiteSpeed backup job uses the X: location as the destination for all full and log backups without issue (and I have variables so it catches all of the user databases that I wanted to grab). Works great and we just deploy the template to each new SQL instance as needed but have it set so that we specify the location when the template is deployed since it changes for each SQL instance although if you use one location for all backups then you could include in the template to just use the one location and then not have to specify it again later on deployment.
↧
