Backup Strategy

I am a newbie to SQL.
I am running SQL 2000 on a SBS 2003 R2 box. What is the best way to make
sure our databases are backed up in the event of a data loss or a crash?
Thanks,
Rich
The easiest way is to create a maintenance plan using the SQL Enterprise
Manager.
Or you can create jobs that use T-SQL statement to backup the databases.
Always make sure that the backup's are stored on offline storage, eg another
server or tapes.
The best way depends or your businessneeds and databasesize.
Robert Hartskeerl, MCTS
http://hartskeerl.nl/blogs/robert/
"Rikellent" wrote:

> I am a newbie to SQL.
> I am running SQL 2000 on a SBS 2003 R2 box. What is the best way to make
> sure our databases are backed up in the event of a data loss or a crash?
> Thanks,
> Rich
|||Hello,
You could use the maintenence wizard to create a backup plan and schedule
it. But I had lot of issues with maintenanceplans and so i went for TSQL
backup
script and schedule it using SQL Server agent.
Take a look into the below article:-
http://www.microsoft.com/india/msdn/articles/185.aspx
Thanks
Hari
"Rikellent" <Rikellent@.discussions.microsoft.com> wrote in message
news:BB10385E-8923-4AF7-B5B8-75F7B44CD993@.microsoft.com...
>I am a newbie to SQL.
> I am running SQL 2000 on a SBS 2003 R2 box. What is the best way to make
> sure our databases are backed up in the event of a data loss or a crash?
> Thanks,
> Rich

Backup strategi

Hi all
I'm in the starting phase of creating a backup strategi for a new SQL Server box. It's a quite big installation with many databases and quite large databases (hundreds of Gbyte). I'm very famililiar with the SQL Server backup technology but I need some examples of strategies to "open up my mind". Does anybody have liks to examples for SQL Server backup strategies that will be very helpful. Maybe I don't have to reinvent the wheel..
Thanks!
FredrikHi,
Perform a full backup on the weekend and differential backups during the
week days , Hourly transaction log backups.
Have a look into the below link which contains the backup / restore
concepts with example:-
http://www.databasejournal.com/features/mssql/article.php/2232371
Thanks
Hari
MCDBA
"Fredrik" <anonymous@.discussions.microsoft.com> wrote in message
news:9322E3DE-20AB-422C-BAB5-0E66259B24FF@.microsoft.com...
> Hi all!
> I'm in the starting phase of creating a backup strategi for a new SQL
Server box. It's a quite big installation with many databases and quite
large databases (hundreds of Gbyte). I'm very famililiar with the SQL Server
backup technology but I need some examples of strategies to "open up my
mind". Does anybody have liks to examples for SQL Server backup strategies
that will be very helpful. Maybe I don't have to reinvent the wheel..
> Thanks!!
> Fredrik|||Fredrik..
We backup all databases using SQL LiteSpeed, which I highly recommend. Each backup job has three steps. After the DB is backed up locally to the SQL server in step 1, the second step is a CmdExec, which deletes the previous backup file located on a file server...
DEL /Q \\fileserver\SQLServers\SQLServerName\Database\
The third step copies the backup file from the SQL server to the file server..
COPY \\SQLServerName\E$\MSSQL\Backup\Database \\fileserver\SQLServers\SQLServerName\Database
We also do this for the hourly or 15 minute tran. log backups (depending on how much activity the DB has) that we do.
Tape backups are done locally on the file server every night.
Not overly complex, but I think it's a step in the right direction for covering ourselves in the case of a disaster
Let me know if you have any questions or suggestions. I'm always open to reviewing our current procedures
sean

Backup strategi

Hi all!
I'm in the starting phase of creating a backup strategi for a new SQL Server box. It's a quite big installation with many databases and quite large databases (hundreds of Gbyte). I'm very famililiar with the SQL Server backup technology but I need some ex
amples of strategies to "open up my mind". Does anybody have liks to examples for SQL Server backup strategies that will be very helpful. Maybe I don't have to reinvent the wheel..
Thanks!!
Fredrik
Hi,
Perform a full backup on the weekend and differential backups during the
week days , Hourly transaction log backups.
Have a look into the below link which contains the backup / restore
concepts with example:-
http://www.databasejournal.com/featu...le.php/2232371
Thanks
Hari
MCDBA
"Fredrik" <anonymous@.discussions.microsoft.com> wrote in message
news:9322E3DE-20AB-422C-BAB5-0E66259B24FF@.microsoft.com...
> Hi all!
> I'm in the starting phase of creating a backup strategi for a new SQL
Server box. It's a quite big installation with many databases and quite
large databases (hundreds of Gbyte). I'm very famililiar with the SQL Server
backup technology but I need some examples of strategies to "open up my
mind". Does anybody have liks to examples for SQL Server backup strategies
that will be very helpful. Maybe I don't have to reinvent the wheel..
> Thanks!!
> Fredrik
|||Thanks.
Acctually I was looking for solutions that are more complex . Not that my intention is to make a very complex solution but I really like to know what my options are.
I found one link that I thougt was interesting.
http://www.microsoft.com/technet/pro.../spltmirr.mspx
/Fredrik
|||Fredrik...
We backup all databases using SQL LiteSpeed, which I highly recommend. Each backup job has three steps. After the DB is backed up locally to the SQL server in step 1, the second step is a CmdExec, which deletes the previous backup file located on a file
server...
DEL /Q \\fileserver\SQLServers\SQLServerName\Database\*
The third step copies the backup file from the SQL server to the file server...
COPY \\SQLServerName\E$\MSSQL\Backup\Database \\fileserver\SQLServers\SQLServerName\Database
We also do this for the hourly or 15 minute tran. log backups (depending on how much activity the DB has) that we do.
Tape backups are done locally on the file server every night.
Not overly complex, but I think it's a step in the right direction for covering ourselves in the case of a disaster.
Let me know if you have any questions or suggestions. I'm always open to reviewing our current procedures.
sean
sql

Backup strategi

Hi all!
I'm in the starting phase of creating a backup strategi for a new SQL Server
box. It's a quite big installation with many databases and quite large data
bases (hundreds of Gbyte). I'm very famililiar with the SQL Server backup te
chnology but I need some ex
amples of strategies to "open up my mind". Does anybody have liks to example
s for SQL Server backup strategies that will be very helpful. Maybe I don't
have to reinvent the wheel..
Thanks!!
FredrikHi,
Perform a full backup on the weekend and differential backups during the
week days , Hourly transaction log backups.
Have a look into the below link which contains the backup / restore
concepts with example:-
http://www.databasejournal.com/feat...cle.php/2232371
Thanks
Hari
MCDBA
"Fredrik" <anonymous@.discussions.microsoft.com> wrote in message
news:9322E3DE-20AB-422C-BAB5-0E66259B24FF@.microsoft.com...
> Hi all!
> I'm in the starting phase of creating a backup strategi for a new SQL
Server box. It's a quite big installation with many databases and quite
large databases (hundreds of Gbyte). I'm very famililiar with the SQL Server
backup technology but I need some examples of strategies to "open up my
mind". Does anybody have liks to examples for SQL Server backup strategies
that will be very helpful. Maybe I don't have to reinvent the wheel..
> Thanks!!
> Fredrik|||Thanks.
Acctually I was looking for solutions that are more complex . Not that my in
tention is to make a very complex solution but I really like to know what my
options are.
I found one link that I thougt was interesting.
http://www.microsoft.com/technet/pr...n/spltmirr.mspx
/Fredrik|||Fredrik...
We backup all databases using SQL LiteSpeed, which I highly recommend. Each
backup job has three steps. After the DB is backed up locally to the SQL s
erver in step 1, the second step is a CmdExec, which deletes the previous ba
ckup file located on a file
server...
DEL /Q \\fileserver\SQLServers\SQLServerName\Da
tabase\*
The third step copies the backup file from the SQL server to the file server
..
COPY \\SQLServerName\E$\MSSQL\Backup\Database
\\fileserver\SQLServers\SQLSer
verName\Database
We also do this for the hourly or 15 minute tran. log backups (depending on
how much activity the DB has) that we do.
Tape backups are done locally on the file server every night.
Not overly complex, but I think it's a step in the right direction for cover
ing ourselves in the case of a disaster.
Let me know if you have any questions or suggestions. I'm always open to re
viewing our current procedures.
sean

Backup retention problem

Hi,
In my full backup maintenance Plan, I configured 1 day in a box 'Remove
files older than : "
The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
older than 1 day.
Why the maintenance Plan does'nt remove those files ?
What can cause this ?
How can I be alert by SQL if the maintenance plan is not able to delete the
..BAK files older than 1 day ?
Thanks
http://support.microsoft.com/default...b;en-us;303292
-- Log files don't delete --
http://support.microsoft.com/default...;en-us;Q303292
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Andrew J. Kelly SQL MVP
"Psa555" <Psa555@.discussions.microsoft.com> wrote in message
news:34A86E28-127A-4A50-B857-EF729A401790@.microsoft.com...
> Hi,
> In my full backup maintenance Plan, I configured 1 day in a box 'Remove
> files older than : "
> The problem is ... sometimes I have 3 or 4 files .BAK in my backup's
> folder
> older than 1 day.
> Why the maintenance Plan does'nt remove those files ?
> What can cause this ?
> How can I be alert by SQL if the maintenance plan is not able to delete
> the
> .BAK files older than 1 day ?
> Thanks
|||Hi,
If you have a mapi e-mail you can have a notification when the job fails.
Probably your status is that the job failed. You can install outlook 2000 or
outlook 2003 and create a new account for sending mails as f.e Database Admin.
Additionally, you can go to the maintenance plan properties and in the
Reporting tab you can tick the check box Write report a text file in
directory or any other option.
Hope that helped
Andreas
"Psa555" wrote:

> Hi,
> In my full backup maintenance Plan, I configured 1 day in a box 'Remove
> files older than : "
> The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
> older than 1 day.
> Why the maintenance Plan does'nt remove those files ?
> What can cause this ?
> How can I be alert by SQL if the maintenance plan is not able to delete the
> .BAK files older than 1 day ?
> Thanks
|||Because 1 day = 24 hours, exactly. If you job is off schedule or takes a
little longer to run than the prior day, even if by 1 minute, the time
stamps are only 23 hours, 59 minutes, etc., which is NOT 1 day.
I usually code mine to delete anything older than 3 hours. When it runs, it
will run the backup or reorg operation first, then it will check for files
to delete.
Sincerely,
Anthony Thomas

"Psa555" <Psa555@.discussions.microsoft.com> wrote in message
news:34A86E28-127A-4A50-B857-EF729A401790@.microsoft.com...
Hi,
In my full backup maintenance Plan, I configured 1 day in a box 'Remove
files older than : "
The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
older than 1 day.
Why the maintenance Plan does'nt remove those files ?
What can cause this ?
How can I be alert by SQL if the maintenance plan is not able to delete the
..BAK files older than 1 day ?
Thanks
sql

Backup retention problem

Hi,
In my full backup maintenance Plan, I configured 1 day in a box 'Remove
files older than : "
The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
older than 1 day.
Why the maintenance Plan does'nt remove those files ?
What can cause this ?
How can I be alert by SQL if the maintenance plan is not able to delete the
.BAK files older than 1 day ?
Thankshttp://support.microsoft.com/defaul...kb;en-us;303292
-- Log files don't delete --
http://support.microsoft.com/defaul...b;en-us;Q303292
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
Andrew J. Kelly SQL MVP
"Psa555" <Psa555@.discussions.microsoft.com> wrote in message
news:34A86E28-127A-4A50-B857-EF729A401790@.microsoft.com...
> Hi,
> In my full backup maintenance Plan, I configured 1 day in a box 'Remove
> files older than : "
> The problem is ... sometimes I have 3 or 4 files .BAK in my backup's
> folder
> older than 1 day.
> Why the maintenance Plan does'nt remove those files ?
> What can cause this ?
> How can I be alert by SQL if the maintenance plan is not able to delete
> the
> .BAK files older than 1 day ?
> Thanks|||Hi,
If you have a mapi e-mail you can have a notification when the job fails.
Probably your status is that the job failed. You can install outlook 2000 or
outlook 2003 and create a new account for sending mails as f.e Database Admi
n.
Additionally, you can go to the maintenance plan properties and in the
Reporting tab you can tick the check box Write report a text file in
directory or any other option.
Hope that helped
Andreas
"Psa555" wrote:

> Hi,
> In my full backup maintenance Plan, I configured 1 day in a box 'Remove
> files older than : "
> The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folde
r
> older than 1 day.
> Why the maintenance Plan does'nt remove those files ?
> What can cause this ?
> How can I be alert by SQL if the maintenance plan is not able to delete th
e
> .BAK files older than 1 day ?
> Thanks|||Because 1 day = 24 hours, exactly. If you job is off schedule or takes a
little longer to run than the prior day, even if by 1 minute, the time
stamps are only 23 hours, 59 minutes, etc., which is NOT 1 day.
I usually code mine to delete anything older than 3 hours. When it runs, it
will run the backup or reorg operation first, then it will check for files
to delete.
Sincerely,
Anthony Thomas
"Psa555" <Psa555@.discussions.microsoft.com> wrote in message
news:34A86E28-127A-4A50-B857-EF729A401790@.microsoft.com...
Hi,
In my full backup maintenance Plan, I configured 1 day in a box 'Remove
files older than : "
The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
older than 1 day.
Why the maintenance Plan does'nt remove those files ?
What can cause this ?
How can I be alert by SQL if the maintenance plan is not able to delete the
.BAK files older than 1 day ?
Thanks

Backup retention problem

Hi,
In my full backup maintenance Plan, I configured 1 day in a box 'Remove
files older than : "
The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
older than 1 day.
Why the maintenance Plan does'nt remove those files ?
What can cause this ?
How can I be alert by SQL if the maintenance plan is not able to delete the
.BAK files older than 1 day ?
Thankshttp://support.microsoft.com/default.aspx?scid=kb;en-us;303292
-- Log files don't delete --
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q303292
This is likely to be either a permissions problem or a sharing violation
problem. The maintenance plan is run as a job, and jobs are run by the
SQLServerAgent service.
Permissions:
1. Determine the startup account for the SQLServerAgent service
(Start|Programs|Administrative tools|Services|SQLServerAgent|Startup). This
account is the security context for jobs, and thus the maintenance plan.
2. If SQLServerAgent is started using LocalSystem (as opposed to a domain
account) then skip step 3.
3. On that box, log onto NT as that account. Using Explorer, attempt to
delete an expired backup. If that succeeds then go to Sharing Violation
section.
4. Log onto NT with an account that is an administrator and use Explorer to
look at the Properties|Security of the folder (where the backups reside)
and ensure the SQLServerAgent startup account has Full Control. If the
SQLServerAgent startup account is LocalSystem, then the account to consider
is SYSTEM.
5. In NT, if an account is a member of an NT group, and if that group has
Access is Denied, then that account will have Access is Denied, even if
that account is also a member of the Administrators group. Thus you may
need to check group permissions (if the Startup Account is a member of a
group).
6. Keep in mind that permissions (by default) are inherited from a parent
folder. Thus, if the backups are stored in C:\bak, and if someone had
denied permission to the SQLServerAgent startup account for C:\, then
C:\bak will inherit access is denied.
Sharing violation:
This is likely to be rooted in a timing issue, with the most likely cause
being another scheduled process (such as NT Backup or Anti-Virus software)
having the backup file open at the time when the SQLServerAgent (i.e., the
maintenance plan job) tried to delete it.
1. Download filemon and handle from www.sysinternals.com.
2. I am not sure whether filemon can be scheduled, or you might be able to
use NT scheduling services to start filemon just before the maintenance
plan job is started, but the filemon log can become very large, so it would
be best to start it some short time before the maintenance plan starts.
3. Inspect the filemon log for another process that has that backup file
open (if your lucky enough to have started filemon before this other
process grabs the backup folder), and inspect the log for the results when
the SQLServerAgent agent attempts to open that same file.
4. Schedule the job or that other process to do their work at different
times.
5. You can use the handle utility if you are around at the time when the
job is scheduled to run.
If the backup files are going to a \\share or a mapped drive (as opposed to
local drive), then you will need to modify the above (with respect to where
the tests and utilities are run).
Finally, inspection of the maintenance plan's history report might be
useful.
Thanks,
Bill Hollinshead
Microsoft, SQL Server
--
Andrew J. Kelly SQL MVP
"Psa555" <Psa555@.discussions.microsoft.com> wrote in message
news:34A86E28-127A-4A50-B857-EF729A401790@.microsoft.com...
> Hi,
> In my full backup maintenance Plan, I configured 1 day in a box 'Remove
> files older than : "
> The problem is ... sometimes I have 3 or 4 files .BAK in my backup's
> folder
> older than 1 day.
> Why the maintenance Plan does'nt remove those files ?
> What can cause this ?
> How can I be alert by SQL if the maintenance plan is not able to delete
> the
> .BAK files older than 1 day ?
> Thanks|||Hi,
If you have a mapi e-mail you can have a notification when the job fails.
Probably your status is that the job failed. You can install outlook 2000 or
outlook 2003 and create a new account for sending mails as f.e Database Admin.
Additionally, you can go to the maintenance plan properties and in the
Reporting tab you can tick the check box Write report a text file in
directory or any other option.
Hope that helped
Andreas
"Psa555" wrote:
> Hi,
> In my full backup maintenance Plan, I configured 1 day in a box 'Remove
> files older than : "
> The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
> older than 1 day.
> Why the maintenance Plan does'nt remove those files ?
> What can cause this ?
> How can I be alert by SQL if the maintenance plan is not able to delete the
> .BAK files older than 1 day ?
> Thanks|||Because 1 day = 24 hours, exactly. If you job is off schedule or takes a
little longer to run than the prior day, even if by 1 minute, the time
stamps are only 23 hours, 59 minutes, etc., which is NOT 1 day.
I usually code mine to delete anything older than 3 hours. When it runs, it
will run the backup or reorg operation first, then it will check for files
to delete.
Sincerely,
Anthony Thomas
"Psa555" <Psa555@.discussions.microsoft.com> wrote in message
news:34A86E28-127A-4A50-B857-EF729A401790@.microsoft.com...
Hi,
In my full backup maintenance Plan, I configured 1 day in a box 'Remove
files older than : "
The problem is ... sometimes I have 3 or 4 files .BAK in my backup's folder
older than 1 day.
Why the maintenance Plan does'nt remove those files ?
What can cause this ?
How can I be alert by SQL if the maintenance plan is not able to delete the
.BAK files older than 1 day ?
Thanks

