Showing posts with label recovery. Show all posts
Showing posts with label recovery. Show all posts

Wednesday, March 21, 2012

Failed services after backup

Last night we did a backup through backup exec using the
no recovery option. This was not part of a plan but it was
done anyway.
This morning when all the databases that had been backed
up with no recovery set were inaccessible (because they
were marked (Loading)) one of the things we did was to
stop to of our SQL server servers.
We now know all we had to do was do a restore database
with recovery but at the time we thought we would stop and
restart the service.
After stopping the service we can not restart it.
it gives a message indicating there was a failure with no
return code.
Does anyone have any ideas on how we can get these servers
started again?
ThanksThe first step is to check the errolog file and see specific messages there.
Then take it from there.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Bob Ryan" <anonymous@.discussions.microsoft.com> wrote in message
news:f32001c3f18c$d1138a20$a001280a@.phx.gbl...
> Last night we did a backup through backup exec using the
> no recovery option. This was not part of a plan but it was
> done anyway.
> This morning when all the databases that had been backed
> up with no recovery set were inaccessible (because they
> were marked (Loading)) one of the things we did was to
> stop to of our SQL server servers.
> We now know all we had to do was do a restore database
> with recovery but at the time we thought we would stop and
> restart the service.
> After stopping the service we can not restart it.
> it gives a message indicating there was a failure with no
> return code.
> Does anyone have any ideas on how we can get these servers
> started again?
>
> Thanks

Failed services after backup

Last night we did a backup through backup exec using the
no recovery option. This was not part of a plan but it was
done anyway.
This morning when all the databases that had been backed
up with no recovery set were inaccessible (because they
were marked (Loading)) one of the things we did was to
stop to of our SQL server servers.
We now know all we had to do was do a restore database
with recovery but at the time we thought we would stop and
restart the service.
After stopping the service we can not restart it.
it gives a message indicating there was a failure with no
return code.
Does anyone have any ideas on how we can get these servers
started again?
ThanksThe first step is to check the errolog file and see specific messages there.
Then take it from there.
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=...ublic.sqlserver
"Bob Ryan" <anonymous@.discussions.microsoft.com> wrote in message
news:f32001c3f18c$d1138a20$a001280a@.phx.gbl...
> Last night we did a backup through backup exec using the
> no recovery option. This was not part of a plan but it was
> done anyway.
> This morning when all the databases that had been backed
> up with no recovery set were inaccessible (because they
> were marked (Loading)) one of the things we did was to
> stop to of our SQL server servers.
> We now know all we had to do was do a restore database
> with recovery but at the time we thought we would stop and
> restart the service.
> After stopping the service we can not restart it.
> it gives a message indicating there was a failure with no
> return code.
> Does anyone have any ideas on how we can get these servers
> started again?
>
> Thankssql

Monday, March 12, 2012

Failed during recovery

I have been having a lot of trouble trying to reattach a database. The
latest issue is that after 9% of recovery I get a primary key violation and
it stops.
Is there anything I can do to get around this'
Thanks
RichardWhat SQL Server version are you using?
If you are using 2000, have you installed service pack 4?
thanks,
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||You most likely dettached the database without using the checkpoint command
to commit the data on memory to disk. This caused your identities to become
of synch to fix run dbcc checkident( sysrestorehistory ) in the msdb
database.
do you still have the old database?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||Richard
Do you have last FULL BACKUP of the database? If you do , perform just
RESTORE command
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>

Failed during recovery

I have been having a lot of trouble trying to reattach a database. The
latest issue is that after 9% of recovery I get a primary key violation and
it stops.
Is there anything I can do to get around this?
Thanks
Richard
What SQL Server version are you using?
If you are using 2000, have you installed service pack 4?
thanks,
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this?
> Thanks
> Richard
>
|||You most likely dettached the database without using the checkpoint command
to commit the data on memory to disk. This caused your identities to become
of synch to fix run dbcc checkident( sysrestorehistory ) in the msdb
database.
do you still have the old database?
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this?
> Thanks
> Richard
>
|||Richard
Do you have last FULL BACKUP of the database? If you do , perform just
RESTORE command
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this?
> Thanks
> Richard
>

Failed during recovery

I have been having a lot of trouble trying to reattach a database. The
latest issue is that after 9% of recovery I get a primary key violation and
it stops.
Is there anything I can do to get around this'
Thanks
RichardWhat SQL Server version are you using?
If you are using 2000, have you installed service pack 4?
thanks,
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||You most likely dettached the database without using the checkpoint command
to commit the data on memory to disk. This caused your identities to become
of synch to fix run dbcc checkident( sysrestorehistory ) in the msdb
database.
do you still have the old database?
--
/*
Warren Brunk - MCITP - SQL 2005, MCDBA
www.techintsolutions.com
*/
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>|||Richard
Do you have last FULL BACKUP of the database? If you do , perform just
RESTORE command
"Richard Douglass" <RDouglass@.arisinc.com> wrote in message
news:uXV9FzS3GHA.4764@.TK2MSFTNGP02.phx.gbl...
>I have been having a lot of trouble trying to reattach a database. The
>latest issue is that after 9% of recovery I get a primary key violation and
>it stops.
> Is there anything I can do to get around this'
> Thanks
> Richard
>