Sponsored Content
Full Discussion: hp-ux mksysb equivalent
Operating Systems HP-UX hp-ux mksysb equivalent Post 302179627 by bdittmar on Friday 28th of March 2008 08:06:16 AM
Old 03-28-2008
ignite - HP-UX configuration, installation, and recovery manager

Quote:
Originally Posted by itik
Hi Guys,

Does hp-ux has mksysb equivalent with aix? Or something similar that you can save the system config.

Or you just backup the boot image, that's it.

Thanks in advance,
itik
Hello,

is this you're searching for ?

ignite - HP-UX configuration, installation, and recovery manager

Regards
 

10 More Discussions You Might Find Interesting

1. AIX

mksysb...

Hi friends.. My one problem is not resolved yet I have another. I am planning to take an OS backup of my p550 using "mksysb". Now i am confussed. suppose I give the command to take the backup into a tape drive and my backup size exceeds the tape capacity.. what will happen? will it ask for... (2 Replies)
Discussion started by: balaji_prk
2 Replies

2. AIX

mksysb

I dont have either a tape drive or a DVD Writer attached to the AIX box. Can you let me know the possibilities of making an mksysb in a bootable media? This is required as we have a requirement to upgrade the OS. (2 Replies)
Discussion started by: chrisanto_2000
2 Replies

3. AIX

mksysb backup

hi guys, i just want to take my server's mksysb backup through dvd-rom.but am having the doubt that, while am taking the mksysb backup in image it shows 8GB. So can i confirm that it takes 2 dvds and after writing in 1st cd it will ask for 2nd cd?????? please help me out. (1 Reply)
Discussion started by: rrlog
1 Replies

4. AIX

mksysb

Hello everyone I have two questions. I would like to hear your opinions, your tips. I have several box with aix 5.3. the rootvg in each box has mirror. but I have a cron that makes a mksysb every week. Do you think that it the best to have a mksysb of rootvg if I have a mirror on this... (4 Replies)
Discussion started by: lo-lp-kl
4 Replies

5. AIX

Help with mksysb

Hi All, Working on AIX 4.2 system. On this server there is no tape drive or a DVD Writer attached to the AIX box. I was able to do mksysb, but I got warning message saying it will not be bootable. On the new system, I did install 5.3 and now I need to restore this mksysb image from the... (5 Replies)
Discussion started by: samnyc
5 Replies

6. Linux

Mksysb Equivalent For Linux?

I have experience with making bootable images of AIX systems using mksysb and wondered if there was some type of equivalent software for Linux. Or perhaps some of the folks here have alternatives or unique ideas for how they are backing up their Linux systems enabling them to recover them as... (13 Replies)
Discussion started by: scotbuff
13 Replies

7. AIX

MKSYSB backup

Hi, Currently we are taking mksysb backup through smitty mksysb command and directing the backup to happen on a tape.We have inbuilt tape drives in the AIX servers. Can we take the mksysb backup through 3rd party software tool (Symantec netbackup of IBm TSM). If yes what is the procedure and... (4 Replies)
Discussion started by: dwiravi
4 Replies

8. AIX

savevg - mksysb

Hello, I use commands savevg & mksysb to do backups on an AIX server. Frequently, I have a return code 3. I would know why, but after searches, I did'nt find. If somebody know ... Tell me. Thanks. emetra (2 Replies)
Discussion started by: emetra
2 Replies

9. AIX

mksysb using NIM

I am implementing mksysb backups using NIM. I am using nimsh as client communication and mksysb backup are working fine, but this requires remote logon to be enabled for root. Any thoughts on how can I implement mksysb backups using NIM without enabling remote logon for "root" ? (1 Reply)
Discussion started by: mk8570
1 Replies

10. AIX

Mandatory FS for mksysb

