Groups | Search | Server Info | Keyboard shortcuts | Login | Register
Groups > comp.databases.ms-sqlserver > #2275
| From | Anton Shepelev <anton.txt@g{oogle}mail.com> |
|---|---|
| Newsgroups | comp.databases.ms-sqlserver |
| Subject | Backup to a network share |
| Date | 2026-01-22 17:21 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <20260122172111.aa47435016e93d0e505cb230@g{oogle}mail.com> (permalink) |
Hello, all (however few that may be). 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$<instance> , 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? -- () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
Back to comp.databases.ms-sqlserver | Previous | Next — Next in thread | Find similar
Backup to a network share Anton Shepelev <anton.txt@g{oogle}mail.com> - 2026-01-22 17:21 +0300
Re: Backup to a network share Erland Sommarskog <esquel@sommarskog.se> - 2026-01-22 23:06 +0100
Re: Backup to a network share Anton Shepelev <anton.txt@g{oogle}mail.com> - 2026-01-23 18:55 +0300
csiph-web