Networker

Re: [Networker] MSSQL restore does not start (update and resolved)

2006-09-08 08:02:06
Subject: Re: [Networker] MSSQL restore does not start (update and resolved)
From: Maarten Boot <maarten.boot AT MBU DOT HR>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 8 Sep 2006 13:59:20 +0200
 This isue is resolved.

The following is the way to resolve it.

Before I came the previous owners had a machine named mbudbs.mbu.local

After migration of software to 7.3.1 somewhere along the way the created a new 
client named mbudbs (without the mbu.local)

Although the old clientname had been deleted from the list of clients and no 
savedet belonging to this client is known in the media database this blocked 
the restore.

Tried to delete the client mbudbs an recreate as mbudbs.mbu.local to see if the 
hostname (which was in the deamon.log file) could be the reason for the 
failure. 
I could however not create a host mbudbs.mbu.local with the client-id of mbudbs 
as the software mentioned that there was a client-id (different then the one I 
noted down for mbudbd) still associated to the name mbudbs.mbu.local.

By creating a dummy client with that blocking client-id (which was not used in 
any backup in the mediadatabase) I succeded in making the restore work.

To sum up this mess.

Deleted and recreated mbudbs with the same client-id that it had before

Created a dummy client with the client id of the offending old client name 
(mbudbs.mbu.local) 

The restore now finds the data belinging to mbudbs with alias mbudbs.mbu.local 
as beloning to the same clinet-id and it works.

So nice that legato did not complain when creating mbudbs with alias 
mbudbs.mbu.local directly, nor that the restore request does not mention the 
offending client-id.

Any way it works  now. (its quite frustrating if you cant restore your 
companies main database anymore).

One question remains.

How can we get rid of any older client-ids??
Deleteing the client is clearly not enough (and rightly so)
But if no associated data is in the media database why isnt it freed ??

Maarten


-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Maarten Boot
Sent: Friday, September 08, 2006 8:57 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] MSSQL restore does not start

I am trying to restore data from a mssql backup using the legato plugin for 
mssql.

We run 7.3.1 with the latest mssql module 4.1 on a win2003 cluster

After selecting the right data sets and asking the client which volume I need 
(to which I get the correct answer) No volume gets mounted and the restore 
never starts mounting the volume and restoring the data.

In the deamon.log on the server I see the following

09/08/06 08:45:30 ansrd: vol_attr, err: aggr_rlists: bad return from vol_info
09/08/06 08:45:30 ansrd: Cannot find the volume needed
09/08/06 08:45:30 ansrd: cannot look up save set for host mbudbs.mbu.local and 
savetime 1157600504
09/08/06 08:45:30 ansrd: vol_attr, err: aggr_rlists: bad return from vol_info
09/08/06 08:45:30 ansrd: Cannot find the volume needed
09/08/06 08:45:30 ansrd: cannot look up save set for host mbudbs.mbu.local and 
savetime 1157600504
09/08/06 08:45:30 ansrd: vol_attr, err: aggr_rlists: bad return from vol_info
09/08/06 08:45:30 ansrd: Cannot find the volume needed
09/08/06 08:45:30 ansrd: cannot look up save set for host mbudbs.mbu.local and 
savetime 1157600504

Interestingly I just saw that the cluster service mbudbs is defined as a client 
with the name mbudbs and has an alias mbudbs.mbu.local.
Could that be the problem somehow ?

Maarten

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems wit this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or via RSS at 
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu 
if you have any problems
wit this list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

<Prev in Thread] Current Thread [Next in Thread>