Hi all, my first post. Be kind to me and to my english writing (i'm french) :) During mksysb backup, some files are moving. I don't know yet which files (i'm starting a new job). For now, i'm wondering which fs are mandatory for a mksysb backup. Currently, hereafter the content of rootvg :... (5 Replies)
Discussion started by: Fundix
5 Replies
kconfig(1M)															       kconfig(1M)

NAME
kconfig - manage kernel configurations SYNOPSIS
fields] [config]... comment] src dest comment] config comment] [config] filename comment] comment] behavior] [config] filename comment] behavior] config comment] behavior] config comment] old new comment] config comment] config title DESCRIPTION
is the administrative command for HP-UX kernel configurations. In the first form, will give summary information about the currently run- ning kernel configuration. In the second form, will give information about saved kernel configurations. If configuration names are listed on the command line, the output is restricted to those configurations. In the other forms, supports various administrative tasks on kernel configurations. See kconfig(5) for more information about kernel configurations. Only users with appropriate privileges can specify the or options. Options Includes detailed information about each kernel configuration in the output listing (see below). In addition, the information about each configuration will be followed by the outputs of: for the configuration, so as to include all configuration data. Note: if additional configuration data are available in future releases of HP-UX, they will be included as well. Specifies whether or not to update the automatic backup configuration before the requested change. Also specifies the default backup behavior for future changes. See kconfig(5) for a description of the various backup behaviors. For compatibility with old releases, is accepted as an alias for and is accepted as an alias for These aliases will be removed in a future release. will make a copy of the saved kernel configuration named src. The copy will be named dest. dest must not already exist. The specified comment will be included in the kernel configuration log file entry made for this invocation of For more details on the ker- nel configuration log file, see kclog(1M). Note that it will usually be necessary to quote the comment in order to avoid interpretation by the shell. will delete the saved kernel configuration named config, and any files associated with it. Some files are shared between saved configurations; these files are not deleted until all of the saved configurations using them have been deleted. will display all changes to the current kernel configuration that are being held for next boot. In other words, it will execute: If any additional kernel configuration data become available in future HP-UX releases, changes to them will be included as well. The return value of will be 1 if there are any such changes; see the section below. Not valid in combination with any other flags. will export the saved kernel configuration named config to a system file named filename, replacing the file if it already exists. If no config is specified, the currently running kernel configuration will be exported, including any changes to it that are being held for next boot. The exported file can be later imported using on this system or any other system with compatible HP-UX software. See kconfig(5) and sys- tem(4) for more information about system files. Tells to proceed with the requested operation despite its potentially dangerous nature. When is asked to make a change that could result in unintended data loss, it will ask for confirmation if being run interactively, or print an error message and stop otherwise. The change can be made, and the interactive confirmation bypassed, by running the command with the option. Tells to hold the requested changes until the next boot, even if they could be applied immediately. Discards all changes being held pending for next boot. The currently running configuration will be used at next boot. will import a kernel configuration from the system file named filename, which may have been created by an invocation of (on any system). If config is specified, the resulting kernel configuration will be saved under that name. Otherwise, the resulting kernel configuration will be applied to the currently running system, overwriting any changes that were being held for next boot. The new configuration changes will be held until next boot if they cannot be applied immediately, or if the option is specified. When duplicate entries for particular tunable or module are found in the system file, only the last entry found is used. A kernel configuration cannot be imported successfully unless the running system has all of the necessary kernel software installed. If the importing system is missing kernel software components that were in use on the exporting system, the import will fail. See the option below. Enables and disables saving of system files as and is a copy of system file from which the machine boots. When the feature is switched ON for the first time, is a copy of the system file at that point. is the copy of the system file from which the machine was booted last time. These files are created in will save the current system file as and will keep updating it on every reboot. It will also create a file which contains nothing on first invocation. will remove these files from the machine and will disable this feature. will load the saved kernel configuration named config, overwriting any changes that were being held for next boot. The state of the currently running system will be changed to match the saved configuration. If the changes cannot be applied without a reboot, they will be marked to take effect at next boot. The saved kernel configuration named config will be marked for use at next boot. Any changes to the currently running configuration that are being held for next boot are discarded. Tells to include only the specified fields in its output, and to print them in the machine-readable form described in kconfig(5). See the below. Not valid in combination with The saved kernel configuration named old will be renamed new. The name new must not already be in use. will save the running kernel configuration under the name config. will display all settings of the currently running configuration that are not at their default value. In other words, it will execute: If any additional kernel configuration data become available in future HP-UX releases, settings of them will be included as well. Not valid in combination with any other flags. will change the title of the saved kernel configuration named config to the given title. title will usually need to be quoted to avoid interpretation by the shell. Includes verbose information about each saved kernel configuration in the output listing. The information includes the name and title of the configuration, the pathname of the associated ker- nel, the creation date and time, etc. Requests strict version checking. With this option, an import operation will only succeed if the kernel components installed on the importing system are the exact same versions as those installed on the exporting system. Prints information about the original source of the currently running configuration. Specifically, it describes the source of the most recent complete kernel configuration operation (load, boot, or import). Also, if a saved configuration is marked for use at next boot, this option will identify it. Note that this source information does not imply that the currently running configuration matches its original source. may say that the currently running configuration was loaded from the saved configuration but that does not mean that the two are identical. Either one may have been changed since the load occurred. Developer's Note The layout and content of output may change without notice, except when is specified. Scripts or applications that need to parse the out- put of are expected to use the option. See kconfig(5) for details. The fields supported in a request are: The name of the saved kernel configuration. The title for the saved kernel configuration. If the configuration does not have a title, this field will be empty. The date and time of the last save of the configuration, in the format returned by The date and time when the configuration was created, in the format returned by The username of the user who created the configuration, if available. The date and time of the last change to the saved configuration, in the format returned by The username of the user who made the last change to the saved configuration, if available. The pathname of the corresponding kernel directory. The special field name may be specified to indicate that all defined fields should be included in the output. The output may include fields not listed in this man page. The fields will be listed in unspecified order. Additional fields may be added in future releases or in patches. RETURN VALUE
returns one of the following values: The requested operation was successful. If was specified, this return value indicates that there are no configuration changes being held for next boot. The requested operation could not be performed immediately as requested, and is being held pending until the next boot. If was specified, this return value indicates that there are configuration changes being held for next boot. The requested operation failed. A diagnostic message is printed. EXAMPLES
To save the current kernel configuration to "myconfig": To delete the saved configuration "useless": To export the current kernel configuration: To import a kernel configuration: To rename a configuration: To load the "nighttime" configuration and apply it immediately: To use the "approved" configuration at next boot: To discard changes being held pending for next boot: To add a description to a configuration: To get a list of all saved configurations: To get details of a saved configuration: SEE ALSO
kclog(1M), kcmodule(1M), kcpath(1M), kctune(1M), mk_kernel(1M), system(4), kconfig(5). available on kconfig(1M)
All times are GMT -4. The time now is 03:12 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy