Path: csiph.com!eternal-september.org!feeder.eternal-september.org!nntp.eternal-september.org!.POSTED!not-for-mail
From: Anton Shepelev <anton.txt@g{oogle}mail.com>
Newsgroups: comp.databases.ms-sqlserver
Subject: Backup to a network share
Date: Thu, 22 Jan 2026 17:21:11 +0300
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <20260122172111.aa47435016e93d0e505cb230@g{oogle}mail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Injection-Date: Thu, 22 Jan 2026 14:21:12 +0000 (UTC)
Injection-Info: dont-email.me; posting-host="01e1ecbe3730ac781bee94281d983c14"; logging-data="3226225"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1+EXClrZFzqIdYwuL3h1qmsUnSDaS8R4Po="
Cancel-Lock: sha1:RHmGcIAjd+T4wqodwJBjMBGyssk=
X-Newsreader: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Xref: csiph.com comp.databases.ms-sqlserver:2275

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