Backup security

Hi,
Our current backup process writes backup to a network drive and that is
transferred to a DVD on a daily basis. How can we prevent people from
installing this backup on the DVD if the DVD is ever stolen? Can the
backups be "password protected" or restricted to prevent un-authorized
restore?
Thanks.From BooksOnLine under BACKUP:
PASSWORD = { password | @.password_variable }
Sets the password for the backup set. PASSWORD is a character string. If a
password is defined for the backup set, the password must be supplied to
perform any restore operation from the backup set.
This may prevent most people from restoring the backup but does nothing to
prevent anyone from reading the file with a simple hex editor. You should
look at one of the 3rd party backup tools that do encryption among other
things.
www.red-gate.com
www.quest.com
Andrew J. Kelly SQL MVP
<RK> wrote in message news:%23Evnr5uIGHA.2628@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Our current backup process writes backup to a network drive and that is
> transferred to a DVD on a daily basis. How can we prevent people from
> installing this backup on the DVD if the DVD is ever stolen? Can the
> backups be "password protected" or restricted to prevent un-authorized
> restore?
> Thanks.
>|||Windows has extensive cryptography capabilities that allow creation of
encryption and decryption software relatively easily. If relevant to your
requirements, there are many programs available at little or no cost that
can encrypt and decrypt the backup file(s) separately.
<RK> wrote in message news:%23Evnr5uIGHA.2628@.TK2MSFTNGP15.phx.gbl...
> Hi,
> Our current backup process writes backup to a network drive and that is
> transferred to a DVD on a daily basis. How can we prevent people from
> installing this backup on the DVD if the DVD is ever stolen? Can the
> backups be "password protected" or restricted to prevent un-authorized
> restore?
> Thanks.
>

Backup script

I want to create a simple SQL 2005 database backup script to run a scheduled
times. This was easy with SQL 2000 but I can't find a similar process in
2005. Can anyone tell me where I can find it? Thanks.
David
David,
In SQL Server Management Studio under the node Management / Maintenance
Plans you can create a maintenance plan using the Maintenance Plan Wizard
that backs up the databases. If you back up to disk using the appropriate
BACK UP DATABASE settings you should also be sure to check and fill out the
information for the MAINTENANCE CLEANUP TASK so that old backups get
deleted.
Is that what you are looking for?
RLF
"David C" <dlchase@.lifetimeinc.com> wrote in message
news:OFL4DY5MIHA.5400@.TK2MSFTNGP04.phx.gbl...
>I want to create a simple SQL 2005 database backup script to run a
>scheduled times. This was easy with SQL 2000 but I can't find a similar
>process in 2005. Can anyone tell me where I can find it? Thanks.
> David
>
|||Alternatively,
In SQL Server 2005 every nearly window is scriptable. So, go to a database
and right click on it and Tasks\Back up... make your changes from the GUI
and you'll see a button on top of the Back Up Database window which is
labeled "Script". There is an arrow near it, click on it and you'll see your
choices.
You can use these scripts to create Jobs from the SQL Server Agent.
Ekrem nsoy
"David C" <dlchase@.lifetimeinc.com> wrote in message
news:OFL4DY5MIHA.5400@.TK2MSFTNGP04.phx.gbl...
>I want to create a simple SQL 2005 database backup script to run a
>scheduled times. This was easy with SQL 2000 but I can't find a similar
>process in 2005. Can anyone tell me where I can find it? Thanks.
> David
>
|||Thank you both. That is what I needed.
David
"Ekrem nsoy" <ekrem@.btegitim.com> wrote in message
news:D82FA9CF-70A7-4802-A7C2-8C1BA3B053E8@.microsoft.com...
> Alternatively,
> In SQL Server 2005 every nearly window is scriptable. So, go to a database
> and right click on it and Tasks\Back up... make your changes from the GUI
> and you'll see a button on top of the Back Up Database window which is
> labeled "Script". There is an arrow near it, click on it and you'll see
> your choices.
> You can use these scripts to create Jobs from the SQL Server Agent.
> --
> Ekrem nsoy
>
> "David C" <dlchase@.lifetimeinc.com> wrote in message
> news:OFL4DY5MIHA.5400@.TK2MSFTNGP04.phx.gbl...
>
sql

backup restore question

Hi,
I wanted to clarify something about the backup restore process. If have the
following backups -
Day1 - 3 AM - Full backup
Day1 - 9 AM - Log backup
Day1 - 3 PM - Log backup
Day1 - 9 PM - Log backup
Day2 - 3 AM - Full backup
Day2 - 9 AM - Log backup
Day2 - 3 PM - Log backup
Day2 - 9 PM - Log backup
I want to restore the database to a point in time of 9 PM on Day2. The Full
backup of Day2 is corrupt. Can I restore the database by applying the
following backups in sequence -
Day1 - 3 AM - Full backup - not recovered
Day1 - 9 AM - Log backup - not recovered
Day1 - 3 PM - Log backup - not recovered
Day1 - 9 PM - Log backup - not recovered
Day2 - 9 AM - Log backup - not recovered
Day2 - 3 PM - Log backup - not recovered
Day2 - 9 PM - Log backup - recovered
Thanks in advance.
sharman,
Yes, if none of your log files are corrupt, you can indeed apply them over a
missing full backup, just as you describe. (Thus explaining, for anyone who
wondered, why the full backup does not free up the transaction log.)
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDA7766C-91AB-49E5-85F2-696B1807D59B@.microsoft.com...
> Hi,
> I wanted to clarify something about the backup restore process. If have
> the
> following backups -
> Day1 - 3 AM - Full backup
> Day1 - 9 AM - Log backup
> Day1 - 3 PM - Log backup
> Day1 - 9 PM - Log backup
> Day2 - 3 AM - Full backup
> Day2 - 9 AM - Log backup
> Day2 - 3 PM - Log backup
> Day2 - 9 PM - Log backup
> I want to restore the database to a point in time of 9 PM on Day2. The
> Full
> backup of Day2 is corrupt. Can I restore the database by applying the
> following backups in sequence -
> Day1 - 3 AM - Full backup - not recovered
> Day1 - 9 AM - Log backup - not recovered
> Day1 - 3 PM - Log backup - not recovered
> Day1 - 9 PM - Log backup - not recovered
> Day2 - 9 AM - Log backup - not recovered
> Day2 - 3 PM - Log backup - not recovered
> Day2 - 9 PM - Log backup - recovered
> Thanks in advance.
>
>

backup restore question

Hi,
I wanted to clarify something about the backup restore process. If have the
following backups -
Day1 - 3 AM - Full backup
Day1 - 9 AM - Log backup
Day1 - 3 PM - Log backup
Day1 - 9 PM - Log backup
Day2 - 3 AM - Full backup
Day2 - 9 AM - Log backup
Day2 - 3 PM - Log backup
Day2 - 9 PM - Log backup
I want to restore the database to a point in time of 9 PM on Day2. The Full
backup of Day2 is corrupt. Can I restore the database by applying the
following backups in sequence -
Day1 - 3 AM - Full backup - not recovered
Day1 - 9 AM - Log backup - not recovered
Day1 - 3 PM - Log backup - not recovered
Day1 - 9 PM - Log backup - not recovered
Day2 - 9 AM - Log backup - not recovered
Day2 - 3 PM - Log backup - not recovered
Day2 - 9 PM - Log backup - recovered
Thanks in advance.sharman,
Yes, if none of your log files are corrupt, you can indeed apply them over a
missing full backup, just as you describe. (Thus explaining, for anyone who
wondered, why the full backup does not free up the transaction log.)
RLF
"sharman" <sharman@.discussions.microsoft.com> wrote in message
news:CDA7766C-91AB-49E5-85F2-696B1807D59B@.microsoft.com...
> Hi,
> I wanted to clarify something about the backup restore process. If have
> the
> following backups -
> Day1 - 3 AM - Full backup
> Day1 - 9 AM - Log backup
> Day1 - 3 PM - Log backup
> Day1 - 9 PM - Log backup
> Day2 - 3 AM - Full backup
> Day2 - 9 AM - Log backup
> Day2 - 3 PM - Log backup
> Day2 - 9 PM - Log backup
> I want to restore the database to a point in time of 9 PM on Day2. The
> Full
> backup of Day2 is corrupt. Can I restore the database by applying the
> following backups in sequence -
> Day1 - 3 AM - Full backup - not recovered
> Day1 - 9 AM - Log backup - not recovered
> Day1 - 3 PM - Log backup - not recovered
> Day1 - 9 PM - Log backup - not recovered
> Day2 - 9 AM - Log backup - not recovered
> Day2 - 3 PM - Log backup - not recovered
> Day2 - 9 PM - Log backup - recovered
> Thanks in advance.
>
>

Backup process lock others out of DB?

I had a backup fail on PM run because of diskspace issue. Fixed that and ran
the job this AM. It just about crippled our DB, and my web-server couldn't
get data, just time outs.
Is this normal for the DB backup to override requests for data? If so are
there other backup software packages to create a .bak file instead of EM's
jobs?
TIA
__Stephen
No, its not normal...were you writing to the same disk that the datafile(s)
reside on?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:O2wtHkv3FHA.1396@.TK2MSFTNGP12.phx.gbl...
>I had a backup fail on PM run because of diskspace issue. Fixed that and
>ran the job this AM. It just about crippled our DB, and my web-server
>couldn't get data, just time outs.
> Is this normal for the DB backup to override requests for data? If so are
> there other backup software packages to create a .bak file instead of EM's
> jobs?
> TIA
> __Stephen
>
|||"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:eSJ%23IEw3FHA.696@.TK2MSFTNGP09.phx.gbl...
> No, its not normal...were you writing to the same disk that the
> datafile(s) reside on?
No I write to a separate server for all backups and transaction logs. I
didn't think it was correct either.
Actually my server was getting hammered with batch work at the time. It's
Tues. morning so lets try to batch in 20% of our weekly business. I do a
tran log backup every 15 min and the one this morning at the time things got
hairy was only 514 meg. Normally its in the 5+ meg range. So that massive
file is an indication that I'll be beating on my system hard for the next
hour or two. We are a print shop and we feed 3 Xerox doc-u-beasts doing
financial outputs and checks.

