Backup Sql database to mapped network drive on another server prob

Until recently (stopped working this week) I have been able to backup my sql
database (on a windows 2000 server) to a mapped network drive(mapped to
another 2000 server). I am a user on both servers (administrator). I can see
the the drive in explorer. I can access the files.
I cannot see the drive in enterprise manager. Can someone help? Thanks.
> I cannot see the drive in enterprise manager. Can someone help? Thanks.
Backup to a network drive must be done with T-SQL Backup command (check it
in Books OnLine). Use UNC names, not mapped drives.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com
|||I understand that's one way to do it and I appreciate your answer. As I said
earlier, I was backing up to a network drive manually and through the
maintenance. I have been doing this for the last 6 months. Something got
change and I don't know where to start. Any suggestions as to what I can take
a look would be appreciated.
"BarbS" wrote:

> Until recently (stopped working this week) I have been able to backup my sql
> database (on a windows 2000 server) to a mapped network drive(mapped to
> another 2000 server). I am a user on both servers (administrator). I can see
> the the drive in explorer. I can access the files.
> I cannot see the drive in enterprise manager. Can someone help? Thanks.
|||It's not just one way to do it , it is the recommended way to do it. What
you see as a user means nothing unless that account is the same one that SQL
Server runs under. It is that account that does the backup regardless of
who initiates it or how they initiate the backup. Mapped drives can easily
get blown away or become unusable when changes are made on either end. So
if you want to continue using a mapped drive (which no one will recommend)
you need to log on to the server (database server) under the account that
sql server is running under and make sure the drive is mapped properly and
it still has the correct permissions to see and write to that share. If not
then the backup can not work properly.
Andrew J. Kelly SQL MVP
"BarbS" <BarbS@.discussions.microsoft.com> wrote in message
news:4FFF5A0E-3592-428D-A732-58378275F3D2@.microsoft.com...[vbcol=seagreen]
>I understand that's one way to do it and I appreciate your answer. As I
>said
> earlier, I was backing up to a network drive manually and through the
> maintenance. I have been doing this for the last 6 months. Something got
> change and I don't know where to start. Any suggestions as to what I can
> take
> a look would be appreciated.
>
> "BarbS" wrote:

Backup Sql database to mapped network drive on another server prob

Until recently (stopped working this week) I have been able to backup my sql
database (on a Windows 2000 server) to a mapped network drive(mapped to
another 2000 server). I am a user on both servers (administrator). I can see
the the drive in explorer. I can access the files.
I cannot see the drive in enterprise manager. Can someone help? Thanks.> I cannot see the drive in enterprise manager. Can someone help? Thanks.
Backup to a network drive must be done with T-SQL Backup command (check it
in Books OnLine). Use UNC names, not mapped drives.
Dejan Sarka, SQL Server MVP
Associate Mentor
www.SolidQualityLearning.com|||I understand that's one way to do it and I appreciate your answer. As I said
earlier, I was backing up to a network drive manually and through the
maintenance. I have been doing this for the last 6 months. Something got
change and I don't know where to start. Any suggestions as to what I can tak
e
a look would be appreciated.
"BarbS" wrote:

> Until recently (stopped working this week) I have been able to backup my s
ql
> database (on a Windows 2000 server) to a mapped network drive(mapped to
> another 2000 server). I am a user on both servers (administrator). I can s
ee
> the the drive in explorer. I can access the files.
> I cannot see the drive in enterprise manager. Can someone help? Thanks.|||It's not just one way to do it , it is the recommended way to do it. What
you see as a user means nothing unless that account is the same one that SQL
Server runs under. It is that account that does the backup regardless of
who initiates it or how they initiate the backup. Mapped drives can easily
get blown away or become unusable when changes are made on either end. So
if you want to continue using a mapped drive (which no one will recommend)
you need to log on to the server (database server) under the account that
sql server is running under and make sure the drive is mapped properly and
it still has the correct permissions to see and write to that share. If not
then the backup can not work properly.
Andrew J. Kelly SQL MVP
"BarbS" <BarbS@.discussions.microsoft.com> wrote in message
news:4FFF5A0E-3592-428D-A732-58378275F3D2@.microsoft.com...[vbcol=seagreen]
>I understand that's one way to do it and I appreciate your answer. As I
>said
> earlier, I was backing up to a network drive manually and through the
> maintenance. I have been doing this for the last 6 months. Something got
> change and I don't know where to start. Any suggestions as to what I can
> take
> a look would be appreciated.
>
> "BarbS" wrote:
>

Backup serious appending problem

