SQL Restore - Could not find directory continuation
Hi,
I'm having issues restoring saveset before a certain point - in this case 24/03 3.00 am. When I change the mark it gives me the message:
16236:nwmssql: Could not find directory continuation //<84>/
Now a few weeks ago, I was restoring the same DB's from the same instance and even older datasets and it did work! However, this is a clustered SQL instance and we're having massive issues with that cluster. But that shouldn't affect the historical backups?
Our whole environment is running on 8.2.1.6 (.806). Any ideas?
I would open a ticket with support for this. I have seen this with nsrauth long time ago, but I have seen it with some older SQL module versions where 2GB chunks were created and that caused issues (at some point there was article about it in KB). Not sure with what version your backup was made, but more experienced support person will be able to connect the strings and check it out.
Never got a real solution, however the issue seemed to be related to the GUI - a workaround is doing the restores command line, then it will work correctly. In the rare case where I had this issue I simply used the workaround when needed.
I am having this same issue, basically a year later and this is the only post I can find on the topic. Is there really no solution to this issue? I'm new to Networker, taking on a process left by someone that moved on when I got here. I don't know any of the command line and barely know the GUI. Surely they has to be a fix for this. :/
The original poster was using NMM 8.2.1.x when he encountered this issue.
The workaround was to recover using the command nsrsqlrc to perform a command line recovery.
Since that particular version, there has been improvements to the NMM product. I would suggest upgrading your NetWorker client and NMM software to a more recent version, and see if the problem returns. Please follow the link to:
and select the version that you are currently using, and then download the latest for that branch. If you are using NMM 8.2.1.x, then you could try NMM 8.2.2.6.
I'll have to find out if that is an option for us. The version being used is 8.2.0.1.479, so admittedly not the same as the latest release. Having no experienced person in-house that would do an upgrade on NetWorker, which is doing many backups, is a whole other issue. Not a warm fuzzy at all. On one SQL Server instance it is displaying and responding properly, and on the other, it is having the error in this post. Both servers running the same OS on nearly identical hardware (clustered servers but one has a little more memory).
The video has been created to demostrate to restore a SQL backup when UI browsing is not possible (NMM will not be able to browe the backup when Meta data / Meta saveset is not available. Additionally, this video clearly explains on how to fetch the savetime for the SQL command line restore.
ble1
6 Operator
•
14354 Posts
•
56186 Points
2523
0
Posted April 13th, 2016 05:00
I would open a ticket with support for this. I have seen this with nsrauth long time ago, but I have seen it with some older SQL module versions where 2GB chunks were created and that caused issues (at some point there was article about it in KB). Not sure with what version your backup was made, but more experienced support person will be able to connect the strings and check it out.