Backup process lock others out of DB?

I had a backup fail on PM run because of diskspace issue. Fixed that and ran
the job this AM. It just about crippled our DB, and my web-server couldn't
get data, just time outs.
Is this normal for the DB backup to override requests for data? If so are
there other backup software packages to create a .bak file instead of EM's
jobs?
TIA
__StephenNo, its not normal...were you writing to the same disk that the datafile(s)
reside on?
--
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:O2wtHkv3FHA.1396@.TK2MSFTNGP12.phx.gbl...
>I had a backup fail on PM run because of diskspace issue. Fixed that and
>ran the job this AM. It just about crippled our DB, and my web-server
>couldn't get data, just time outs.
> Is this normal for the DB backup to override requests for data? If so are
> there other backup software packages to create a .bak file instead of EM's
> jobs?
> TIA
> __Stephen
>|||"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:eSJ%23IEw3FHA.696@.TK2MSFTNGP09.phx.gbl...
> No, its not normal...were you writing to the same disk that the
> datafile(s) reside on?
No I write to a separate server for all backups and transaction logs. I
didn't think it was correct either.
Actually my server was getting hammered with batch work at the time. It's
Tues. morning so lets try to batch in 20% of our weekly business. I do a
tran log backup every 15 min and the one this morning at the time things got
hairy was only 514 meg. Normally its in the 5+ meg range. So that massive
file is an indication that I'll be beating on my system hard for the next
hour or two. We are a print shop and we feed 3 Xerox doc-u-beasts doing
financial outputs and checks.

Backup process lock others out of DB?

I had a backup fail on PM run because of diskspace issue. Fixed that and ran
the job this AM. It just about crippled our DB, and my web-server couldn't
get data, just time outs.
Is this normal for the DB backup to override requests for data? If so are
there other backup software packages to create a .bak file instead of EM's
jobs?
TIA
__StephenNo, its not normal...were you writing to the same disk that the datafile(s)
reside on?
Kevin Hill
President
3NF Consulting
www.3nf-inc.com/NewsGroups.htm
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:O2wtHkv3FHA.1396@.TK2MSFTNGP12.phx.gbl...
>I had a backup fail on PM run because of diskspace issue. Fixed that and
>ran the job this AM. It just about crippled our DB, and my web-server
>couldn't get data, just time outs.
> Is this normal for the DB backup to override requests for data? If so are
> there other backup software packages to create a .bak file instead of EM's
> jobs?
> TIA
> __Stephen
>|||"Kevin3NF" <KHill@.NopeIDontNeedNoSPAM3NF-inc.com> wrote in message
news:eSJ%23IEw3FHA.696@.TK2MSFTNGP09.phx.gbl...
> No, its not normal...were you writing to the same disk that the
> datafile(s) reside on?
No I write to a separate server for all backups and transaction logs. I
didn't think it was correct either.
Actually my server was getting hammered with batch work at the time. It's
Tues. morning so lets try to batch in 20% of our weekly business. I do a
tran log backup every 15 min and the one this morning at the time things got
hairy was only 514 meg. Normally its in the 5+ meg range. So that massive
file is an indication that I'll be beating on my system hard for the next
hour or two. We are a print shop and we feed 3 Xerox doc-u-beasts doing
financial outputs and checks.

Backup process hanging?

Hi everybody
OS is Win2000 with latest SP.
Microsoft SQL Server 7.00 - 7.00.842.
The problem is that there is a backup-process that is
runnable but wont finish or timeout. When i am trying to
kill the process nothing happens. It is still there!?!
Can someone maybe give some pointers to what i should do
to get ride of this process.
As it is now i cannot take a backup of the database the
backup process is hanged on.
/Risun
Hi,
From the SQL Server machine, Open Query Analyzer and execute the below
comamnd and see whether it suceeds.
Ensure that an existing Backup process is not going on.
BACKUP database <dbname> to disk='d:\backup\dbname.bak' with init , stats=10
Init parameter will overwrite the backup filr every time and stats=10 , will
show the percentage completed.
Note:
See the CPU and Memory usage of server.
Thanks
Hari
MCDBA
"Risun" <risun@.wmdata.com> wrote in message
news:1f69101c45781$a986adb0$a001280a@.phx.gbl...
> Hi everybody
> OS is Win2000 with latest SP.
> Microsoft SQL Server 7.00 - 7.00.842.
> The problem is that there is a backup-process that is
> runnable but wont finish or timeout. When i am trying to
> kill the process nothing happens. It is still there!?!
> Can someone maybe give some pointers to what i should do
> to get ride of this process.
> As it is now i cannot take a backup of the database the
> backup process is hanged on.
> /Risun
|||Ehh, but the problem is that the previous backup-process
will not die/go away/disappear. I have tried to kill the
process from the EM and with T-sql. It still remains.
The solution i am trying to avoid is stopping and starting
the MSSQLSERVER service. But as it is now i cannot see
another solution.
Trying to take a backup isnt possible as long as this
process is still alive.
Please, how can i kill this sucker.
/Risun

