Unsolved
This post is more than 5 years old
96 Posts
0
1100
November 3rd, 2016 14:00
Scan an expired MSSQL backup
Hi, all.
I need help with this case: I have a MSSQL backup from 31Mar. It was expired and recyclable. I need to restore this backup. These are the steps I have done:
1. Change mode to nonrecyclable
2. Change retention policy
3. Scanner -i -S XXXXXX dev to rebuild index
4. nsrck -L7
Now, I can see the backup from Networker Module for SQL in the list of backup versions, but I cannot change browse time to this backup version. Do I forget something?
NW version 8.2.3 and NMM version is 8.2.2
Thanks in advance
0 events found
No Events found!


ElanC
53 Posts
0
November 3rd, 2016 22:00
NMM SQL Saveset generates metasaveset per backup. This saveset is always marked as INCR backup type. Hence, you need make the same changes to the metadata saveset to browse in the NMM SQL UI.
ledugarte
96 Posts
0
November 4th, 2016 06:00
Hello, ElanC.
Thanks for your feedback, but after review my SQL full backups, I cannot see any incr savesets... all of them are MSSQL:, and the index saveset.
bingo.1
2.4K Posts
0
November 4th, 2016 11:00
Let me add some general issues here as there seems to be a general misunderstanding:
1. Change save set mode to 'nonrecyclable'. o.k.
2. Change retention date for that save set (nsrmm -e -S )
Policies only apply to new save sets - once they exists in the media index, changing a policy does have no influence.
3. "scanner -i -S XXXXXX" will only work if there is file index info at all.
A lot of db backups already start their lifecycle not as 'browsable' but as 'recoverable' - which makes sense as you most
likley never receover a part of such save set.
4. Do not use "nsrck -L7" - it does not make sense in this case.
ledugarte
96 Posts
0
November 4th, 2016 12:00
Bingo, a few comments.
1. Change save set mode to 'nonrecyclable'. o.k.
2. Change retention date for that save set (nsrmm -e -S )
Policies only apply to new save sets - once they exists in the media index, changing a policy does have no influence.
You are correct. It was a misunderstand. I changed the retention date for the saveset. Obviously, tha's why I wrote the command.
3. "scanner -i -S XXXXXX" will only work if there is file index info at all.
I am not agree with you. If you use scanner, as I understand, Networker reads the media and repopulate the file index. If I had index backup, I would recover it using nsrck.
4. Do not use "nsrck -L7" - it does not make sense in this case.
I am agree, it was a desperate action.
In case I lost all my backup environment, and I only had a tape with a DB expired backup, I would like to know that I could recover it. I think scanner is done for this case... Am I wrong?
ElanC
53 Posts
1
November 8th, 2016 00:00
Hello ledugarte,
I still doubt on browing the SQL saveset's in the NMM SQL UI. I am very much sure that SQL Meta saveset's needed for the UI browsing (NMM SSMS and NWMSSQL.exe). I think, command line restore should be possible for the backups without SQL Metasavesets.
Thanks,
Elango C
mkeil
68 Posts
1
November 8th, 2016 01:00
Hi ledugarte,
have you checked the NMM Advanced Recovery Guide? Maybe that helps.
NMM 8.2.1 Advanced Recovery Guide, Rev 1, Page 49: Recovering NMM data from recoverable or eligible for recycling save sets
Regards
mkeil
ledugarte
96 Posts
0
November 8th, 2016 06:00
Hello, ElanC.
After review in NMM Advance Recovery Guide, I can see that metadata savesets exists. Thanks for your help. I will do a research.
ledugarte
96 Posts
0
November 8th, 2016 06:00
Thanks. I didn't know about this guide. I will do a research.
ElanC
53 Posts
0
November 15th, 2016 00:00
Hi Ledugarte,
You may want refer the Admin/user guide for NW SQL backups. I think, there is a mention of meta savesets. Let me know queries, if any.
Thanks,
Elango C