03-06-2016
Cloning a system via mksysb backup from one system and restore to new system
Hello All,
I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance.
Moderator's Comments:
|
|
Please use CODE tags for sample input, sample output, and for code segments; not for plain text explaining what you are trying to do.
|
|
Last edited by Don Cragun; 03-06-2016 at 09:42 PM..
Reason: Remove CODE tags.
10 More Discussions You Might Find Interesting
1. AIX
Hi everyone,
I want to clone a AIX 5.2 system from a machine to another one.
So i modified bosinst.data and image.data files (according to future platform) before making mksysb on old platform.
After booting on CD and restoring system using mksysb tape, the installation is launched but ever... (2 Replies)
Discussion started by: fgaulois
2 Replies
2. UNIX for Dummies Questions & Answers
I am new to UNIX and need help in cloning a HPUX 10.2 Ace 5, can anybody please guide me in making a full system backup.
Real Chess (0 Replies)
Discussion started by: real-chess
0 Replies
3. UNIX for Dummies Questions & Answers
Hello,
With AIX 5.3 is it possible to run a mksysb with users logged into the system?
The users are accessing a database app that runs on a separate physical disk than the system files. Does this even matter?
Thanks (1 Reply)
Discussion started by: samsa1mi
1 Replies
4. AIX
I use AIX 5.2 I want to allow a non-root user to do a system backup with 'mksysb' command.
I try to add 'ManageBackup' Role to that non-root user but it have an error "ksh: mksysb: 0403-006 Execute permission denied."
What should I do? (8 Replies)
Discussion started by: AIX122
8 Replies
5. UNIX for Advanced & Expert Users
I have several Solaris 8,9 and 10 servers.
I need to refresh them and avoid doing any OS upgrades. I may have to apply patches when I am done due to the new hardware.
My current servers have internal disk and my new target servers (same processor types) will have only SAN storage. Once the... (0 Replies)
Discussion started by: zzqv9p
0 Replies
6. UNIX for Advanced & Expert Users
Hi,
In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way :
- Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies
7. Solaris
I have installed Solaris 11 Express on my machine and now I am wondering what is the best way to backup (to another hard disc) and restore the system hard disc content.
The backup should to be done every night using a script launched by cron and all previously done backups should be available to... (8 Replies)
Discussion started by: RychnD
8 Replies
8. Solaris
Hi all
I have a DLT tape in that tape backup is there is in veritas volume format and i want to restore it in ufs file system how can i do it?
right now i don't have veritas file system setup. i have only ufs file sysytem
please help some production data is to be restore.
backup was taken... (0 Replies)
Discussion started by: nikhil kasar
0 Replies
9. Cybersecurity
Hello there,
I would like to protect a Linux system from cloning, I don't mind if the cloned hard drive works in the same computer, but I need to avoid it to work in other one, even if it uses exactly same mainboard model and rest of computer parts. I want the cloned system to get frozen or... (4 Replies)
Discussion started by: Installimat
4 Replies
10. Solaris
Hi all,
I am trying to use archiveadm to backup/clone an existing Solaris11.4 system.
However, i failed at media creation with the error -> "Media can only be created from archives containing root-only data"
root@xxx:/mnt/opt/software# zpool list
NAME SIZE ALLOC FREE CAP DEDUP ... (6 Replies)
Discussion started by: javanoob
6 Replies
LEARN ABOUT CENTOS
machinectl
MACHINECTL(1) machinectl MACHINECTL(1)
NAME
machinectl - Control the systemd machine manager
SYNOPSIS
machinectl [OPTIONS...] {COMMAND} [NAME...]
DESCRIPTION
machinectl may be used to introspect and control the state of the systemd(1) virtual machine and container registration manager systemd-
machined.service(8).
OPTIONS
The following options are understood:
-h, --help
Prints a short help text and exits.
--version
Prints a short version string and exits.
-p, --property=
When showing machine properties, limit the output to certain properties as specified by the argument. If not specified, all set
properties are shown. The argument should be a property name, such as "Name". If specified more than once, all properties with the
specified names are shown.
-a, --all
When showing machine properties, show all properties regardless of whether they are set or not.
-l, --full
Do not ellipsize process tree entries.
--no-pager
Do not pipe output into a pager.
--no-ask-password
Do not query the user for authentication for privileged operations.
--kill-who=
When used with kill-machine, choose which processes to kill. Must be one of leader, or all to select whether to kill only the leader
process of the machine or all processes of the machine. If omitted, defaults to all.
-s, --signal=
When used with kill-machine, choose which signal to send to selected processes. Must be one of the well-known signal specifiers, such
as SIGTERM, SIGINT or SIGSTOP. If omitted, defaults to SIGTERM.
-H, --host
Execute operation remotely. Specify a hostname, or username and hostname separated by "@", to connect to. This will use SSH to talk to
the remote machine manager instance.
-P, --privileged
Acquire privileges via PolicyKit before executing the operation.
The following commands are understood:
list
List currently running virtual machines and containers.
status [ID...]
Show terse runtime status information about one or more virtual machines and containers. This function is intended to generate
human-readable output. If you are looking for computer-parsable output, use show instead.
show [ID...]
Show properties of one or more registered virtual machines or containers or the manager itself. If no argument is specified, properties
of the manager will be shown. If an ID is specified, properties of this virtual machine or container are shown. By default, empty
properties are suppressed. Use --all to show those too. To select specific properties to show, use --property=. This command is
intended to be used whenever computer-parsable output is required. Use status if you are looking for formatted human-readable output.
terminate [ID...]
Terminates a virtual machine or container. This kills all processes of the virtual machine or container and deallocates all resources
attached to that instance.
kill [ID...]
Send a signal to one or more processes of the virtual machine or container. This means processes as seen by the host, not the processes
inside the virtual machine or container. Use --kill-who= to select which process to kill. Use --signal= to select the signal to send.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
ENVIRONMENT
$SYSTEMD_PAGER
Pager to use when --no-pager is not given; overrides $PAGER. Setting this to an empty string or the value "cat" is equivalent to
passing --no-pager.
SEE ALSO
systemd-machined.service(8), systemd-logind.service(8), systemd.special(7).
systemd 208 MACHINECTL(1)