>--Original Message--
>Hi,
>From the SQL Server machine, Open Query Analyzer and
execute the below
>comamnd and see whether it suceeds.
>Ensure that an existing Backup process is not going on.
>BACKUP database <dbname> to disk='d:\backup\dbname.bak'
with init , stats=10
>Init parameter will overwrite the backup filr every time
and stats=10 , will
>show the percentage completed.
>Note:
>See the CPU and Memory usage of server.
>--
>Thanks
>Hari
>MCDBA
>"Risun" <risun@.wmdata.com> wrote in message
>news:1f69101c45781$a986adb0$a001280a@.phx.gbl...
>
>.
>
|||If you can not kill it from SQL, you might try to kil the process from Task
manager, but I suspect you will have to stop/start SQL Server service..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Risun" <risun@.wmdata.com> wrote in message
news:1f69101c45781$a986adb0$a001280a@.phx.gbl...
> Hi everybody
> OS is Win2000 with latest SP.
> Microsoft SQL Server 7.00 - 7.00.842.
> The problem is that there is a backup-process that is
> runnable but wont finish or timeout. When i am trying to
> kill the process nothing happens. It is still there!?!
> Can someone maybe give some pointers to what i should do
> to get ride of this process.
> As it is now i cannot take a backup of the database the
> backup process is hanged on.
> /Risun
|||Hi,
If you kill the BACKUP process mostly that process will not be removed from
the process list. The only solution is to stop and start the MSSQL Server
service.
Why do you need to kill the backup process. Use my previous post (BACKUP
DATABASE) command
to backup the database. STATS=10 parameter will give you the percentage of
backup completed.
INF: Understanding How the Transact-SQL KILL Command Works
http://support.microsoft.com/default...microsoft.com:
80/support/kb/articles/Q171/2/24.ASP&NoWebContent=1
Thanks
Hari
MCDBA
"Risun" <risun@.wmdata.com> wrote in message
news:1ef1e01c4578c$55d2e8e0$a301280a@.phx.gbl...[vbcol=seagreen]
> Ehh, but the problem is that the previous backup-process
> will not die/go away/disappear. I have tried to kill the
> process from the EM and with T-sql. It still remains.
> The solution i am trying to avoid is stopping and starting
> the MSSQLSERVER service. But as it is now i cannot see
> another solution.
> Trying to take a backup isnt possible as long as this
> process is still alive.
> Please, how can i kill this sucker.
> /Risun
> execute the below
> with init , stats=10
> and stats=10 , will

Backup process hanging?

Hi everybody
OS is Win2000 with latest SP.
Microsoft SQL Server 7.00 - 7.00.842.
The problem is that there is a backup-process that is
runnable but wont finish or timeout. When i am trying to
kill the process nothing happens. It is still there!?!
Can someone maybe give some pointers to what i should do
to get ride of this process.
As it is now i cannot take a backup of the database the
backup process is hanged on.
/RisunHi,
From the SQL Server machine, Open Query Analyzer and execute the below
comamnd and see whether it suceeds.
Ensure that an existing Backup process is not going on.
BACKUP database <dbname> to disk='d:\backup\dbname.bak' with init , stats=10
Init parameter will overwrite the backup filr every time and stats=10 , will
show the percentage completed.
Note:
See the CPU and Memory usage of server.
Thanks
Hari
MCDBA
"Risun" <risun@.wmdata.com> wrote in message
news:1f69101c45781$a986adb0$a001280a@.phx
.gbl...
> Hi everybody
> OS is Win2000 with latest SP.
> Microsoft SQL Server 7.00 - 7.00.842.
> The problem is that there is a backup-process that is
> runnable but wont finish or timeout. When i am trying to
> kill the process nothing happens. It is still there!?!
> Can someone maybe give some pointers to what i should do
> to get ride of this process.
> As it is now i cannot take a backup of the database the
> backup process is hanged on.
> /Risun|||Ehh, but the problem is that the previous backup-process
will not die/go away/disappear. I have tried to kill the
process from the EM and with T-sql. It still remains.
The solution i am trying to avoid is stopping and starting
the MSSQLSERVER service. But as it is now i cannot see
another solution.
Trying to take a backup isnt possible as long as this
process is still alive.
Please, how can i kill this sucker.
/Risun

