Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Web UI Cloud Administrator's Guide
  3. Performing granular restore
  4. Performing steps after volume restore containing LVM
NetBackup™ Web UI Cloud Administrator's Guide

Performing steps after volume restore containing LVM

You can perform steps after volume restore for the LVM volumes.

Note:

SFR (Single File Restore) or GRT (Granule Restore) and application restore are performed through the installed agents. However, for volume recovery, it is necessary to make the associated file systems online after successful recovery.

To perform steps after volume restore

  1. Run the command to see all newly attached post volumes on to the host PV's.

    If there are duplicate PVs (a warning is displayed on the above command) then run,

    vgimportclone --import /dev/<Device1> /dev/<Device2> ... --basevgname <NewVGName>

    Otherwise, find out the newly created Volume Groups (VG) on the host. If new VGs are not displayed then import the VG using the following command. It discovers new VG as <NewVGName>

    vgimport -a

    vgs

  2. Run this command to list all the logical volumes (new and old):

    lvs <NewVGName>

  3. Activate all the LVs belonging to <NewVGName> as,

    lvchange --activate y /dev/mapper/<NewVGName>-<LVName1>

    lvchange --activate y /dev/mapper/<NewVGName>-<LVName2>

    lvchange --activate y /dev/mapper/<NewVGName>-<LVNameN>

  4. Identify the UUID and file system of an authenticated and newly activated LV.

    blkid -p /dev/mapper/<NewVGName>-<LVName1>

    Output: /dev/mapper/<NewVGName>-<LVName1>: 
    UUID="2a4bdc14-b5eb-4ee6-b876-ebdcb66c55d9" 
    BLOCK_SIZE="4096"TYPE="xfs" USAGE="filesystem"

    blkid -p /dev/mapper/<OldVGName>-<LVName1>

    Output: /dev/mapper/<OldVGName>-<LVName1>: 
    UUID="2a4bdc14-b5eb-4ee6-b876-ebdcb66c55d9" 
    BLOCK_SIZE="4096"TYPE="xfs" USAGE="filesystem"
  5. If the UUID is the same, then you need to change it as follows

    File System

    Steps

    xfs

    mkdir <NewMountPoint>

    mount -o nouuid /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>

    umount <NewMountPoint>

    xfs_admin -U generate /dev/mapper/<NewVGName>-<LVName1>

    mount /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>

    ext2 / ext3/ ext4

    mkdir<NewMountPoint>

    tune2fs -U random /dev/mapper/<NewVGName>-<LVName1>

    mount /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>

  6. If the UUID is different, then run the following command.

    mount /dev/mapper/<NewVGName>-<LVName1> <NewMountPoint>

Feedback

Was this page helpful?
Previous

Restoring volumes on cloud virtual machines

Next

Troubleshooting

Feedback

Was this page helpful?