Backup not working in 2005

I am trying to backup a database that was moved from 2000 to 2005 and I get
the following error message:
The backup of full-text catalog ‘Attachment’ is not permitted because it is
not online. Check errorlog file for the reason that full-text catalog becomes
offline and bring it online. Or BACKUP can be performed by using the
FILEGROUP or FILE clauses to restrict the selection to include only online
data.
Why am I getting this message and how do I fix it?
Thanks,
Emma
My guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>
|||Please disregard this post. I enabled full-text indexing in the backup worked
fine.
Thanks
"Emma" wrote:

> I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>
|||Thanks for the response. I will try that as well. For now, enabling the Use
full-text indexing took care of the error message as well.
Thanks.
"Tibor Karaszi" wrote:

> My guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
> 2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
> don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
> the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Emma" <Emma@.discussions.microsoft.com> wrote in message
> news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>

Backup not working in 2005

I am trying to backup a database that was moved from 2000 to 2005 and I get
the following error message:
The backup of full-text catalog ‘Attachment’ is not permitted because it
is
not online. Check errorlog file for the reason that full-text catalog become
s
offline and bring it online. Or BACKUP can be performed by using the
FILEGROUP or FILE clauses to restrict the selection to include only online
data.
Why am I getting this message and how do I fix it?
Thanks,
EmmaMy guess is that the 2000 database had full.text catalogs which for some rea
son isn't there anymore.
2005 treats a full text catalog as a filegroup when it comes to backup and r
estore. Perhaps you
don't want this full-text meta-data hanging around? If so, I'd remove it so
it won't interfere with
the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because
it is
> not online. Check errorlog file for the reason that full-text catalog beco
mes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Please disregard this post. I enabled full-text indexing in the backup worke
d
fine.
Thanks
"Emma" wrote:

> I am trying to backup a database that was moved from 2000 to 2005 and I ge
t
> the following error message:
> The backup of full-text catalog ‘Attachment’ is not permitted because
it is
> not online. Check errorlog file for the reason that full-text catalog beco
mes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Thanks for the response. I will try that as well. For now, enabling the Use
full-text indexing took care of the error message as well.
Thanks.
"Tibor Karaszi" wrote:

> My guess is that the 2000 database had full.text catalogs which for some r
eason isn't there anymore.
> 2005 treats a full text catalog as a filegroup when it comes to backup and
restore. Perhaps you
> don't want this full-text meta-data hanging around? If so, I'd remove it s
o it won't interfere with
> the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Emma" <Emma@.discussions.microsoft.com> wrote in message
> news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>

Backup not working in 2005

I am trying to backup a database that was moved from 2000 to 2005 and I get
the following error message:
The backup of full-text catalog â'Attachmentâ' is not permitted because it is
not online. Check errorlog file for the reason that full-text catalog becomes
offline and bring it online. Or BACKUP can be performed by using the
FILEGROUP or FILE clauses to restrict the selection to include only online
data.
Why am I getting this message and how do I fix it?
Thanks,
EmmaMy guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
>I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog â'Attachmentâ' is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Please disregard this post. I enabled full-text indexing in the backup worked
fine.
Thanks
"Emma" wrote:
> I am trying to backup a database that was moved from 2000 to 2005 and I get
> the following error message:
> The backup of full-text catalog â'Attachmentâ' is not permitted because it is
> not online. Check errorlog file for the reason that full-text catalog becomes
> offline and bring it online. Or BACKUP can be performed by using the
> FILEGROUP or FILE clauses to restrict the selection to include only online
> data.
> Why am I getting this message and how do I fix it?
> Thanks,
> Emma
>|||Thanks for the response. I will try that as well. For now, enabling the Use
full-text indexing took care of the error message as well.
Thanks.
"Tibor Karaszi" wrote:
> My guess is that the 2000 database had full.text catalogs which for some reason isn't there anymore.
> 2005 treats a full text catalog as a filegroup when it comes to backup and restore. Perhaps you
> don't want this full-text meta-data hanging around? If so, I'd remove it so it won't interfere with
> the backups. DROP FULLTEXT CATALOG seems to be what you'd want to use.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://sqlblog.com/blogs/tibor_karaszi
>
> "Emma" <Emma@.discussions.microsoft.com> wrote in message
> news:71D47831-F702-4750-9A11-F0C5DE27BA49@.microsoft.com...
> >I am trying to backup a database that was moved from 2000 to 2005 and I get
> > the following error message:
> >
> > The backup of full-text catalog â'Attachmentâ' is not permitted because it is
> > not online. Check errorlog file for the reason that full-text catalog becomes
> > offline and bring it online. Or BACKUP can be performed by using the
> > FILEGROUP or FILE clauses to restrict the selection to include only online
> > data.
> >
> > Why am I getting this message and how do I fix it?
> >
> > Thanks,
> > Emma
> >
>

backup LSN help

I've been working on some code to be able to reverse catalog a set of
backups into the msdb backup* tables, which was easy, but now I'm struggling
with the necessary code to create the restore commands for an arbitrary
point in time.
My question is what is the appropriate logic or psuedo code for walking a
tree backup resources to get to a point in time.
I believe the following to be appropriate logic, but would like
verification:
full backup id = (max (checkpointlsn) where finishtime<[point in time]) and
type = 1
differential backup id = (max(checkpointlsn) where backuplsn = full backup
checkpointlsn and type = 5 and finishtime<[point in time])
But I am still struggling with the T-log resources and how to put it all
together (like for example, if you simply cannot get to a given point in
time given a set of files, and only wanting to restore the necessary the
last t-log where the lsn hasn't changed in 10 backup files)
Help!?
Bump
<news@.news.com> wrote in message
news:%23l52asjXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> I've been working on some code to be able to reverse catalog a set of
> backups into the msdb backup* tables, which was easy, but now I'm
struggling
> with the necessary code to create the restore commands for an arbitrary
> point in time.
> My question is what is the appropriate logic or psuedo code for walking a
> tree backup resources to get to a point in time.
> I believe the following to be appropriate logic, but would like
> verification:
> full backup id = (max (checkpointlsn) where finishtime<[point in time])
and
> type = 1
> differential backup id = (max(checkpointlsn) where backuplsn = full backup
> checkpointlsn and type = 5 and finishtime<[point in time])
> But I am still struggling with the T-log resources and how to put it all
> together (like for example, if you simply cannot get to a given point in
> time given a set of files, and only wanting to restore the necessary the
> last t-log where the lsn hasn't changed in 10 backup files)
> Help!?
>
>
>
>
>

backup LSN help

I've been working on some code to be able to reverse catalog a set of
backups into the msdb backup* tables, which was easy, but now I'm struggling
with the necessary code to create the restore commands for an arbitrary
point in time.
My question is what is the appropriate logic or psuedo code for walking a
tree backup resources to get to a point in time.
I believe the following to be appropriate logic, but would like
verification:
full backup id = (max (checkpointlsn) where finishtime<[point in time]) and
type = 1
differential backup id = (max(checkpointlsn) where backuplsn = full backup
checkpointlsn and type = 5 and finishtime<[point in time])
But I am still struggling with the T-log resources and how to put it all
together (like for example, if you simply cannot get to a given point in
time given a set of files, and only wanting to restore the necessary the
last t-log where the lsn hasn't changed in 10 backup files)
Help!?Bump
<news@.news.com> wrote in message
news:%23l52asjXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> I've been working on some code to be able to reverse catalog a set of
> backups into the msdb backup* tables, which was easy, but now I'm
struggling
> with the necessary code to create the restore commands for an arbitrary
> point in time.
> My question is what is the appropriate logic or psuedo code for walking a
> tree backup resources to get to a point in time.
> I believe the following to be appropriate logic, but would like
> verification:
> full backup id = (max (checkpointlsn) where finishtime<[point in time])
and
> type = 1
> differential backup id = (max(checkpointlsn) where backuplsn = full backup
> checkpointlsn and type = 5 and finishtime<[point in time])
> But I am still struggling with the T-log resources and how to put it all
> together (like for example, if you simply cannot get to a given point in
> time given a set of files, and only wanting to restore the necessary the
> last t-log where the lsn hasn't changed in 10 backup files)
> Help!?
>
>
>
>
>

backup LSN help

I've been working on some code to be able to reverse catalog a set of
backups into the msdb backup* tables, which was easy, but now I'm struggling
with the necessary code to create the restore commands for an arbitrary
point in time.
My question is what is the appropriate logic or psuedo code for walking a
tree backup resources to get to a point in time.
I believe the following to be appropriate logic, but would like
verification:
full backup id = (max (checkpointlsn) where finishtime<[point in time])
and
type = 1
differential backup id = (max(checkpointlsn) where backuplsn = full backup
checkpointlsn and type = 5 and finishtime<[point in time])
But I am still struggling with the T-log resources and how to put it all
together (like for example, if you simply cannot get to a given point in
time given a set of files, and only wanting to restore the necessary the
last t-log where the lsn hasn't changed in 10 backup files)
Help!?Bump
<news@.news.com> wrote in message
news:%23l52asjXEHA.1656@.TK2MSFTNGP09.phx.gbl...
> I've been working on some code to be able to reverse catalog a set of
> backups into the msdb backup* tables, which was easy, but now I'm
struggling
> with the necessary code to create the restore commands for an arbitrary
> point in time.
> My question is what is the appropriate logic or psuedo code for walking a
> tree backup resources to get to a point in time.
> I believe the following to be appropriate logic, but would like
> verification:
> full backup id = (max (checkpointlsn) where finishtime<[point in time])[/vbcol
]
and[vbcol=seagreen]
> type = 1
> differential backup id = (max(checkpointlsn) where backuplsn = full backup
> checkpointlsn and type = 5 and finishtime<[point in time])
> But I am still struggling with the T-log resources and how to put it all
> together (like for example, if you simply cannot get to a given point in
> time given a set of files, and only wanting to restore the necessary the
> last t-log where the lsn hasn't changed in 10 backup files)
> Help!?
>
>
>
>
>