>--Original Message--
>Hi,
>From the SQL Server machine, Open Query Analyzer and
execute the below
>comamnd and see whether it suceeds.
>Ensure that an existing Backup process is not going on.
>BACKUP database <dbname> to disk='d:\backup\dbname.bak'
with init , stats=10
>Init parameter will overwrite the backup filr every time
and stats=10 , will
>show the percentage completed.
>Note:
>See the CPU and Memory usage of server.
>--
>Thanks
>Hari
>MCDBA
>"Risun" <risun@.wmdata.com> wrote in message
> news:1f69101c45781$a986adb0$a001280a@.phx
.gbl...
>
>.
>|||If you can not kill it from SQL, you might try to kil the process from Task
manager, but I suspect you will have to stop/start SQL Server service..
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Risun" <risun@.wmdata.com> wrote in message
news:1f69101c45781$a986adb0$a001280a@.phx
.gbl...
> Hi everybody
> OS is Win2000 with latest SP.
> Microsoft SQL Server 7.00 - 7.00.842.
> The problem is that there is a backup-process that is
> runnable but wont finish or timeout. When i am trying to
> kill the process nothing happens. It is still there!?!
> Can someone maybe give some pointers to what i should do
> to get ride of this process.
> As it is now i cannot take a backup of the database the
> backup process is hanged on.
> /Risun|||Hi,
If you kill the BACKUP process mostly that process will not be removed from
the process list. The only solution is to stop and start the MSSQL Server
service.
Why do you need to kill the backup process. Use my previous post (BACKUP
DATABASE) command
to backup the database. STATS=10 parameter will give you the percentage of
backup completed.
INF: Understanding How the Transact-SQL KILL Command Works
http://support.microsoft.com/defaul...microsoft.com:
80/support/kb/articles/Q171/2/24.ASP&NoWebContent=1
Thanks
Hari
MCDBA
"Risun" <risun@.wmdata.com> wrote in message
news:1ef1e01c4578c$55d2e8e0$a301280a@.phx
.gbl...[vbcol=seagreen]
> Ehh, but the problem is that the previous backup-process
> will not die/go away/disappear. I have tried to kill the
> process from the EM and with T-sql. It still remains.
> The solution i am trying to avoid is stopping and starting
> the MSSQLSERVER service. But as it is now i cannot see
> another solution.
> Trying to take a backup isnt possible as long as this
> process is still alive.
> Please, how can i kill this sucker.
> /Risun
>
> execute the below
> with init , stats=10
> and stats=10 , will

Backup process hanging?

Hi everybody
OS is Win2000 with latest SP.
Microsoft SQL Server 7.00 - 7.00.842.
The problem is that there is a backup-process that is
runnable but wont finish or timeout. When i am trying to
kill the process nothing happens. It is still there!?!
Can someone maybe give some pointers to what i should do
to get ride of this process.
As it is now i cannot take a backup of the database the
backup process is hanged on.
/RisunHi,
From the SQL Server machine, Open Query Analyzer and execute the below
comamnd and see whether it suceeds.
Ensure that an existing Backup process is not going on.
BACKUP database <dbname> to disk='d:\backup\dbname.bak' with init , stats=10
Init parameter will overwrite the backup filr every time and stats=10 , will
show the percentage completed.
Note:
See the CPU and Memory usage of server.
--
Thanks
Hari
MCDBA
"Risun" <risun@.wmdata.com> wrote in message
news:1f69101c45781$a986adb0$a001280a@.phx.gbl...
> Hi everybody
> OS is Win2000 with latest SP.
> Microsoft SQL Server 7.00 - 7.00.842.
> The problem is that there is a backup-process that is
> runnable but wont finish or timeout. When i am trying to
> kill the process nothing happens. It is still there!?!
> Can someone maybe give some pointers to what i should do
> to get ride of this process.
> As it is now i cannot take a backup of the database the
> backup process is hanged on.
> /Risun|||Ehh, but the problem is that the previous backup-process
will not die/go away/disappear. I have tried to kill the
process from the EM and with T-sql. It still remains.
The solution i am trying to avoid is stopping and starting
the MSSQLSERVER service. But as it is now i cannot see
another solution.
Trying to take a backup isnt possible as long as this
process is still alive.
Please, how can i kill this sucker.
/Risun
>--Original Message--
>Hi,
>From the SQL Server machine, Open Query Analyzer and
execute the below
>comamnd and see whether it suceeds.
>Ensure that an existing Backup process is not going on.
>BACKUP database <dbname> to disk='d:\backup\dbname.bak'
with init , stats=10
>Init parameter will overwrite the backup filr every time
and stats=10 , will
>show the percentage completed.
>Note:
>See the CPU and Memory usage of server.
>--
>Thanks
>Hari
>MCDBA
>"Risun" <risun@.wmdata.com> wrote in message
>news:1f69101c45781$a986adb0$a001280a@.phx.gbl...
>> Hi everybody
>> OS is Win2000 with latest SP.
>> Microsoft SQL Server 7.00 - 7.00.842.
>> The problem is that there is a backup-process that is
>> runnable but wont finish or timeout. When i am trying to
>> kill the process nothing happens. It is still there!?!
>> Can someone maybe give some pointers to what i should do
>> to get ride of this process.
>> As it is now i cannot take a backup of the database the
>> backup process is hanged on.
>> /Risun
>
>.
>|||If you can not kill it from SQL, you might try to kil the process from Task
manager, but I suspect you will have to stop/start SQL Server service..
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Risun" <risun@.wmdata.com> wrote in message
news:1f69101c45781$a986adb0$a001280a@.phx.gbl...
> Hi everybody
> OS is Win2000 with latest SP.
> Microsoft SQL Server 7.00 - 7.00.842.
> The problem is that there is a backup-process that is
> runnable but wont finish or timeout. When i am trying to
> kill the process nothing happens. It is still there!?!
> Can someone maybe give some pointers to what i should do
> to get ride of this process.
> As it is now i cannot take a backup of the database the
> backup process is hanged on.
> /Risun|||Hi,
If you kill the BACKUP process mostly that process will not be removed from
the process list. The only solution is to stop and start the MSSQL Server
service.
Why do you need to kill the backup process. Use my previous post (BACKUP
DATABASE) command
to backup the database. STATS=10 parameter will give you the percentage of
backup completed.
INF: Understanding How the Transact-SQL KILL Command Works
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:
80/support/kb/articles/Q171/2/24.ASP&NoWebContent=1
Thanks
Hari
MCDBA
"Risun" <risun@.wmdata.com> wrote in message
news:1ef1e01c4578c$55d2e8e0$a301280a@.phx.gbl...
> Ehh, but the problem is that the previous backup-process
> will not die/go away/disappear. I have tried to kill the
> process from the EM and with T-sql. It still remains.
> The solution i am trying to avoid is stopping and starting
> the MSSQLSERVER service. But as it is now i cannot see
> another solution.
> Trying to take a backup isnt possible as long as this
> process is still alive.
> Please, how can i kill this sucker.
> /Risun
> >--Original Message--
> >Hi,
> >
> >From the SQL Server machine, Open Query Analyzer and
> execute the below
> >comamnd and see whether it suceeds.
> >Ensure that an existing Backup process is not going on.
> >
> >BACKUP database <dbname> to disk='d:\backup\dbname.bak'
> with init , stats=10
> >
> >Init parameter will overwrite the backup filr every time
> and stats=10 , will
> >show the percentage completed.
> >
> >Note:
> >
> >See the CPU and Memory usage of server.
> >
> >--
> >Thanks
> >Hari
> >MCDBA
> >"Risun" <risun@.wmdata.com> wrote in message
> >news:1f69101c45781$a986adb0$a001280a@.phx.gbl...
> >> Hi everybody
> >>
> >> OS is Win2000 with latest SP.
> >> Microsoft SQL Server 7.00 - 7.00.842.
> >>
> >> The problem is that there is a backup-process that is
> >> runnable but wont finish or timeout. When i am trying to
> >> kill the process nothing happens. It is still there!?!
> >>
> >> Can someone maybe give some pointers to what i should do
> >> to get ride of this process.
> >> As it is now i cannot take a backup of the database the
> >> backup process is hanged on.
> >>
> >> /Risun
> >
> >
> >.
> >

backup problem 2

Has anyone encountered a situation where the backup process is still
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
AramidHi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:
> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
>Hi
>Run sp_who2 during the process. You will see if the backup is still running.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
>> Has anyone encountered a situation where the backup process is still
>> running but Enterprise Manager already says that it was finished and
>> was successful.
>> I initiated a backup to a UNC share (but the actual drive is directly
>> attached to the server) and the backup started. I see the size of the
>> backup file increasing (via Windows Explorer) so I assumed everything
>> is okay. After about 10% was done, EM suddenly showed me the usual
>> "The backup operation has completed successfully" window, but the size
>> of the backup file continued increasing...and apparently went on an
>> on, up to the expected size of the backup. Upon checking (restore),
>> the backup file was okay.
>> Has anyone encountered a similar situation? Any thoughts on this?
>>
>> Aramid|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK => N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME => N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
> >Hi
> >
> >Run sp_who2 during the process. You will see if the backup is still
running.
> >What does the job history say about the run time? Does it match the file
> >datetime stamp?
> >
> >Regards
> >Mike
> >
> >
> >"aramid" wrote:
> >
> >> Has anyone encountered a situation where the backup process is still
> >> running but Enterprise Manager already says that it was finished and
> >> was successful.
> >>
> >> I initiated a backup to a UNC share (but the actual drive is directly
> >> attached to the server) and the backup started. I see the size of the
> >> backup file increasing (via Windows Explorer) so I assumed everything
> >> is okay. After about 10% was done, EM suddenly showed me the usual
> >> "The backup operation has completed successfully" window, but the size
> >> of the backup file continued increasing...and apparently went on an
> >> on, up to the expected size of the backup. Upon checking (restore),
> >> the backup file was okay.
> >>
> >> Has anyone encountered a similar situation? Any thoughts on this?
> >>
> >>
> >> Aramid
> >>
>|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:
>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/default.aspx?scid=kb;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
>news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
>> Thanks, Mike.
>> I did monitor the backup process via sp_who2 and also did a TSQL
>> backup via QA as:
>> BACKUP DATABASE [database_namer] TO DISK =>> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =>> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
>> After about 1 minute, the error below shows up in QA:
>> =====>> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
>> (WrapperRead()).
>> Server: Msg 11, Level 16, State 1, Line 0
>> General network error. Check your network documentation.
>> 10 percent backed up.
>> Connection Broken
>> =====>> Running sp_who2 shows that my QA connection still exists and is
>> running. The backup eventually completes without any problem from
>> this point onwards.
>> I did this several times, just to check if the pattern is consistent,
>> and it is. I also noticed that running something else on the QA
>> window (after the error has showed itself) where I ran the backup
>> command will immediately stop the "background backup" (tantamount to
>> killing the spid) and execute my new command (such as sp_who2).
>> Note that I am using the QA on the server itself, not from some remote
>> machine.
>> Aramid
>>
>> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
>> <mike@.epprecht.net> wrote:
>> >Hi
>> >
>> >Run sp_who2 during the process. You will see if the backup is still
>running.
>> >What does the job history say about the run time? Does it match the file
>> >datetime stamp?
>> >
>> >Regards
>> >Mike
>> >
>> >
>> >"aramid" wrote:
>> >
>> >> Has anyone encountered a situation where the backup process is still
>> >> running but Enterprise Manager already says that it was finished and
>> >> was successful.
>> >>
>> >> I initiated a backup to a UNC share (but the actual drive is directly
>> >> attached to the server) and the backup started. I see the size of the
>> >> backup file increasing (via Windows Explorer) so I assumed everything
>> >> is okay. After about 10% was done, EM suddenly showed me the usual
>> >> "The backup operation has completed successfully" window, but the size
>> >> of the backup file continued increasing...and apparently went on an
>> >> on, up to the expected size of the backup. Upon checking (restore),
>> >> the backup file was okay.
>> >>
>> >> Has anyone encountered a similar situation? Any thoughts on this?
>> >>
>> >>
>> >> Aramid
>> >>
>

backup problem 2

Has anyone encountered a situation where the backup process is still
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
AramidHi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:

> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =
N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
[vbcol=seagreen]
>Hi
>Run sp_who2 during the process. You will see if the backup is still running
.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
>|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/defaul...kb;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.
4ax.com ?...
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK =
> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====
> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
>
running.[vbcol=seagreen]
>|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:

>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/defaul...kb;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
> news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.
4ax.com ?...
>running.
>

backup problem 2

Has anyone encountered a situation where the backup process is still
running but Enterprise Manager already says that it was finished and
was successful.
I initiated a backup to a UNC share (but the actual drive is directly
attached to the server) and the backup started. I see the size of the
backup file increasing (via Windows Explorer) so I assumed everything
is okay. After about 10% was done, EM suddenly showed me the usual
"The backup operation has completed successfully" window, but the size
of the backup file continued increasing...and apparently went on an
on, up to the expected size of the backup. Upon checking (restore),
the backup file was okay.
Has anyone encountered a similar situation? Any thoughts on this?
Aramid
Hi
Run sp_who2 during the process. You will see if the backup is still running.
What does the job history say about the run time? Does it match the file
datetime stamp?
Regards
Mike
"aramid" wrote:

