Close All Files on the Archive or Virtual Disk
Using the ldmp2v Command
This department includes examples for the iii phases of conversion.
Case xiv-oneCollection Phase Examples
-
Sharing an NFS-mounted file system. The post-obit example shows the simplest way to perform the collect step where the source and target systems share an NFS-mounted file system.
As superuser, ensure that all required UFS file systems are mounted.
volumia# df -m Filesystem kbytes used avail chapters Mounted on /dev/dsk/c1t1d0s0 16516485 463289 15888032 3% / /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0% /etc/mnttab /dev/dsk/c1t1d0s3 8258597 4304 8171708 1% /var swap 4487448 sixteen 4487432 one% /var/run bandy 4487448 sixteen 4487432 1% /tmp /dev/dsk/c1t0d0s0 1016122 9 955146 1% /u01 vandikhout:/u1/home/dana 6230996752 1051158977 5179837775 17% /home/dana
The post-obit exammple shows how to run the collection tool when the source and target systems share an NFS-mounted file system:
volumia# ldmp2v collect -d home/dana/volumia Collecting organisation configuration ... Archiving file systems ... Determining which filesystems will be included in the archive... Creating the archive... 895080 blocks Annal creation complete.
-
Non sharing an NFS-mounted file system. When the source and target systems do not share an NFS-mounted file system, the file organisation image tin can be written to local storage and later copied to the command domain. The Wink Archive utility automatically excludes the archive that it creates.
volumia# ldmp2v collect -d /var/tmp/volumia Collecting system configuration ... Archiving file systems ... Determining which filesystems volition be included in the archive... Creating the archive... 895080 blocks Archive creation complete.
Copy the flash archive and the manifest file from the /var/tmp/volumia directory to the target system.
Tip -In some cases,
ldmp2vmight show
cpiocommand errors. Most ordinarily, these errors generate messages such as
File size of etc/mnttab has increased by 435. You tin ignore messages that pertain to log files or to files that reflect the arrangement land. Be sure to review all fault messages thoroughly.
-
Skip file-system backup step. If you already create backups of the system using a third-party backup tool such equally NetBackup, you tin can skip the file organization fill-in step by using the none archiving method. When you use this option, only the organisation configuration manifest is created.
volumia# ldmp2v collect -d /home/dana/p2v/volumia -a none Collecting system configuration ... The post-obit file organisation(s) must be archived manually: / /u01 /var
Note that if the directory specified by –d is not shared past the source and target systems, you must copy the contents of that directory to the control domain. The directory contents must be copied to the command domain prior to the preparation phase.
The following examples show how you might employ the ldmp2v collect command.
Example fourteen-2Preparation Phase Examples
-
The following case creates a logical domain called volumia past using the defaults configured in /etc/ldmp2v.conf while keeping the MAC addresses of the physical system:
# ldmp2v prepare -d /home/dana/p2v/volumia -o go along-mac volumia Creating vdisks ... Creating file systems ... Populating file systems ... Modifying invitee domain Bone epitome ... Removing SVM configuration ... Unmounting invitee file systems ... Creating domain volumia ... Attaching vdisks to domain volumia ...
-
The following command shows information about the volumia logical domain:
# ldm list -50 volumia NAME State FLAGS CONS VCPU MEMORY UTIL UPTIME volumia inactive ------ 2 4G NETWORK NAME SERVICE DEVICE MAC Way PVID VID vnet0 primary-vsw0 00:03:ba:1d:7a:5a ane Deejay Name DEVICE TOUT MPGROUP Book SERVER disk0 volumia-vol0@primary-vds0 disk1 volumia-vol1@primary-vds0
-
The following example shows how to completely remove a domain and its dorsum-end devices by using the –C option.
# ldmp2v prepare -C volumia Cleaning upwards domain volumia ... Removing vdisk disk0 ... Removing vdisk disk1 ... Removing domain volumia ... Removing volume volumia-vol0@chief-vds0 ... Removing ZFS book tank/ldoms/volumia/disk0 ... Removing volume volumia-vol1@chief-vds0 ... Removing ZFS volume tank/ldoms/volumia/disk1 ...
-
The following example shows how to resize one or more file systems during P2V past specifying the mount indicate and the new size with the –chiliad option.
# ldmp2v prepare -d /habitation/dana/p2v/volumia -m /:8g volumia Resizing file systems ... Creating vdisks ... Creating file systems ... Populating file systems ... Modifying guest domain OS epitome ... Removing SVM configuration ... Modifying file systems on SVM devices ... Unmounting guest file systems ... Creating domain volumia ... Attaching vdisks to domain volumia ...
The following examples show how yous might employ the ldmp2v gear up control.
Example 14-3Conversion Phase Examples
-
Using a network installation server. The ldmp2v catechumen command boots the domain over the network by using the specified virtual network interface. You lot must run the setup_install_server and add_install_client scripts on the installation server.
On Oracle Solaris 10 systems, y'all can use the Oracle Solaris JumpStart feature to perform a fully automated conversion. This feature requires that you create and configure the appropriate sysidcfg and profile files for the customer on the JumpStart server. The profile should consist of the following lines:
install_type upgrade root_device c0d0s0
The sysidcfg file is only used for the upgrade operation, so a configuration such as the post-obit should exist sufficient:
name_service=NONE root_password=uQkoXlMLCsZhI system_locale=C timeserver=localhost timezone=Europe/Amsterdam terminal=vt100 security_policy=NONE nfs4_domain=dynamic auto_reg=disable network_interface=PRIMARY {netmask=255.255.255.192 default_route=none protocol_ipv6=no}For more than information about using JumpStart, see Oracle Solaris ten 8/11 Installation Guide: Custom JumpStart and Avant-garde Installations .
Annotation -The instance
sysidcfgfile includes the
auto_regkeyword, which was introduced in the Oracle Solaris 10 9/10 release. This keyword is required but if you are running at least the Oracle Solaris 10 9/ten release.
# ldmp2v convert -j -n vnet0 -d /p2v/volumia volumia LDom volumia started Waiting for Solaris to come ... Using Custom JumpStart Trying 0.0.0.0... Connected to 0. Escape graphic symbol is '^]'. Connecting to console "volumia" in group "volumia" .... Press ~? for command options .. SunOS Release 5.10 Version Generic_137137-09 64-bit Copyright (c) 1983-2010, Oracle and/or its affiliates. All rights reserved. Configuring devices. Using RPC Bootparams for network configuration information. Attempting to configure interface vnet0... Configured interface vnet0 Reading ZFS config: washed. Setting up Coffee. Please wait... Serial console, reverting to text install Beginning system identification... Searching for configuration file(s)... Using sysid configuration file 129.159.206.54:/opt/SUNWjet/Clients/volumia/sysidcfg Search complete. Discovering additional network configuration... Completing system identification... Starting remote procedure call (RPC) services: done. System identification consummate. Starting Solaris installation programme... Searching for JumpStart directory... Using rules.ok from 129.159.206.54:/opt/SUNWjet. Checking rules.ok file... Using brainstorm script: Clients/volumia/begin Using contour: Clients/volumia/profile Using finish script: Clients/volumia/stop Executing JumpStart preinstall phase... Executing begin script "Clients/volumia/begin"... Brainstorm script Clients/volumia/brainstorm execution completed. Searching for SolStart directory... Checking rules.ok file... Using brainstorm script: install_begin Using finish script: patch_finish Executing SolStart preinstall stage... Executing begin script "install_begin"... Begin script install_begin execution completed. Alert: Fill-in media not specified. A backup media (backup_media) keyword must be specified if an upgrade with disk space reallocation is required Processing contour Loading local environment and services Generating upgrade actions Checking file system space: 100% completed Space cheque complete. Building upgrade script Preparing system for Solaris upgrade Upgrading Solaris: x% completed [...]
-
Using an ISO image. The ldmp2v convert command attaches the Oracle Solaris DVD ISO prototype to the logical domain and boots from information technology. To upgrade, answer all sysid prompts and select Upgrade.
Caution -A safe bank check is performed prior to converting the guest domain. This check ensures that none of the original system's IP addresses are agile so as to prevent duplicate agile IP addresses on the network. Y'all tin can use the –x skip-ping-test option to skip this safety check. Skipping this check speeds up the conversion process. Use this pick just if you are certain that no duplicate IP addresses be, such as when the original host is not agile.
The answers to the sysid questions are used only for the duration of the upgrade procedure. This data is not applied to the existing Bone image on disk. The fastest and simplest manner to run the conversion is to select Non-networked. The root password that you specify does not need to match the root password of the source system. The arrangement'southward original identity is preserved by the upgrade and takes effect after the post-upgrade reboot. The time required to perform the upgrade depends on the Oracle Solaris Cluster that is installed on the original system.
# ldmp2v convert -i /tank/iso/s10s_u5.iso -d /dwelling/dana/p2v/volumia volumia Testing original arrangement status ... LDom volumia started Waiting for Solaris to come up ... Select 'Upgrade' (F2) when prompted for the installation type. Disconnect from the console after the Upgrade has finished. Trying 0.0.0.0... Connected to 0. Escape graphic symbol is '^]'. Connecting to console "volumia" in group "volumia" .... Press ~? for control options .. Configuring devices. Using RPC Bootparams for network configuration information. Attempting to configure interface vnet0... Extracting windowing system. Please look... Get-go system identification... Searching for configuration file(s)... Search complete. Discovering additional network configuration... Configured interface vnet0 Setting up Java. Please wait... Select a Linguistic communication 0. English 1. French 2. German 3. Italian four. Japanese 5. Korean 6. Simplified Chinese seven. Castilian 8. Swedish 9. Traditional Chinese Please make a choice (0 - 9), or press h or ? for help: [...] - Solaris Interactive Installation -------------------------------------------- This organisation is upgradable, so in that location are two means to install the Solaris software. The Upgrade choice updates the Solaris software to the new release, saving as many modifications to the previous version of Solaris software equally possible. Back upwardly the system before using the Upgrade option. The Initial selection overwrites the organisation disks with the new version of Solaris software. This option allows you to preserve whatever existing file systems. Dorsum up whatever modifications made to the previous version of Solaris software before starting the Initial option. After you select an option and complete the tasks that follow, a summary of your deportment volition be displayed. ------------------------------------------------------------------------------- F2_Upgrade F3_Go Back F4_Initial F5_Exit F6_Help
The following examples show how y'all might use the ldmp2v catechumen command.
  |
Source: https://docs.oracle.com/cd/E38405_01/html/E38406/p2vexamples.html
0 Response to "Close All Files on the Archive or Virtual Disk"
Post a Comment