- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Client Rename and Getting Ignite and Client to...
Operating System - HP-UX
1748179
Members
3970
Online
108758
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2008 10:25 AM
тАО05-19-2008 10:25 AM
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
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
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2008 01:00 PM
тАО05-19-2008 01:00 PM
Solution
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
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
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2008 11:36 AM
тАО05-20-2008 11:36 AM
Re: Client Rename and Getting Ignite and Client to both use the new client name
Thanks for the information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-20-2008 11:37 AM
тАО05-20-2008 11:37 AM
Re: Client Rename and Getting Ignite and Client to both use the new client name
No further questions.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP