Our NIM server has a filesystem named /export/mksysb just to hold mksysb images. We use to have the client LPARs NFS mount this filesystem and create their backups there, but with AIX 6.1 TL5, the NIM server doesn't like it when there is already a /export/mksysb entry in the /etc/exports that he didn't put there. Now, we have our NIM server tell the clients to create their mksysb's to the same /export/mksysb filesystem on our NIM server. The difference is that the backups are being handled by our NIM server and it maintains the entries in the /etc/exports file. These are the NIM commands that we use:
First remove the old mksysb resource and file to create enough space for a new mksysb:
Code:
nim -o remove -a rm_image=yes lpar01_mksysb
Create a new mksysb file and NIM resource:
Code:
nim -o define \
-t mksysb \
-a server=master \
-a location=/export/mksysb/lpar01 \
-a source=lpar01 \
-a mk_image=yes \
-a mksysb_flags=iXp \
-a comments="lpar01_mksysb_AIX$(oslevel -r)_defined$(date +%Y/%m/%d)" \
lpar01_mksysb
Also, the NIM server doesn't like to make 2 mksysbs going on at the same time because it may not complete correctly due to limited amount of space in the /exports/mksysb filesystem. This can be over riden by adding the "-F" option to the first part like this:
Whats up guys. I dont ask many questions but this time i need a quick one answerd.
NOS: AIX 4.3.3 and 4.3.2
BOX: RS/6000 F50
i have 12 pv's (mirrored) and 2 vg's and i want them both backed up @ once on one tape drive so i can do it via cron.
I have looked at mksysb and backup. my main... (5 Replies)
Hi All
i have a number of IBM servers with different models, and i want to do a backup for the rootvg using mksysb and that backup will be stored on a 4mm DDS tape.
i have only one machine (p550) which i can use it for testing purposes, so the quesion is that can i test my mksysb backups on... (6 Replies)
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)
Hello,
Last night I applied a DB2 fix pack which is now causing problems with the application that uses db2. Prior to applying the fix pack I did a mksysb(rootvg) which includes the file system that has db2 installed on it. If I do a restore from this will it restore the db2 version back to... (1 Reply)
hi
we are having one rootvg in that we created one lv named mksysb_backuplv
and normally script will run accordingly to take the backup in the cron,here i just want to know if any rootfilesystem was correpted like /usr or /tmp ,then how could i restore the particular filesystme from the... (1 Reply)
i have an AIX server and planning to upgrade the operating system, before that i want to take a system backup which can be used in case of upgrade failure. i dont have NIM server t hold the mksysb backups. so i have the only option of taking the backup on DVD. i have the following optical drive... (5 Replies)
Hi Experts,
I am very new to AIX, I have a mksysb image in one of my aix server (V6), I would like to install this mksysb image on newly lpar. Is it possible without tape and NIM?
Advice would be appreciated.
Regards,
Rockie (11 Replies)
Discussion started by: aix.rockie
11 Replies
LEARN ABOUT HPUX
norewind_close_disabled
norewind_close_disabled(5) File Formats Manual norewind_close_disabled(5)NAME
norewind_close_disabled - determine whether access to tape device special files without the no-rewind-on-close option is allowed
VALUES
Default
Allowed values
DESCRIPTION
Note: this tunable was named in releases prior to HP-UX 11i v3.
This tunable notifies the tape driver whether it should allow access to device special files without the no-rewind-on-close option. When
this tunable is on, the tape driver will fail any open on a tape device special file that does not have the no-rewind-on-close option (that
is, or with a status of
The tunable allows the safe sharing of tape devices in SAN tape backup solution configurations. The disabling of device special files
without no-rewind-on-close in a SAN tape backup solution configuration prevents the accidental sending of a rewind command on close from
HP-UX systems via standard tape commands like which would corrupt a backup in process.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately.
When Should the Tunable Be Turned On?
This tunable should be turned on if the system is going to be used in a SAN tape backup solution configuration.
What Are the Side Effects of Turning the Tunable On?
The tape driver will fail any open to a tape device special file that does not have the no-rewind-on-close option with a status of This
behavior prevents the usage of any tape device special file without the no-rewind-on-close option.
When Should the Tunable Be Turned Off?
This tunable should be turned off if the system is not part of a SAN tape backup solution configuration or the system utilizes will not
function unless it has access to device special files without the no-rewind-on-close option.
What Are the Side Effects of Turning the Tunable Off?
A rewind may be issued accidentally from this system on close, possibly corrupting a backup being issued from another system on the SAN.
What Other Tunables Should Be Changed at the Same Time?
None.
EXAMPLES
Query the current value of the tunable:
Set the value of the tunable to
To save the value of the tunable across reboots:
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by Hewlett-Packard.
SEE ALSO scsi_tape(7), scsimgr_estape(7).
Tunable Kernel Parameters norewind_close_disabled(5)