- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: newbies to ignite ux
Operating System - HP-UX
1753809
Members
8777
Online
108805
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
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
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
03-04-2001 08:19 PM
03-04-2001 08:19 PM
Hi,
I am quite new to ignite ux. I have read through some of the documentation here though I am still a little bit confused.
I have two servers svr1 and svr2, both have ignite ux installed. To do a make_net_recovery,
Is this sufficient just to use the following command?
make_net_recovery -a svr1:/image
Let said I have already export the /image in svr1.
anyhelp will be appreciated.
Thanks!
I am quite new to ignite ux. I have read through some of the documentation here though I am still a little bit confused.
I have two servers svr1 and svr2, both have ignite ux installed. To do a make_net_recovery,
Is this sufficient just to use the following command?
make_net_recovery -a svr1:/image
Let said I have already export the /image in svr1.
anyhelp will be appreciated.
Thanks!
abc
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-05-2001 10:06 AM
03-05-2001 10:06 AM
Solution
I run Ignite v.11, on a number of HPUX 10.20 machines and the command I have inserted into the cron file on each server looks something like this ...
0 12 * * * /opt/ignite/bin/make_net_recovery -s Igniteserver.domain.com -a Igniteserver.domain.com/archive/Machinename -x inc_entire=vg00 -x exclude=/dontback
The above is (of course) all one line and the following explains it ...
0 12 * * * = the crontab format of saying run the following at 0 minutes, 12 hours (noon), every day, every month and every year. You would not include this part in a command line or a script. This is crontab specific.
/opt/ignite/bin/make_net_recovery = is, of course, is the command for make_net_recovery itself.
-s Igniteserver.domain.com = the '-s' option stands for source and references the location of the Ignite server which is managing the backup. Even though the command is running on the machine which is being backed up, an Ignite server must be contacted by the command. Igniteserver.domain.com is the FQDN of the Ignite server. You can use IP addresses as well.
-a Igniteserver.domain.com/archive/Machinename = the directory location to store the Ignite recovery file which is made. The file will be stored on the machine Igniteserver.domain.com, in the directory /archive/Machinename. Although the server and the storage machine location are the same here, they do not have to be. You could use a third file server as the location as long as both machines can NFS to the directory. The final directory /Machinename must belong to bin:bin (using the command 'chown bin:bin Machinename') and be writable by the Ignite server and the machine being backed up.
-x inc_entire=vg00 = an option telling the make_net_recovery command to back up ALL of volume group 'vg00'
-x exclude=/dontback = an option telling the make_net_recovey command NOT to back up the directory '/dontback".
Hope this helps and is not more confusing :-)
Mike
0 12 * * * /opt/ignite/bin/make_net_recovery -s Igniteserver.domain.com -a Igniteserver.domain.com/archive/Machinename -x inc_entire=vg00 -x exclude=/dontback
The above is (of course) all one line and the following explains it ...
0 12 * * * = the crontab format of saying run the following at 0 minutes, 12 hours (noon), every day, every month and every year. You would not include this part in a command line or a script. This is crontab specific.
/opt/ignite/bin/make_net_recovery = is, of course, is the command for make_net_recovery itself.
-s Igniteserver.domain.com = the '-s' option stands for source and references the location of the Ignite server which is managing the backup. Even though the command is running on the machine which is being backed up, an Ignite server must be contacted by the command. Igniteserver.domain.com is the FQDN of the Ignite server. You can use IP addresses as well.
-a Igniteserver.domain.com/archive/Machinename = the directory location to store the Ignite recovery file which is made. The file will be stored on the machine Igniteserver.domain.com, in the directory /archive/Machinename. Although the server and the storage machine location are the same here, they do not have to be. You could use a third file server as the location as long as both machines can NFS to the directory. The final directory /Machinename must belong to bin:bin (using the command 'chown bin:bin Machinename') and be writable by the Ignite server and the machine being backed up.
-x inc_entire=vg00 = an option telling the make_net_recovery command to back up ALL of volume group 'vg00'
-x exclude=/dontback = an option telling the make_net_recovey command NOT to back up the directory '/dontback".
Hope this helps and is not more confusing :-)
Mike
"If we treated each person we met as if they were carrying an unspeakable burden, we might almost treat each other as we should." Dale Carnegie
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