Networker

Re: [Networker] Rename MS SQL client?- RESOLVED

2012-03-05 14:51:29
Subject: Re: [Networker] Rename MS SQL client?- RESOLVED
From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Mon, 5 Mar 2012 14:50:20 -0500
The answer is - yes, the old SQL5 client aggravates matters slightly. You 
must first create a "dummy" client (one that has no scheduled backup) 
called something like "OLD-SQL5", and use the client ID of the old client 
that was previously named SQL5.

Then, you cam create a new client called SQL5, giving it the client ID of 
SQL4, and Networker will quite politely ask you if you want to rename 
"SQL4" to "SQL5". You say yes, and then go about your business ...

And the "OLD-SQL5" client definition will not use a license, since it has 
no scheduled backups ...

So I should be good to go

-- 
Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2500 Jackson St
Philadelphia, PA 19145
Tel:  215-684-4180
Cell: 215-252-0143
<mailto:michael.leone AT pha.phila DOT gov>


EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU> wrote on 
03/05/2012 08:37:51 AM:

> From: Michael Leone <Michael.Leone AT PHA.PHILA DOT GOV>
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Date: 03/05/2012 08:38 AM
> Subject: [Networker] Rename MS SQL client?
> Sent by: EMC NetWorker discussion <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
> 
> I have a MS SQL client (SQL4, IP = x.x.x.154); this is a cluster client. 

> Over the weekend my DBAs migrated all it's functions over to a new name 
> (SQL 5, with the same IP x.x.x.154). I want to verify what I need to do 
> ...
> 
> Save the client ID of the SQL4 client
> Delete the SQL4 client
> Create a new client SQL5, with the same IP *and* the same client ID as 
> SQL4
> (that should save all the history of SQL4, but it will be accessible as 
> the new name SQL5)
> 
> Possible wrinkle: there used to be a separate client called SQL5 (not 
sure 
> of the IP), which had a different client ID ...
> 
> The DNS name is now SQL5, BTW - SQL4 doesn't actually exist anywhere ...
> 
> That should all Just Work, creating a new SQL5 with SQL4's client ID, in 

> order to keep all the history available, and the fact that there was a 
> previous client with the same name (SQL5) should be immaterial, as the 
> client IDs  are completely different. Correct?
> 
> -- 
> Michael Leone
> Network Administrator, ISM
> Philadelphia Housing Authority
> 2500 Jackson St
> Philadelphia, PA 19145
> Tel:  215-684-4180
> Cell: 215-252-0143
> <mailto:michael.leone AT pha.phila DOT gov>
> 
> 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 
> with 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 with 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>