Backup question

Not sure if this is the correct group......
The tape drive on our SQL Server 2000 box died and I have just had it
replaced. The new tape drive is a Dell Powervault 110T DLT VS 80. The
problem I am having is that after every single backup job...or every step in
a backup job if it has multiple steps...the tape ejects on its own. I have
made no changes to the backup jobs, just changed the physical tape drive.
Any ideas where to start looking for the cause?
Thanks
Eric StewartCheck out the section in BooksOnLine for Backup and the Options UNLOAD and
NOUNLOAD. I suspect the old tape drive just didn't support this
functionality and you might now need to set NOUNLOAD.
--
Andrew J. Kelly
SQL Server MVP
"Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
news:OZrLr246DHA.2264@.tk2msftngp13.phx.gbl...
> Not sure if this is the correct group......
> The tape drive on our SQL Server 2000 box died and I have just had it
> replaced. The new tape drive is a Dell Powervault 110T DLT VS 80. The
> problem I am having is that after every single backup job...or every step
in
> a backup job if it has multiple steps...the tape ejects on its own. I have
> made no changes to the backup jobs, just changed the physical tape drive.
> Any ideas where to start looking for the cause?
> Thanks
> Eric Stewart
>|||Thanks Andrew. I will check this out first thing in the morning!
Eric
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OEAd2956DHA.2996@.tk2msftngp13.phx.gbl...
> Check out the section in BooksOnLine for Backup and the Options UNLOAD and
> NOUNLOAD. I suspect the old tape drive just didn't support this
> functionality and you might now need to set NOUNLOAD.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
> news:OZrLr246DHA.2264@.tk2msftngp13.phx.gbl...
> > Not sure if this is the correct group......
> >
> > The tape drive on our SQL Server 2000 box died and I have just had it
> > replaced. The new tape drive is a Dell Powervault 110T DLT VS 80. The
> > problem I am having is that after every single backup job...or every
step
> in
> > a backup job if it has multiple steps...the tape ejects on its own. I
have
> > made no changes to the backup jobs, just changed the physical tape
drive.
> > Any ideas where to start looking for the cause?
> >
> > Thanks
> >
> > Eric Stewart
> >
> >
>|||That was it!!!
Thanks again Andrew for the very helpful advice.
Eric
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OEAd2956DHA.2996@.tk2msftngp13.phx.gbl...
> Check out the section in BooksOnLine for Backup and the Options UNLOAD and
> NOUNLOAD. I suspect the old tape drive just didn't support this
> functionality and you might now need to set NOUNLOAD.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
> news:OZrLr246DHA.2264@.tk2msftngp13.phx.gbl...
> > Not sure if this is the correct group......
> >
> > The tape drive on our SQL Server 2000 box died and I have just had it
> > replaced. The new tape drive is a Dell Powervault 110T DLT VS 80. The
> > problem I am having is that after every single backup job...or every
step
> in
> > a backup job if it has multiple steps...the tape ejects on its own. I
have
> > made no changes to the backup jobs, just changed the physical tape
drive.
> > Any ideas where to start looking for the cause?
> >
> > Thanks
> >
> > Eric Stewart
> >
> >
>sql

Backup question

Not sure if this is the correct group......
The tape drive on our SQL Server 2000 box died and I have just had it
replaced. The new tape drive is a Dell Powervault 110T DLT VS 80. The
problem I am having is that after every single backup job...or every step in
a backup job if it has multiple steps...the tape ejects on its own. I have
made no changes to the backup jobs, just changed the physical tape drive.
Any ideas where to start looking for the cause?
Thanks
Eric StewartCheck out the section in BooksOnLine for Backup and the Options UNLOAD and
NOUNLOAD. I suspect the old tape drive just didn't support this
functionality and you might now need to set NOUNLOAD.
Andrew J. Kelly
SQL Server MVP
"Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
news:OZrLr246DHA.2264@.tk2msftngp13.phx.gbl...

quote:

---

> Not sure if this is the correct group......
> The tape drive on our SQL Server 2000 box died and I have just had it
> replaced. The new tape drive is a Dell Powervault 110T DLT VS 80. The
> problem I am having is that after every single backup job...or every step

---

in

quote:

---

> a backup job if it has multiple steps...the tape ejects on its own. I have
> made no changes to the backup jobs, just changed the physical tape drive.
> Any ideas where to start looking for the cause?
> Thanks
> Eric Stewart
>

---

|||Thanks Andrew. I will check this out first thing in the morning!
Eric
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OEAd2956DHA.2996@.tk2msftngp13.phx.gbl...

quote:

---

> Check out the section in BooksOnLine for Backup and the Options UNLOAD and
> NOUNLOAD. I suspect the old tape drive just didn't support this
> functionality and you might now need to set NOUNLOAD.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
> news:OZrLr246DHA.2264@.tk2msftngp13.phx.gbl...
step[QUOTE]
> in
have[QUOTE]
drive.[QUOTE]
>

---

|||That was it!!!
Thanks again Andrew for the very helpful advice.
Eric
"Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote in message
news:OEAd2956DHA.2996@.tk2msftngp13.phx.gbl...

quote:

---

