06-06-2007
If you have another machine, you could configure that as a nim server and keep the mksysb there to re-image the server.
Or if it is just for the upgrade, you could break the rootvg mirror and do an alt_disk_copy to update the free disk with the latest OS and boot through it.
Regards,
Kaps
10 More Discussions You Might Find Interesting
1. AIX
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
Am taking a tape backup and the error output shows this.
----------------------------------------------------------------
====== mksysb errors from /opt/uss/log/run_mksysb.stdout:
0512-038 mksysb: Backup Completed Successfully.
====== mksysb errors from /opt/uss/log/run_mksysb.stderr:
... (1 Reply)
Discussion started by: balaji_prk
1 Replies
3. AIX
Hi, guys
I have experience in UNIX, but more in hpux, have done an mksysb in an Aix server 5.3, and then restore in other server with same model, everithing fine but no TCP/IP configuration and hostname its like "localhost" after the restore. It's something wrong? I've change the configuration,... (5 Replies)
Discussion started by: uadm26
5 Replies
4. AIX
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
5. AIX
Hello,
I'm starting a mksysb with the help of a unix script and the crontab.
The script is scheduled with crontab and executes "mksysb -i -X /dev/rmt0".
When the mksysb is completed the script displays the endtime.
But I also get a lot of cat messages (see below). When I look with "ps -ef... (2 Replies)
Discussion started by: Peter_e
2 Replies
6. AIX
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
7. AIX
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
8. AIX
Hi,
Can any one suggest me how to take the mksysb backup in CD (VCD/DVD). I have tried like #mkcd -d /dev/cd0, but its not working. (3 Replies)
Discussion started by: oprakash
3 Replies
9. AIX
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)
Discussion started by: senmak
1 Replies
10. AIX
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
LEARN ABOUT DEBIAN
systemd-machine-id-commit.service
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8) systemd-machine-id-commit.service SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk
SYNOPSIS
systemd-machine-id-commit.service
DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk
file system. See machine-id(5) for more information about machine IDs.
This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such
as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID
to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes.
See systemd-machine-id-setup(1) for details.
The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system
manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase.
This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to
make it permanent.
SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1)
systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)