Next question regarding to backup location.

Hi,
First of all, thanks for the answer about "Have you found any solution for
this?" qustion...
Here is another question, but related previous question.
Environment : Win Svr 2003/SQL Svr 2000
As far as I know, to specify a UNC path for backup location, MSSQLServer
service should be running with an account that can access network resources.
.
As you know, by default, SQL Svr 2000 is installed with LocalSystem account.
Prior to the release of the Win200 OS, LocalSystem account can't access
network resources, but with the release of Win2000, the account has been
changed to allow authentication to network resources...
However, according to my testing, when I run the MSSQLServer service with
LocalSystem account, a UNC path couldn't be used, however, the service
running with an account that has network access rights, a UNC path could be
used for backup location...
Is my understanding something wrong?
Since the LocalSystem account was modified to allow authentication to
network resources, should it work a UNC path for backup location when the SQ
L
service is running with LocalSystem account?
Thank you in advance.
......................................................TJHi again,
it might be better to keep posting responses as opposed to posting new
threads, as people that have posted tend to see those in preference to
new stuff.
Anyway, permissions wise, I've never tried altering the permissions of
the local system account to try to make things happen, if you need
additional behaviour, why not actually run the service under a more
priviledged account.
On a separate note, could you explain what you're trying to do? the
nature of a backup is to preserve data, and while it can be used to
transfer it (and I do that regularly) I would not expect that behaviour
to be built in to an automated process, if you need data elsewhere
there are probably better ways of moving it.
Cheers
Will
P.S I should point out (and am about to amend my sig to say it) - I am
not in anyway an expert/ affiliated with any company/ in anyway
competent. I post for fun, and to help people. Don't assume my advice
to be expert.|||Hi, Will
Thanks for your posting.
Sombody answered the question about my account issue...
He/She provided this link for the issue. (This is a just information for
somebody needs this...)
http://support.microsoft.com/?id=555128
I am trying to develop an application to backup remote SQL server(SQL-DMO),
and the physical backup file(xxxx.bak) should be exist in my app folder(Of
course, my app is running in another machine) because another app needs to
access them via the folder...
To backup SQL server into a UNC path, I do not think that it is a scable
soultion since there are some requirements to use a UNC path in SQL server.
Also, once the backup is done to each temporary folder in remote machine, I
may be able to move the backup file from remote temporary folder to my app
folder. However, I also do not think that is is a scable or reliable
solution...
Any idea?
Thanks.
.........................................................
..........TJ
"Will" wrote:

> Hi again,
> it might be better to keep posting responses as opposed to posting new
> threads, as people that have posted tend to see those in preference to
> new stuff.
> Anyway, permissions wise, I've never tried altering the permissions of
> the local system account to try to make things happen, if you need
> additional behaviour, why not actually run the service under a more
> priviledged account.
> On a separate note, could you explain what you're trying to do? the
> nature of a backup is to preserve data, and while it can be used to
> transfer it (and I do that regularly) I would not expect that behaviour
> to be built in to an automated process, if you need data elsewhere
> there are probably better ways of moving it.
> Cheers
> Will
> P.S I should point out (and am about to amend my sig to say it) - I am
> not in anyway an expert/ affiliated with any company/ in anyway
> competent. I post for fun, and to help people. Don't assume my advice
> to be expert.
>|||Hi TJ,
I think that the main point that needs to be considered here is what's
actually doing the backup. It's not a trivial task for a SQL server to
convert it's live database into a restorable form, as a result the
processing and the storage of the result would have to take place
locally.
You want to create a utility that backs up databases to a remote
location, but if this was simple, it would have been implemented.
As for scalable, the idea of a scalable set of backups is not really
one that people often consider as usually you're in control of the
device you're backing up.
You've said that you want to backup databases, but what is the ultimate
aim of these backups? is this so that the data can be retrieved (in
which case your app seems a little trivial), or do you intend to move
this data to a new location? or something else?
I "think" I can help out here, but you'll need to post a few specifics
as to what you're trying to do.
Cheers
Will|||Hi, Will.
Thanks for your posting again.
I know that backup processing is expensive one...
For your questions, the simple answer would be that I am trying to move the
data to a new location(Central location)...
There could be some better solution, but I would like to stay with backup
for some reasons...
Thanks again.
...................................................TJ
"Will" wrote:

> Hi TJ,
> I think that the main point that needs to be considered here is what's
> actually doing the backup. It's not a trivial task for a SQL server to
> convert it's live database into a restorable form, as a result the
> processing and the storage of the result would have to take place
> locally.
> You want to create a utility that backs up databases to a remote
> location, but if this was simple, it would have been implemented.
> As for scalable, the idea of a scalable set of backups is not really
> one that people often consider as usually you're in control of the
> device you're backing up.
> You've said that you want to backup databases, but what is the ultimate
> aim of these backups? is this so that the data can be retrieved (in
> which case your app seems a little trivial), or do you intend to move
> this data to a new location? or something else?
> I "think" I can help out here, but you'll need to post a few specifics
> as to what you're trying to do.
> Cheers
> Will
>|||Hi TJ,
As far as the sql server backup route goes, to my knowledge (which is
far from expert) the only way you're going to get the sql server to
write the backup file to a new location is to use a UNC path, you
cannot get it to use the client machine to perform the backup, it will
be done by the server, the permissions on the account performing the
backup will be those of the user for the service running on the server.
If a UNC path is not an option then I think the sql backup route won't
work.
As for other things you could do, without more info than "moving the
data to a new location" I can't really suggest much.
Do you want the data to be live in the new location? If so perhaps
features such as replication may be a better route.
Is your app intended as an end user application that has to be able to
apply to lots of situations, or is it to solve one specific problem?
When you say you want a scalable solution, what needs to scale - the
number of databases, the size of the databases, the distance between
the client and server, etc.?
If you could provide a lot more info as to how you intend to use the
backup, there are probably other ways of doing it.
Cheers
Will