InfoScale™ 9.0 Solutions Guide - Linux
- Section I. Introducing Veritas InfoScale
- Section II. Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- Solutions for Veritas InfoScale products
- Section III. Stack-level migration to IPv6 or dual stack
- Section IV. Improving database performance
- Overview of database accelerators
- Improving database performance with Veritas Concurrent I/O
- Improving database performance with atomic write I/O
- Section V. Using point-in-time copies
- Understanding point-in-time copy methods
- Backing up and recovering
- Preserving multiple point-in-time copies
- Online database backups
- Backing up on an off-host cluster file system
- Database recovery using Storage Checkpoints
- Backing up and recovering in a NetBackup environment
- Off-host processing
- Creating and refreshing test environments
- Creating point-in-time copies of files
- Section VI. Maximizing storage utilization
- Optimizing storage tiering with SmartTier
- Optimizing storage with Flexible Storage Sharing
- Optimizing storage tiering with SmartTier
- Section VII. Migrating data
- Understanding data migration
- Offline migration from LVM to VxVM
- Offline conversion of native file system to VxFS
- Online migration of a native file system to the VxFS file system
- Migrating a source file system to the VxFS file system over NFS v4
- VxFS features not available during online migration
- Migrating storage arrays
- Migrating data between platforms
- Overview of the Cross-Platform Data Sharing (CDS) feature
- CDS disk format and disk groups
- Setting up your system to use Cross-platform Data Sharing (CDS)
- Maintaining your system
- Disk tasks
- Disk group tasks
- Displaying information
- File system considerations
- Specifying the migration target
- Using the fscdsadm command
- Maintaining the list of target operating systems
- Migrating a file system on an ongoing basis
- Converting the byte order of a file system
- Migrating from Oracle ASM to Veritas File System
- Section VIII. Veritas InfoScale 4K sector device support solution
- Section IX. REST API support
- Support for configurations and operations using REST APIs
- Support for configurations and operations using REST APIs
- Section X. Reference
Converting unused LVM physical volumes to VxVM disks
LVM disks or disk partitions that are not part of any volume group, and which contain no user data, can be converted by removing the LVM disk headers.
Warning:
Make sure that the disks to be converted are not in use in any LVM configuration. Any user data on these disks is destroyed during conversion.
To convert unused LVM physical volumes to VxVM disks
- Use the pvscan command to make sure that the disk is not part of any volume group as shown in this example:
# pvscan pvscan -- reading all physical volumes (this may take a while...) pvscan -- inactive PV "/dev/sde1" is in no VG [8.48 GB] pvscan -- ACTIVE PV "/dev/sdf" of VG "vg02" [8.47 GB / 8.47 GB free] pvscan -- inactive PV "/dev/sdg" is in no VG [8.48 GB] pvscan -- ACTIVE PV "/dev/sdh1" of VG "vg02" [8.47 GB / 8.47 GB free] pvscan -- total: 4 [33.92 GB] / in use: 2 [16.96 GB] / in no VG: 2 [16.96 GB]
This shows that the disk devices sdf and sdh1 are associated with volume group, vg02, but sde1 and sdg are not in any volume group.
- Use the following commands to remove LVM header information from each disk:
# dd if=/dev/zero of=/dev/diskdev bs=1k count=3 # blockdev --rereadpt /dev/diskdev
Warning:
When running dd on a disk partition, make sure that you specify the device for the disk partition rather than the disk name. Otherwise, you will overwrite information for other partitions on the disk.
- After overwriting the LVM header, use the fdisk or sfdisk command to edit the partition table on the disk:
# fdisk -l /dev/diskdev
If the LVM disk was created on an entire disk, relabel it as a DOS or SUN partition.
If the LVM disk was created on a disk partition, change the partition type from "Linux LVM" to "Linux".
- After writing the partition table to the disk, a disk or disk partition (where there is no other useful partition on the disk) may be initialized as a VM disk by running the vxdiskadm command and selecting item 1 Add or initialize one or more disks, or by using the VEA GUI. For a disk partition that coexists with other partitions on a disk, initialize the partition as a simple disk.