Start a Conversation

Unsolved

This post is more than 5 years old

849

May 18th, 2016 05:00

Unable to restore small database

Hi,

we have NW 8.2.1.

Everything is working well except we are facing minor issue with restoring small DB.

DB is being baked up FULL everyday.

In order to recover that DB, NW is searcihg for backup on the tape volume that has been taken out because it was full.

We have new tape, and we have new savesets on that volume for that DB, so there should be no problem with restoring that DB.

I hope You understand my question and that somebody can help me.

Thanks in advance

14.3K Posts

May 18th, 2016 05:00

What DB is that?  Anyway, what you should realize is that DB can be restored at some point in time and then API/NW will request data needed to restore that data.  So, if data requested requires ssid which is on tape - it requires it.  Best thing you can do it to supply it.  Each DB backup is different and it really depends what you are (and how) restoring.

2 Posts

May 18th, 2016 06:00

Thank You for Your answer.

Its MSSQL database.

Basiclly we where backing up that DB to tape 1 (for example). That tape got full and we replaced it with new one (tape 2 for example).

That DB continued to be backed up on tape 2 for  a month now, full backup every day.

But shouldnt we be able to restore that DB from new tape - tape 2 ?

2.4K Posts

May 18th, 2016 09:00

As already mentioned - it depends what you have and what you are doing.

In general, you are right. It should only use the second tape.

But if you have specified the backup time wrong (just an example) then NW might use the elder tape.

In the moment, we do not know anything else - only you can let us know.

14.3K Posts

May 19th, 2016 03:00

It should unless specified DB to be restored includes records only on tape 1.

43 Posts

May 19th, 2016 04:00

Hello,

Please verify that you use the correct browse time (by default, it uses the current time and you shouldn't have any problem), after that check the required volumes (tape 2) should be in the required volumes list - in your example.

example to verify the volume using CLI on a specific day (login to Networker Server):

mminfo -q "client=MSSQL_CLIENT_NAME, savetime<05/19/2016 23:59:59, savetime>05/19/2016 00:00:00" -r 'ssid,name,volume,savetime'

The above command will give you the ssid, saveset name, savetime and the required volume (tape).

No Events found!

Top