Backup Exec 10d SQL redirect restore

Hello,

A Windows Server 2000 SQL server running SQL 2000 experienced a motherboard failure with onboard RAID. The data has been backup up using Backup Exec 10d. This includes all SQL databases, drives, and System State. Luckily the day before they had backup the production database directly from the sqldata folder onto a hard drive which is what I loaded on another Server 2000 box running SQL2000. This loaded just fine by attaching the database. We now need the non production databases that were backed up on TAPE. I tried doing a SQL redirect restore to the temp SQL box, but it keeps failing saying the Agent is not available. It seems to keep looking for the old SQL box. Can I grab the database .ldf and .mdf files which I can easily attach to the running SQL server as I did with the hard drive files? Hopefully simply attaching databases like that is OK?

Your assistance is most appreciated as I am not very good at SQL and BE working together.
tacshose1Asked:
Who is Participating?
 
honmapogCommented:
chakko's suggestion may work.
Backup Exec needs to see the original system on the network before it can do a (redirected) restore.
Should chakko's suggestion of fooling the system through the hosts file not work and if you're doing a redirected restore, you can just rename a client system as the original name of the SQL 2000 server. You may have to quickly install a BE Remote Agent on it as well. When you do the redirected restore, BE will see that "original" system and then ignore it and carry on redirecting the restore to the system you want the backup restored to.
0
 
AnujSQL Server DBACommented:
Is your SQL Server Agent Stopped? if this is stopped then start SQL Server Agent.

Also, if you have mdf and ldf files you can easily attach in the development box.
0
 
prashant9885Commented:
Databases (.mdf and ldf) backed up through agent can be restored only through agent, either to original location or different location (path) on the same server  (OR) to different SQL server instance.

Refer the document for help.

http://www.symantec.com/business/support/index?page=content&id=TECH56694

Also check the credentials used to access the destination box, if it accepts SA and windows authentication.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
tacshose1Author Commented:
The SQL server agent is running. Perhaps I will try reinstalling the Backup exec SQL server agent on this server.

To restore the databse on a new server can I just restore the single database I need or do I need to restore "Master" and so on?
0
 
prashant9885Commented:
You can restore single database (application) No need of system databases.l
0
 
tacshose1Author Commented:
Is it proper to just attached ldf and mdf files to a SQL server and it is ready for use?
0
 
tacshose1Author Commented:
Ok, I have loaded a server with a new Windows 2003 install and installed SQL 2000 SP3a just like the box that failed. The previous Windows Server name was "SQL" and the new Windows Server name is "Cr-sqltest" The SQL agent is installed and running. I can check permissions problems, but it does not seem to even get that far based upon the below error.

When I try to run a restore I get the below error:
Click an error below to locate it in the job log
Restore- SQLThe Media Server was unable to connect to Remote Machine SQL. The machine could not be found on the network.
The Media Server will fall back on the local agent to try and complete the operation.
Remote Agent not detected on SQL.

Even though i full out the SQL redirect and SQL areas it keeps looking for the old server.

Thoughts?
0
 
tacshose1Author Commented:
What can I do to make this work?
0
 
tacshose1Author Commented:
"Also check the credentials used to access the destination box, if it accepts SA and windows authentication."

Yes, these have been checked and match up.
0
 
tacshose1Author Commented:
"Is your SQL Server Agent Stopped? if this is stopped then start SQL Server Agent.

Also, if you have mdf and ldf files you can easily attach in the development box."

The Agent is not stopped. It has also been reinstalled via Push from the media server, and is correctly running.

I unfortunately do not have the MDF/LDF files, just the Backup Exec tapes.
0
 
chakkoCommented:
Can you edit you hosts file on the backup server and make a manual entry of SQL and give it the ip of your target machine?

Just suggesting a 'trick' so that the backup can find the SQL machine to complete your task.
0
 
tacshose1Author Commented:
Thank you for the responses. I had no idea BE needed to see the old server.

Chakko's,  how do I change the hosts file?
0
 
chakkoCommented:
look at c:\windows\system32\drivers\etc

its the hosts file (no extension). You may need to change the read only status

add this line (change for your info) and see how it works.

192.168.1.1     SERVERNAME      SERVERNAME.DOMAIN.LOCAL
0
 
honmapogCommented:
Open c:\winnt\system32\drivers\etc\hosts file in notepad.

At the bottom of the file, add an entry as below

ip_address_new server                     hostname_old_sql_server

Of course replace the ip_address_new_server with the actual IP address, and replace hostname_old_sql_server with the actual hostname of the old sql server.
Then save the file and try the restore again.
If the problem remains, edit the hosts file again and remove the changes you made.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.