> Has anyone encountered a situation where the backup process is still
> running but Enterprise Manager already says that it was finished and
> was successful.
> I initiated a backup to a UNC share (but the actual drive is directly
> attached to the server) and the backup started. I see the size of the
> backup file increasing (via Windows Explorer) so I assumed everything
> is okay. After about 10% was done, EM suddenly showed me the usual
> "The backup operation has completed successfully" window, but the size
> of the backup file continued increasing...and apparently went on an
> on, up to the expected size of the backup. Upon checking (restore),
> the backup file was okay.
> Has anyone encountered a similar situation? Any thoughts on this?
>
> Aramid
>
|||Thanks, Mike.
I did monitor the backup process via sp_who2 and also did a TSQL
backup via QA as:
BACKUP DATABASE [database_namer] TO DISK =
N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
After about 1 minute, the error below shows up in QA:
=====
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
(WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
10 percent backed up.
Connection Broken
=====
Running sp_who2 shows that my QA connection still exists and is
running. The backup eventually completes without any problem from
this point onwards.
I did this several times, just to check if the pattern is consistent,
and it is. I also noticed that running something else on the QA
window (after the error has showed itself) where I ran the backup
command will immediately stop the "background backup" (tantamount to
killing the spid) and execute my new command (such as sp_who2).
Note that I am using the QA on the server itself, not from some remote
machine.
Aramid
On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
<mike@.epprecht.net> wrote:
[vbcol=seagreen]
>Hi
>Run sp_who2 during the process. You will see if the backup is still running.
>What does the job history say about the run time? Does it match the file
>datetime stamp?
>Regards
>Mike
>
>"aramid" wrote:
|||Dear Aramid,
I seems encounter similar problem.
At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
with XP sp2 or Win2003),
I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
SP1 yet).
The reason why I guess so? Check out
http://support.microsoft.com/default...b;en-us;827452
Hope it does not mislead you anyway ... Eric
"aramid" <aramid@.hotmail.com> ?
news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...[vbcol=seagreen]
> Thanks, Mike.
> I did monitor the backup process via sp_who2 and also did a TSQL
> backup via QA as:
> BACKUP DATABASE [database_namer] TO DISK =
> N'F:\temp\database_name_041105' WITH INIT , NOUNLOAD , NAME =
> N'Database_Name backup', NOSKIP , STATS = 10, NOFORMAT
> After about 1 minute, the error below shows up in QA:
> =====
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead
> (WrapperRead()).
> Server: Msg 11, Level 16, State 1, Line 0
> General network error. Check your network documentation.
> 10 percent backed up.
> Connection Broken
> =====
> Running sp_who2 shows that my QA connection still exists and is
> running. The backup eventually completes without any problem from
> this point onwards.
> I did this several times, just to check if the pattern is consistent,
> and it is. I also noticed that running something else on the QA
> window (after the error has showed itself) where I ran the backup
> command will immediately stop the "background backup" (tantamount to
> killing the spid) and execute my new command (such as sp_who2).
> Note that I am using the QA on the server itself, not from some remote
> machine.
> Aramid
>
> On Mon, 11 Apr 2005 00:35:02 -0700, "Mike Epprecht (SQL MVP)"
> <mike@.epprecht.net> wrote:
running.
>
|||Thanks, Eric.
I will check this out.
Aramid
On Tue, 12 Apr 2005 18:31:26 +0800, "Eric Fung" <Pls type eric.fung
plus @.hld.com> wrote:

>Dear Aramid,
>I seems encounter similar problem.
>At the moment, I am suspecting it is caused by MDAC 2.8 (which is installed
>with XP sp2 or Win2003),
>I am just asking if someone on the forum got latest MDAC 2.8 hot fix (as no
>SP1 yet).
>The reason why I guess so? Check out
>http://support.microsoft.com/default...b;en-us;827452
>Hope it does not mislead you anyway ... Eric
>
>"aramid" <aramid@.hotmail.com> ?
>news:hpkm51hcbgo183qaop05ju4mi7s6pitrdi@.4ax.com ?...
>running.
>

Backup into individual folders or create timestamps

Hi there,
I am using SQL 2000 SP2 and am trying to establish a viable backup
process. I want to be able to automate backing up databases and then
have them moved to a folder on a file server.
Since I have discovered that I can't backup to a mapped drive I am
having to backup locally. What I want to do though is backup daily and
have it create separate backups per day. I don't want to overwrite
what is currently there, I want it to create a backup called e.g.
Backup_220903, and then on Tuesday create another file called
Backup_230903 and so on.
After that I then need a reliable way of having the files copied
automatically to my remote file server
Does anyone know how I can do this'
Many thanks in advanceYou can backup directly to the network folder.
You need to use the full UNC name. Example :-
BACKUP DATABASE Dbname TO DISK = \\servername\sharename\backup.bak WITH INIT
--
HTH
Ryan Waight, MCDBA, MCSE
"Derek" <dryan@.legendware.co.uk> wrote in message
news:72938c9c.0309220639.55a36e94@.posting.google.com...
> Hi there,
> I am using SQL 2000 SP2 and am trying to establish a viable backup
> process. I want to be able to automate backing up databases and then
> have them moved to a folder on a file server.
> Since I have discovered that I can't backup to a mapped drive I am
> having to backup locally. What I want to do though is backup daily and
> have it create separate backups per day. I don't want to overwrite
> what is currently there, I want it to create a backup called e.g.
> Backup_220903, and then on Tuesday create another file called
> Backup_230903 and so on.
> After that I then need a reliable way of having the files copied
> automatically to my remote file server
> Does anyone know how I can do this'
> Many thanks in advance

Backup Getting locked

Hello, I do a full backup daily on a user database. I received an error
telling we the backup failed. (Operating system error = 32(The process
cannot access the file because it is being used by another process.)). How
can I tell what process is locking the file?Don
http://support.microsoft.com/default.aspx?scid=kb;en-us;287309&sd=tech
http://support.microsoft.com/?id=833167
"Don" <dons100@.ameritech.net> wrote in message
news:wvLyf.20196$or4.18846@.newssvr12.news.prodigy.com...
> Hello, I do a full backup daily on a user database. I received an error
> telling we the backup failed. (Operating system error = 32(The process
> cannot access the file because it is being used by another process.)).
> How
> can I tell what process is locking the file?
>