SQL 2000 loading SQLbill to the rescue? 1

[iklaas]

Hi,
We have an MSSQL 2000 database (60MB) backup that will not restore with recovery. (as seen everywhere on the net)
Without recover is keeps loading. When we command it to load database ourdatabase with recovery, it will not work.
We are looking everywhere but unable to find a working solution. SQLbill stated in an earlier discussion that he had problems and finaly got Veritas to solve it. Is there anyone who knows something today?
You can guess I have a major problem if ALL client data is gone.
Thanks for any help!

 

[jjeffm]

Hi Iklaas:
did you change something on your server? Partition size or drive letter? i have more questions then answers right now.
What happen to the original DB?

 

[iklaas]

Hi jjeffm,

Thanks for posting back. We solved the problem!
We had a hd crash (completely scraped off) and we had to install SQL again and tried to restore. It is a know issue, has nothing to do with BE (except for that it can not restore completely in itself).

The workaround is to restore the database, create a new one and import in the new one. Then it will create the log file and it works.

Thanks.

 

[justin2000]

iklass

did you happen to restore the master database first, since you had re-installed SQL?

 

[iklaas]

The master was build by the reinstall, we did nothing with it, perhaps restore from tapen with BE did? We are not sure right now. What we do know: No more BE. Why? It should be able to do the trick on its own. This silly thing has cost us 4 days, we are setback 2 full working days in data when we should have now loss at all since all failed at night and no transactions were taking place.

Ivar

 

[SQLBill]

Glad to see you got it working. There are several different causes of SQL Server databases not recovering after a RESTORE. You found one of the solutions.

Sometimes running RESTORE DATABASE dbname WITH RECOVERY from the Query Analyzer will work.

Sometimes stopping and restarting SQLSERVER Service will work.

Sometimes you just have to do as you did.

My issue was with Backup Exec version. There was a version where if you had Win2000 Advanced Server on a cluster and were using SQL Server 2000 Enterprise edition clustered and had a few other things, Backup Exec didn't work at all unless you had the hotfix applied.

I now do the 'native' SQL Server Backup commands to create a backup on my hard drives, then I use BE to copy those files to tape.

-SQLBill

(Sorry I wasn't able to respond sooner....apparently you are in a different time zone than me.)

 

[iklaas]

Hi SQLBill,

Thanks for replying! I'm in the Netherlands and we were working on this late last night. I read the other tread but in it you clearly asked for people NOT to reply so I figured I'd create a new case.

We will take your tip of backing up to heart and do it that way from now on. However, I find it strange that BE pretents to be able to do something and then it is not. We are by no means DBA's and have a very broad working area so we are not at all informed well enough on SQL issues to really say anything useful. (just like this sentence really;-))

Ivar

 

[SQLBill]

Just in case you aren't aware of it, TEK-TIPS also has two great Microsoft SQL Server forums. One for Administration and one for Programming.

-SQLBill

 

[iklaas]

Thanks SQLBill,

Perhaps you can enlight us on the following:
We created a new database, which is empty and import the data. This works, but we did not get ALL permissions! We used DTS import-expor twizard. When we choose to copy all objects we get error: "failed to copy objects". What gives? We would be ever so thankful for a reply!

 

[SQLBill]

I don't use DTS, so I can't help you with that. I suggest posting in the MS SQL Server: Setup and Administration forum (FORUM962).

-SQLBill