We are running Small Business Server 2003 and using a SQL
database .. At some point in the setup of this, another
person apparently setup from 1 to 3 backup jobs .. the
problem is that there have been 3 backup jobs running
nightly and that 2 of the 3 are appending to the previous
backup.. this resulted in our hard drive filling up almost
to the crash point before we realized there was a
problem .. I don't know where to look for this ..
To recover space on the server we had deleted all of the
backups which are in the c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP folder...
I don't work with SQL much and this has become my problem
to fix .. any help would be appreciated
Thank you
LauraYou have to tell us how the backups are done. Are they happening from a
Maintenance plan job or plain BACKUP commands? You can find this by looking
at the job step.
Anyway, you have to use the WITH INIT option for the BACKUP command, if you
don't want to append.
Also, you should think about moving the database backups to a different
machine, to be able to recover from a failure on the SQL Server box.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"laura" <lauras@.microtechsystems.com> wrote in message
news:0a7601c48b78$202e7b30$a301280a@.phx.gbl...
We are running Small Business Server 2003 and using a SQL
database .. At some point in the setup of this, another
person apparently setup from 1 to 3 backup jobs .. the
problem is that there have been 3 backup jobs running
nightly and that 2 of the 3 are appending to the previous
backup.. this resulted in our hard drive filling up almost
to the crash point before we realized there was a
problem .. I don't know where to look for this ..
To recover space on the server we had deleted all of the
backups which are in the c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP folder...
I don't work with SQL much and this has become my problem
to fix .. any help would be appreciated
Thank you
Laura|||Thank you much for the reply..
As I said I do not work with SQL except to troubleshoot
when there is a problem that no one else is trying to
solve, but with your suggestion I did find out 1. What a
job step is
2. Where to look for this information under the
Management ->SQL Server Agent -> Jobs (at least I think I
am looking in the right place..
3. Now I will try to find why there are 4 Backup jobs
listed in this category..
Any other info you can send would be appreciated..
Again, Thank you
Laura
>--Original Message--
>You have to tell us how the backups are done. Are they
happening from a
>Maintenance plan job or plain BACKUP commands? You can
find this by looking
>at the job step.
>Anyway, you have to use the WITH INIT option for the
BACKUP command, if you
>don't want to append.
>Also, you should think about moving the database backups
to a different
>machine, to be able to recover from a failure on the SQL
Server box.
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>
>"laura" <lauras@.microtechsystems.com> wrote in message
>news:0a7601c48b78$202e7b30$a301280a@.phx.gbl...
>We are running Small Business Server 2003 and using a SQL
>database .. At some point in the setup of this, another
>person apparently setup from 1 to 3 backup jobs .. the
>problem is that there have been 3 backup jobs running
>nightly and that 2 of the 3 are appending to the previous
>backup.. this resulted in our hard drive filling up almost
>to the crash point before we realized there was a
>problem .. I don't know where to look for this ..
>To recover space on the server we had deleted all of the
>backups which are in the c:\Program Files\Microsoft SQL
>Server\MSSQL\BACKUP folder...
>I don't work with SQL much and this has become my problem
>to fix .. any help would be appreciated
>Thank you
>Laura
>
>.
>sql

Backup serious appending problem

We are running Small Business Server 2003 and using a SQL
database .. At some point in the setup of this, another
person apparently setup from 1 to 3 backup jobs .. the
problem is that there have been 3 backup jobs running
nightly and that 2 of the 3 are appending to the previous
backup.. this resulted in our hard drive filling up almost
to the crash point before we realized there was a
problem .. I don't know where to look for this ..
To recover space on the server we had deleted all of the
backups which are in the c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP folder...
I don't work with SQL much and this has become my problem
to fix .. any help would be appreciated
Thank you
Laura
You have to tell us how the backups are done. Are they happening from a
Maintenance plan job or plain BACKUP commands? You can find this by looking
at the job step.
Anyway, you have to use the WITH INIT option for the BACKUP command, if you
don't want to append.
Also, you should think about moving the database backups to a different
machine, to be able to recover from a failure on the SQL Server box.
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"laura" <lauras@.microtechsystems.com> wrote in message
news:0a7601c48b78$202e7b30$a301280a@.phx.gbl...
We are running Small Business Server 2003 and using a SQL
database .. At some point in the setup of this, another
person apparently setup from 1 to 3 backup jobs .. the
problem is that there have been 3 backup jobs running
nightly and that 2 of the 3 are appending to the previous
backup.. this resulted in our hard drive filling up almost
to the crash point before we realized there was a
problem .. I don't know where to look for this ..
To recover space on the server we had deleted all of the
backups which are in the c:\Program Files\Microsoft SQL
Server\MSSQL\BACKUP folder...
I don't work with SQL much and this has become my problem
to fix .. any help would be appreciated
Thank you
Laura
|||Thank you much for the reply..
As I said I do not work with SQL except to troubleshoot
when there is a problem that no one else is trying to
solve, but with your suggestion I did find out 1. What a
job step is
2. Where to look for this information under the
Management ->SQL Server Agent -> Jobs (at least I think I
am looking in the right place..
3. Now I will try to find why there are 4 Backup jobs
listed in this category..
Any other info you can send would be appreciated..
Again, Thank you
Laura
>--Original Message--
>You have to tell us how the backups are done. Are they
happening from a
>Maintenance plan job or plain BACKUP commands? You can
find this by looking
>at the job step.
>Anyway, you have to use the WITH INIT option for the
BACKUP command, if you
>don't want to append.
>Also, you should think about moving the database backups
to a different
>machine, to be able to recover from a failure on the SQL
Server box.
>--
>HTH,
>Vyas, MVP (SQL Server)
>http://vyaskn.tripod.com/
>
>"laura" <lauras@.microtechsystems.com> wrote in message
>news:0a7601c48b78$202e7b30$a301280a@.phx.gbl...
>We are running Small Business Server 2003 and using a SQL
>database .. At some point in the setup of this, another
>person apparently setup from 1 to 3 backup jobs .. the
>problem is that there have been 3 backup jobs running
>nightly and that 2 of the 3 are appending to the previous
>backup.. this resulted in our hard drive filling up almost
>to the crash point before we realized there was a
>problem .. I don't know where to look for this ..
>To recover space on the server we had deleted all of the
>backups which are in the c:\Program Files\Microsoft SQL
>Server\MSSQL\BACKUP folder...
>I don't work with SQL much and this has become my problem
>to fix .. any help would be appreciated
>Thank you
>Laura
>
>.
>