> Check out the section in BooksOnLine for Backup and the Options UNLOAD and
> NOUNLOAD. I suspect the old tape drive just didn't support this
> functionality and you might now need to set NOUNLOAD.
> --
> Andrew J. Kelly
> SQL Server MVP
>
> "Eric Stewart" <stewarte@.repsilverstate.com> wrote in message
> news:OZrLr246DHA.2264@.tk2msftngp13.phx.gbl...
step[QUOTE]
> in
have[QUOTE]
drive.[QUOTE]
>

---

backup log terminated abormally

I backup the transaction log unsuccessfully.
It pops up :
Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
DetailMessgae : Write
on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
=112.
Has anyone experienced this before or knows what is
going wrong ?You can type 'NET HELPMSG 112' from a command prompt window to get the
following Windows error message text:
There is not enough space on the disk.
Try the backup again after freeing some disk space.
Hope this helps.
Dan Guzman
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:618b01c481ad$b566e040$a401280a@.phx.gbl...
> I backup the transaction log unsuccessfully.
> It pops up :
> Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
> DetailMessgae : Write
> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
> =112.
> Has anyone experienced this before or knows what is
> going wrong ?
>|||Thanks Dan for the answers...

>--Original Message--
>You can type 'NET HELPMSG 112' from a command prompt
window to get the
>following Windows error message text:
> There is not enough space on the disk.
>Try the backup again after freeing some disk space.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Newbie" <anonymous@.discussions.microsoft.com> wrote in
message
>news:618b01c481ad$b566e040$a401280a@.phx.gbl...
42000)[vbcol=seagreen]
status[vbcol=seagreen]
>
>.
>

backup log terminated abormally

I backup the transaction log unsuccessfully.
It pops up :
Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
DetailMessgae : Write
on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
=112.
Has anyone experienced this before or knows what is
going wrong ?
You can type 'NET HELPMSG 112' from a command prompt window to get the
following Windows error message text:
There is not enough space on the disk.
Try the backup again after freeing some disk space.
Hope this helps.
Dan Guzman
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:618b01c481ad$b566e040$a401280a@.phx.gbl...
> I backup the transaction log unsuccessfully.
> It pops up :
> Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
> DetailMessgae : Write
> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
> =112.
> Has anyone experienced this before or knows what is
> going wrong ?
>
|||Thanks Dan for the answers...

>--Original Message--
>You can type 'NET HELPMSG 112' from a command prompt
window to get the
>following Windows error message text:
> There is not enough space on the disk.
>Try the backup again after freeing some disk space.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Newbie" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:618b01c481ad$b566e040$a401280a@.phx.gbl...
42000)[vbcol=seagreen]
status
>
>.
>

backup log terminated abormally

I backup the transaction log unsuccessfully.
It pops up :
Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
DetailMessgae : Write
on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
=112.
Has anyone experienced this before or knows what is
going wrong ?You can type 'NET HELPMSG 112' from a command prompt window to get the
following Windows error message text:
There is not enough space on the disk.
Try the backup again after freeing some disk space.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Newbie" <anonymous@.discussions.microsoft.com> wrote in message
news:618b01c481ad$b566e040$a401280a@.phx.gbl...
> I backup the transaction log unsuccessfully.
> It pops up :
> Error Box Title : Microsoft SQL-DMO(ODBC SQLState 42000)
> DetailMessgae : Write
> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed, status
> =112.
> Has anyone experienced this before or knows what is
> going wrong ?
>|||Thanks Dan for the answers...
>--Original Message--
>You can type 'NET HELPMSG 112' from a command prompt
window to get the
>following Windows error message text:
> There is not enough space on the disk.
>Try the backup again after freeing some disk space.
>--
>Hope this helps.
>Dan Guzman
>SQL Server MVP
>"Newbie" <anonymous@.discussions.microsoft.com> wrote in
message
>news:618b01c481ad$b566e040$a401280a@.phx.gbl...
>> I backup the transaction log unsuccessfully.
>> It pops up :
>> Error Box Title : Microsoft SQL-DMO(ODBC SQLState
42000)
>> DetailMessgae : Write
>> on 'c:\MSSQL\Backup\mydata_db_2004043.BAK' failed,
status
>> =112.
>> Has anyone experienced this before or knows what is
>> going wrong ?
>>
>
>.
>