Tuesday, March 27, 2012

Backing up SQL 2000

Hello!'
New to the admin aspect of SQL 2000, wondering if there
are any advantages/disadvantaged of backing the databases
using the NT backup utility found in Windows 2000 server.
Is there anything that should be excluded similar to,like,
the M drive on Exchange 2000?
Thanks !
CarlosThe NT backup will only copy files. You don't want a file level backup of
sql server you want file generated from a SQL Server Backup. The file level
backup will most likely be useless if you can even get it to copy while it
is running. Take a look at the BACKUP command in BooksOnLine. It will
generate a file(s) that you can use the NT backup process to copy and not
the original sql server files.
--
Andrew J. Kelly
SQL Server MVP
"Carlos" <anonymous@.discussions.microsoft.com> wrote in message
news:742101c3e765$bef02c30$a001280a@.phx.gbl...
> Hello!'
> New to the admin aspect of SQL 2000, wondering if there
> are any advantages/disadvantaged of backing the databases
> using the NT backup utility found in Windows 2000 server.
> Is there anything that should be excluded similar to,like,
> the M drive on Exchange 2000?
> Thanks !
> Carlos|||Abdrew,
Do you mean running the backup-to-file within the SQL 2000
and then backing up those files to tape, etc?
I have done that, however, when doing that within sql
2000, an event id 208 appears. I have changed the master
db to simple recovery model and set the msdb to full
recovery model. This should have resolved issue, but it
didn't.
Thanks for your help!
Carlos
>--Original Message--
>The NT backup will only copy files. You don't want a
file level backup of
>sql server you want file generated from a SQL Server
Backup. The file level
>backup will most likely be useless if you can even get it
to copy while it
>is running. Take a look at the BACKUP command in
BooksOnLine. It will
>generate a file(s) that you can use the NT backup process
to copy and not
>the original sql server files.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Carlos" <anonymous@.discussions.microsoft.com> wrote in
message
>news:742101c3e765$bef02c30$a001280a@.phx.gbl...
>> Hello!'
>> New to the admin aspect of SQL 2000, wondering if there
>> are any advantages/disadvantaged of backing the
databases
>> using the NT backup utility found in Windows 2000
server.
>> Is there anything that should be excluded similar
to,like,
>> the M drive on Exchange 2000?
>> Thanks !
>> Carlos
>
>.
>|||The MSDB should be set to simple recovery as well. If you mean you get a
SQL error number 208 then you most likely typed something in wrong or
possibly have spaces in the db name. If so use [] around the names. If you
could post the exact command and error it would help.
--
Andrew J. Kelly
SQL Server MVP
"Carlos" <anonymous@.discussions.microsoft.com> wrote in message
news:70a601c3e76d$71023f10$a101280a@.phx.gbl...
> Abdrew,
> Do you mean running the backup-to-file within the SQL 2000
> and then backing up those files to tape, etc?
> I have done that, however, when doing that within sql
> 2000, an event id 208 appears. I have changed the master
> db to simple recovery model and set the msdb to full
> recovery model. This should have resolved issue, but it
> didn't.
> Thanks for your help!
> Carlos
>
> >--Original Message--
> >The NT backup will only copy files. You don't want a
> file level backup of
> >sql server you want file generated from a SQL Server
> Backup. The file level
> >backup will most likely be useless if you can even get it
> to copy while it
> >is running. Take a look at the BACKUP command in
> BooksOnLine. It will
> >generate a file(s) that you can use the NT backup process
> to copy and not
> >the original sql server files.
> >
> >--
> >
> >Andrew J. Kelly
> >SQL Server MVP
> >
> >
> >"Carlos" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:742101c3e765$bef02c30$a001280a@.phx.gbl...
> >> Hello!'
> >>
> >> New to the admin aspect of SQL 2000, wondering if there
> >> are any advantages/disadvantaged of backing the
> databases
> >> using the NT backup utility found in Windows 2000
> server.
> >>
> >> Is there anything that should be excluded similar
> to,like,
> >> the M drive on Exchange 2000?
> >>
> >> Thanks !
> >>
> >> Carlos
> >
> >
> >.
> >|||Hello!
The exact event id 208 is:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance
Plan "Nightly Maintenance Plan"(hexnumber)- Status:
Failed -invoked on date - Message: The job failed. The Job
was invoked by Schedule 4 (Schedule 1). The last step was
step 1 (Step 1)
msdb was actually set back to simple
Thanks for your advise!
>--Original Message--
>The MSDB should be set to simple recovery as well. If
you mean you get a
>SQL error number 208 then you most likely typed something
in wrong or
>possibly have spaces in the db name. If so use [] around
the names. If you
>could post the exact command and error it would help.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Carlos" <anonymous@.discussions.microsoft.com> wrote in
message
>news:70a601c3e76d$71023f10$a101280a@.phx.gbl...
>> Abdrew,
>> Do you mean running the backup-to-file within the SQL
2000
>> and then backing up those files to tape, etc?
>> I have done that, however, when doing that within sql
>> 2000, an event id 208 appears. I have changed the
master
>> db to simple recovery model and set the msdb to full
>> recovery model. This should have resolved issue, but it
>> didn't.
>> Thanks for your help!
>> Carlos
>>
>> >--Original Message--
>> >The NT backup will only copy files. You don't want a
>> file level backup of
>> >sql server you want file generated from a SQL Server
>> Backup. The file level
>> >backup will most likely be useless if you can even get
it
>> to copy while it
>> >is running. Take a look at the BACKUP command in
>> BooksOnLine. It will
>> >generate a file(s) that you can use the NT backup
process
>> to copy and not
>> >the original sql server files.
>> >
>> >--
>> >
>> >Andrew J. Kelly
>> >SQL Server MVP
>> >
>> >
>> >"Carlos" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:742101c3e765$bef02c30$a001280a@.phx.gbl...
>> >> Hello!'
>> >>
>> >> New to the admin aspect of SQL 2000, wondering if
there
>> >> are any advantages/disadvantaged of backing the
>> databases
>> >> using the NT backup utility found in Windows 2000
>> server.
>> >>
>> >> Is there anything that should be excluded similar
>> to,like,
>> >> the M drive on Exchange 2000?
>> >>
>> >> Thanks !
>> >>
>> >> Carlos
>> >
>> >
>> >.
>> >
>
>.
>|||By the way, no spaces in the DB name.
>--Original Message--
>The MSDB should be set to simple recovery as well. If
you mean you get a
>SQL error number 208 then you most likely typed something
in wrong or
>possibly have spaces in the db name. If so use [] around
the names. If you
>could post the exact command and error it would help.
>--
>Andrew J. Kelly
>SQL Server MVP
>
>"Carlos" <anonymous@.discussions.microsoft.com> wrote in
message
>news:70a601c3e76d$71023f10$a101280a@.phx.gbl...
>> Abdrew,
>> Do you mean running the backup-to-file within the SQL
2000
>> and then backing up those files to tape, etc?
>> I have done that, however, when doing that within sql
>> 2000, an event id 208 appears. I have changed the
master
>> db to simple recovery model and set the msdb to full
>> recovery model. This should have resolved issue, but it
>> didn't.
>> Thanks for your help!
>> Carlos
>>
>> >--Original Message--
>> >The NT backup will only copy files. You don't want a
>> file level backup of
>> >sql server you want file generated from a SQL Server
>> Backup. The file level
>> >backup will most likely be useless if you can even get
it
>> to copy while it
>> >is running. Take a look at the BACKUP command in
>> BooksOnLine. It will
>> >generate a file(s) that you can use the NT backup
process
>> to copy and not
>> >the original sql server files.
>> >
>> >--
>> >
>> >Andrew J. Kelly
>> >SQL Server MVP
>> >
>> >
>> >"Carlos" <anonymous@.discussions.microsoft.com> wrote in
>> message
>> >news:742101c3e765$bef02c30$a001280a@.phx.gbl...
>> >> Hello!'
>> >>
>> >> New to the admin aspect of SQL 2000, wondering if
there
>> >> are any advantages/disadvantaged of backing the
>> databases
>> >> using the NT backup utility found in Windows 2000
>> server.
>> >>
>> >> Is there anything that should be excluded similar
>> to,like,
>> >> the M drive on Exchange 2000?
>> >>
>> >> Thanks !
>> >>
>> >> Carlos
>> >
>> >
>> >.
>> >
>
>.
>|||This is one of the main reasons why I dislike the MP so much. It can be
very hard to tell what is going on and what the problems are. If you can't
easily find the issue I recommend just creating your own scheduled job that
issues the backups so you can have more control over what is going on.
Andrew J. Kelly
SQL Server MVP
"Carlos" <anonymous@.discussions.microsoft.com> wrote in message
news:886f01c3e9a5$e01c90f0$a001280a@.phx.gbl...
> Hello!
> The exact event id 208 is:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance
> Plan "Nightly Maintenance Plan"(hexnumber)- Status:
> Failed -invoked on date - Message: The job failed. The Job
> was invoked by Schedule 4 (Schedule 1). The last step was
> step 1 (Step 1)
> msdb was actually set back to simple
> Thanks for your advise!
> >--Original Message--
> >The MSDB should be set to simple recovery as well. If
> you mean you get a
> >SQL error number 208 then you most likely typed something
> in wrong or
> >possibly have spaces in the db name. If so use [] around
> the names. If you
> >could post the exact command and error it would help.
> >
> >--
> >
> >Andrew J. Kelly
> >SQL Server MVP
> >
> >
> >"Carlos" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:70a601c3e76d$71023f10$a101280a@.phx.gbl...
> >> Abdrew,
> >>
> >> Do you mean running the backup-to-file within the SQL
> 2000
> >> and then backing up those files to tape, etc?
> >>
> >> I have done that, however, when doing that within sql
> >> 2000, an event id 208 appears. I have changed the
> master
> >> db to simple recovery model and set the msdb to full
> >> recovery model. This should have resolved issue, but it
> >> didn't.
> >>
> >> Thanks for your help!
> >>
> >> Carlos
> >>
> >>
> >> >--Original Message--
> >> >The NT backup will only copy files. You don't want a
> >> file level backup of
> >> >sql server you want file generated from a SQL Server
> >> Backup. The file level
> >> >backup will most likely be useless if you can even get
> it
> >> to copy while it
> >> >is running. Take a look at the BACKUP command in
> >> BooksOnLine. It will
> >> >generate a file(s) that you can use the NT backup
> process
> >> to copy and not
> >> >the original sql server files.
> >> >
> >> >--
> >> >
> >> >Andrew J. Kelly
> >> >SQL Server MVP
> >> >
> >> >
> >> >"Carlos" <anonymous@.discussions.microsoft.com> wrote in
> >> message
> >> >news:742101c3e765$bef02c30$a001280a@.phx.gbl...
> >> >> Hello!'
> >> >>
> >> >> New to the admin aspect of SQL 2000, wondering if
> there
> >> >> are any advantages/disadvantaged of backing the
> >> databases
> >> >> using the NT backup utility found in Windows 2000
> >> server.
> >> >>
> >> >> Is there anything that should be excluded similar
> >> to,like,
> >> >> the M drive on Exchange 2000?
> >> >>
> >> >> Thanks !
> >> >>
> >> >> Carlos
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >

No comments:

Post a Comment