Operating System - HP-UX
1748179 Members
3970 Online
108758 Solutions
New Discussion юеВ

Re: Client Rename and Getting Ignite and Client to both use the new client name

 
SOLVED
Go to solution
ddwx2
Occasional Contributor

Client Rename and Getting Ignite and Client to both use the new client name

When an ignite client is renamed the ignite server still knows the client by it's old name. The Ignite GUI can be used to change the icon name which will rename the symlink in /var/opt/ignite/clients. However this still leaves many references in use to the old server name.

When make_net_recovery runs on the client it still mounts the appropriate directories on the Ignite server using the old name. This also means the old server name continues to be used in /var/opt/ignite/recovery/archives on the Ignite server.

I'm looking for a solution that will change all references from the old server name to the new server name or in other words:
1. Enable the client to nfs mount it's ignite directories using it's correct name.
2. Change all Ignite server references from the old name to the new name.
3. Reassign the recovery archive files created to the new client name.

On the client side it looks like the archive_dir line in /var/opt/ignite/recovery/previews might control the client name used for mounting from the Ignite Server.

On the server side is there an easier method than writing a script to search through all the client files and change the old server name to the new server name and finally rename the recovery archive directory itself in /var/opt/ignite/recovery/archives?

I thought about removing the old client and adding the new client but the recovery archives created would not transfer using this method.

Thanks in advance for any suggestions.

D



3 REPLIES 3
Steven E. Protter
Exalted Contributor
Solution

Re: Client Rename and Getting Ignite and Client to both use the new client name

Shalom,

Normally, I would just use the Ignite GUI interface and add a new client and insure any NFS mount points permit access to both the hold and the new client.

The old archives are a problem, but perhaps you could keep some tape archives as a back up.

It should be possible to fool Ignite into using the old archives with DNS alias. Make the two names resolve to the same IP address.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
ddwx2
Occasional Contributor

Re: Client Rename and Getting Ignite and Client to both use the new client name

Thanks for the information.
ddwx2
Occasional Contributor

Re: Client Rename and Getting Ignite and Client to both use the new client name

No further questions.