Aix: Moving File system to a new Volume group

Step 1 Close the source LV
# umount /fs_on_rootvg

Step 2 Copy the source logical volume to the desired volume group.
# cplv -v new_vg lv_source
this will return the name of the new logicla volum, such as lv00

Step 3 JFS and JFS2 file systems require a log device.
run lsvg -l <vg_name> , if JFS or JFS2 log does not exist you have to create it.

To make a new JFS2 log, enter
# mklv -t jfs2log <vg_name> 1
This will return a new jfs2log volume, such as loblv00.
This new log volume will need to be formatted with the logform command .
# logform /dev/loglv00
Answer yes to destroy.

Step 4 change file system's lv and log device
# chfs -a dev=/dev/lv00 -a log=/dev/loblv00 /myfilessytem

Step 5 run fsck to ensure file system integrity.
# fsck -p /dev/lv00

Step 6 rmove the source logical volume
# rmlv lv_source

Comments

What You Must Know Before Establishing a Recovery Plan ?

In today's rapidly evolving digital landscape, organizations are increasingly adopting the zero trust model, primarily due to the expanding attack surface that leaves critical systems and data exposed. This shift is also fueled by the heightened sophistication of cyber-attacks, which have become more complex and harder to detect, surpassing traditional security measures. Additionally, the existing operating models within organizations are often inconsistent, typically characterized by distributed and siloed environments. This fragmentation creates vulnerabilities and makes it challenging to implement uniform security protocols. The zero trust model addresses these challenges by assuming that threats exist both inside and outside the network, necessitating continuous verification of all users and devices. Its adoption represents a proactive stance in the ongoing battle against cyber threats, ensuring a more robust and resilient organizational security posture. The Evolution ...

A comprehensive guide to ransomware distribution in VMware environments

In a virtualized on-premises environment based on VMware, ransomware distribution scenarios can be somewhat unique due to the nature of virtualization technology. However, many of the traditional attack vectors still apply. Here are some ransomware distribution scenarios specific to a VMware-based virtualized environment: Phishing Attacks Targeting Administrators: Administrators with access to the VMware environment might receive phishing emails. If they fall for these and their credentials are compromised, attackers can gain access to the virtualized environment. Exploiting Vulnerabilities in VMware Software: If VMware software or the underlying operating system is not kept up-to-date with security patches, vulnerabilities can be exploited by attackers to deliver ransomware into the virtualized environment. Compromised Remote Management Tools: Tools used for remote management of the virtualized environment, such as vSphere, can be a target. If these tools are compromised, attackers ca...

Edge Computing Demystified Book

After a while I'm back and pleased to share in this post my first book around Edge computing Technologies. Edge computing has been a very hot and interesting topic nowadays for communication service provider and Enterprise so far. Augmented Reality / Virtual Reality, Smart cities, Healthcare, industrial IoT and many others use cases require a change in the way we operate and host application in the cloud. IA, Big Data and analytics are often used today to understand the behavior of the customer and even the health of services. Real-time and high throughput demand are the characteristic of the new business services. Edge computing technology promises to resolve different challenges and brings compute, storage and bandwidth close to the data source. I tried in ‘the Edge Computing Demystified’ book to explain Edge computing technology referring to different use cases from communication service provider and enterprise industry. I h...

Peta Room

Search This Blog