Unsolved
This post is more than 5 years old
7 Posts
0
7233
May 18th, 2010 05:00
SQL restore
Hello,
I have a problem restoring master database. The problem is that sql instance which is in cluster is not online because of corrupted master database. I try to rebuild it with sql tool but still not working. Also restore do different instance doesnt work. The sql server is 2008 and server 2008 r2.
The question is can i restore master database from networker user for sql to file? That mean that i will restore mdf and ldf to file on some disk, after that i will attached/copy the database to sql instance.
Thanks for help.
Peter
No Events found!



Prozic
7 Posts
0
May 18th, 2010 05:00
Hello Bruno,
The problem is when i use copy restore that i get this errror:
37725:(pid 7404):Recovering database 'msdb' into 'CopyOfmsdb' ...
37827:(pid 7404):Can't configure VDI set (failed to recognize the SQL Server instance name).
35867:(pid 7404):Error processing SQL database 'msdb'.
Restore operation finished with error(s). Refer to the module backup log file for details.
unknown XBSA error -2139684857 (0x80770007)
Peter
BSequeira
30 Posts
0
May 18th, 2010 05:00
Hi,
You can do a directed recover to an alternate location using the NMSQL or using command line:
Please try the following steps:
The following command syntax can be used for the sql recover. This will perform a Copy Restore:
nsrsqlrc -s NetWorker_server_name -c source_client
-d MSSQL:CopyOfProject
-C "Project_Data=C:\RelocationPath\CopyofProject_Data.mdF,
Project_Data2=C:\RelocationPath\CopyofProject_Data2.ndF,...,
Project_Log=C:\Relocation\Path\Project_Log.ldF" MSSQL:Project
NOTES:
1. If the "Relocation path" includes spaces then it needs to be put in single quotes: e.g. 'c:\program files\data'
The complete -C string still requires double quotes.
2. The C:\Relocation\path should already exist on the target SQL server.
Let me know if this helps.
Regards,
Bruno
BSequeira
30 Posts
0
May 18th, 2010 06:00
You will first need to repair the Master database by Running the SQL setup and repair option, this will repair the SQL installation and system databases, and should bring you SQL services back online.
If SQL setup program does not work, please try to rebuild using command line:
To rebuild system databases for an instance of SQL Server 2008:
Insert the SQL Server 2008 installation media into the disk drive, or, from a command prompt, change directories to the location of the setup.exe file on the local server. The default location on the server is C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Release.
From a command prompt window, enter the following command. Square brackets are used to indicate optional parameters. Do not enter the brackets. When using the Windows Vista operating system with User Account Control (UAC) enabled, running Setup requires elevated privileges. The command prompt must be run as Administrator.
Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts /[ SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName]
You should be able to restore you database after this process.
Regards,
Bruno.
elvinperez
87 Posts
0
May 18th, 2010 07:00
Hello,
After retrieving the database the same application of the attached SQL database, if the database is corrupted you should perform a normal return from this database.
Regards,
Prozic
7 Posts
0
May 18th, 2010 07:00
Hello,
The problem is that Setup /QUIET /ACTION=REBUILDDATABASE /INSTANCENAME=InstanceName /SQLSYSADMINACCOUNTS=accounts /[ SAPWD= StrongPassword ] [ /SQLCOLLATION=CollationName] doesnt work.
Thats why i would like to restore databases as files.
BSequeira
30 Posts
0
May 18th, 2010 07:00
If the command line repair doesent work, the syntax could be wrong, or something is missing.
Do you have the database templates on the SQL template folder? Are you running the command using the correct account and instance name?
Please follow these steps: http://technet.microsoft.com/en-us/library/dd207003.aspx
I think you should contact Microsoft to assist you with the SQL instance repair since there is not much you can do from a Networker point of view, until this is sorted.
Regards,
Bruno
Prozic
7 Posts
0
May 18th, 2010 08:00
You are right. Until we fix sql instance we cant restore with networker.
Regards,
Peter
elvinperez
87 Posts
0
May 18th, 2010 08:00
Hello,
You must recover the database with the application of networker (Networker Module for SQL Server), this should not give any problem if the indexes exist.
Prozic
7 Posts
0
May 18th, 2010 10:00
I did it. We manage to restore some old master form sql backup to other instance. After that we could start fail sql instance and restore other DB with networker.
Thanks for help everyone!
Best regards,
Peter