Veritas Access Troubleshooting Guide

Last Published:
Product(s): Access (7.4.2)
Platform: Linux
  1. Introduction
    1.  
      About troubleshooting
    2.  
      General tips for the troubleshooting process
    3.  
      General techniques for the troubleshooting process
    4.  
      About the support user account
    5.  
      Configuring the support user account
    6.  
      Using the support login
  2. General troubleshooting procedures
    1.  
      About general troubleshooting procedures
    2.  
      Viewing the Veritas Access log files
    3.  
      About event logs
    4.  
      About shell-activity logs
    5.  
      Setting the CIFS log level
    6.  
      Setting the NetBackup client log levels and debugging options
    7.  
      Retrieving and sending debugging information
    8.  
      Insufficient delay between two successive OpenStack commands may result in failure
  3. Monitoring Veritas Access
    1.  
      About monitoring Veritas Access operations
    2.  
      Monitoring processor activity
    3.  
      Generating CPU and device utilization reports
    4.  
      Monitoring network traffic
    5.  
      Exporting and displaying the network traffic details
  4. Common recovery procedures
    1.  
      About common recovery procedures
    2.  
      Restarting servers
    3. Bringing services online
      1.  
        Using the services command
    4.  
      Recovering from a non-graceful shutdown
    5.  
      Testing the network connectivity
    6.  
      Troubleshooting with traceroute
    7.  
      Using the traceroute command
    8.  
      Collecting the metasave image of a file system
    9.  
      Replacing an Ethernet interface card (online mode)
    10.  
      Replacing an Ethernet interface card (offline mode)
    11.  
      Replacing a Veritas Access node
    12.  
      Replacing a disk
    13. Speeding up replication
      1.  
        About synchronizing a replication job
      2.  
        Synchronizing an episodic replication job
    14.  
      Uninstalling a patch release or software upgrade
  5. Troubleshooting the Veritas Access cloud as a tier feature
    1.  
      Troubleshooting tips for cloud tiering
    2.  
      Issues when reading or writing data from the cloud tier
    3.  
      Log locations for checking for cloud tiering errors
  6. Troubleshooting Veritas Access installation and configuration issues
    1.  
      How to find the management console IP
    2.  
      Viewing the installation logs
    3.  
      Installation fails and does not complete
    4.  
      Excluding PCI IDs from the cluster
    5.  
      Cannot recover from root file system corruption
    6.  
      The storage disk list command returns nothing
  7. Troubleshooting the LTR upgrade
    1.  
      Locating the log files for troubleshooting the LTR upgrade
    2.  
      Troubleshooting pre-upgrade issues for LTR
    3.  
      Troubleshooting post-upgrade issues for LTR
  8. Troubleshooting Veritas Access CIFS issues
    1.  
      User access is denied on a CTDB directory share
  9. Troubleshooting Veritas Access GUI startup issues
    1.  
      Resolving GUI startup issues
  10.  
    Index

Replacing a disk

In some cases, you may need to replace an existing disk. This section describes the steps for replacing a disk.

Note:

You can replace a disk in a storage pool from a master or a subordinate node. From a Cluster Volume Manager (CVM) master node, you can replace DAS and SAN disks. From a subordinate node, you can replace only DAS disks.

To replace a disk

  1. Remove the disk that needs to be replaced from the array side.
  2. Add the new disk to the system from the array side.
  3. Run the following command on all the nodes in the cluster to eliminate the old disk from the Veritas Volume Manager (VxVM) view.
    #vxdisk rm <old-disk-name>
  4. Run the following command on the node for which you want to replace the disk.
    # vxdisk scandisks
  5. Initialize the new disk that has been added to the cluster by using the vxdisksetup command.
    #/etc/vx/bin/vxdisksetup  - fi <new-disk-name>
  6. Apply the tag to the newly added device that is similar to the Veritas Access pool name on the node where the failed disk resides.
    # vxdisk settag site=<pool-name> <new-disk-name>
  7. Run the vxdiskadm command and choose option #5 to replace a failed disk with a new disk on the node where the failed disk resides.
    #vxdiskadm

    Note:

    If the disk replacement is triggered from a subordinate node, the vxrecover command fails.

  8. If the disk replacement is triggered from a subordinate node, run the following command from the slave node for all the affected volumes.
    #vxrecover  - b  - c  - s <vol-name>
  9. Rename the newly added disk to the disk access name.
    #vxedit  - g <dg-name> rename <old-disk-name> <new-disk-name>
  10. Rename the subdisks as per the newly added disk name.
    #vxedit  - g <dg-name> rename <old-subdisk-name> <new-subdisk-name>

Example: Disk replacement from a CVM master node

This example describes the procedure for replacing the emc0_2255 disk with emc0_2263 disk. The emc0_2263 disk has been excluded and it is added later to simulate the disk addition.

Replacing a disk from a CVM master node

  1. Run the vxdmpadm exclude command to remove the emc0_2255 disk.
    # vxdmpadm exclude dmpnodename=emc0_2255
  2. Run the the vxdmpadm include command to include the emc0_2263 disk.
    # vxdmpadm include dmpnodename=emc0_2263

    Note:

    You can run the vxdisk scandisks command to scan the disks.

  3. Run the settag command to apply the tag to the underlying disk.
    # vxdisk settag emc0_2263 tag=pool1
  4. Run the vxdiskadm command and choose option #5 to replace the failed disk.
    [root@fss7310_01 ~]# vxdiskadm
    Volume Manager Support Operations
    Menu:: VolumeManager/Disk
    1 Add or initialize one or more disks
    2 Encapsulate one or more disks
    3 Remove a disk
    4 Remove a disk for replacement 5 Replace a failed or removed disk
    6 Mirror volumes on a disk
    7 Move volumes from a disk
    8 Enable access to (import) a disk group
    9 Remove access to (deport) a disk group
    10 Enable (online) a disk device
    11 Disable (offline) a disk device
    12 Mark a disk as a spare for a disk group
    13 Turn off the spare flag on a disk
    14 Unrelocate subdisks back to a disk
    15 Exclude a disk from hot-relocation use
    16 Make a disk available for hot-relocation use
    17 Prevent multipathing/Suppress devices from VxVM's view
    18 Allow multipathing/Unsuppress devices from VxVM's view
    19 List currently suppressed/non-multipathed devices
    20 Change the disk naming scheme
    21 Change/Display the default disk layouts
    22 Dynamic Reconfiguration Operations
    list List disk information
    
    Select an operation to perform: 5
    
    Replace a failed or removed disk
    Menu:: VolumeManager/Disk/ReplaceDisk
    
    Use this menu operation to specify a replacement disk for a disk
    that you removed with the "Remove a disk for replacement" menu
    operation, or that failed during use. You will be prompted for
    a disk name to replace and a disk device to use as a replacement.
    You can choose an uninitialized disk, in which case the disk will
    be initialized, or you can choose a disk that you have already
    initialized using the Add or initialize a disk menu operation.
    
    Select a removed or failed disk [<disk>,list,q,?] list
    Disk group: sfsdg
    DM NAME DEVICE TYPE PRIVLEN PUBLEN STATE
    dm emc0_2255 - - - - NODEVICE
    
    Select a removed or failed disk [<disk>,list,q,?] emc0_2255
    
    The following devices are available as replacements:
    emc0_2263
    You can choose one of these devices to replace emc0_2255. 
    Choose "none" to initialize another device to replace emc0_2255.
    Choose a device, or select "none" [<device>,none,q,?] 
    (default: emc0_2263) emc0_2263
    VxVM INFO V-5-2-382
    The requested operation is to use the initialized device emc0_2263
    to replace the removed or failed disk emc0_2255 in disk group sfsdg.
    Continue with operation? [y,n,q,?] (default: y) y
    Use FMR for plex resync? [y,n,q,?] (default: n)
    VxVM INFO V-5-2-282 Replacement of disk emc0_2255 in group 
    sfsdg with disk device emc0_2263 completed successfully.
    Replace another disk? [y,n,q,?] (default: n)
  5. Rename the disk as per the disk access name to avoid the vxdg issue.
    # vxedit -g sfsdg rename emc0_2255 emc0_2263
    
    # vxdisk list | grep emc0_2263 emc0_2263 auto:cdsdisk emc0_2263 
    sfsdg online shared
  6. Rename the subdisks as per disk access name.
    # vxedit -g sfsdg rename emc0_2255-03 emc0_2263-03
    # vxedit -g sfsdg rename emc0_2255-02 emc0_2263-02
    
    [root@fss7310_01 ~]# vxprint -pvs | grep -i 2263
    sd emc0_2263-02 vol1-P01 ENABLED 699136 0 - - -
    sd emc0_2263-03 vol1_dcl-01 ENABLED 67840 0 - - -
    [root@fss7310_01 ~]# vxprint -pvs | grep -i 2255
    [root@fss7310_01 ~]#

Example: Disk replacement from a subordinate node

This example describes the procedure for replacing the emc0_2273 disk with emc0_2305 disk. The emc0_2263 disk has been excluded and it is added later to simulate the disk addition.

To replace a disk from a subordinate node

  1. Run the vxdmpadm exclude command to remove the emc0_2273 disk.
    # vxdmpadm exclude dmpnodename=emc0_2273
  2. Run the vxdmpadm include command to include the emc0_2305 disk.
    # vxdmpadm include dmpnodename=emc0_2305

    Note:

    You can run the vxdisk scandisks command to scan the disks.

  3. Run the vxdisk rm command from the remaining nodes in the cluster:
    [root@fss7310_02 ~]# vxdisk rm emc0_2273
    [root@fss7310_01 ~]# vxdisk rm emc0_2273

    Note:

    If you encounter an error, wait for a few minutes and run the command again.

  4. Run the settag command to apply the tags to the underlying disk:
    # vxdisk settag emc0_2305 tag=pool1
  5. Run the vxdiskadm command and choose option #5 to replace the failed disk.
    [root@fss7310_01 ~]# vxdiskadm
    
    Volume Manager Support Operations
    Menu:: VolumeManager/Disk
    
    1 Add or initialize one or more disks
    2 Encapsulate one or more disks
    3 Remove a disk
    4 Remove a disk for replacement 5 Replace a failed or removed disk
    6 Mirror volumes on a disk
    7 Move volumes from a disk
    8 Enable access to (import) a disk group
    9 Remove access to (deport) a disk group
    10 Enable (online) a disk device
    11 Disable (offline) a disk device
    12 Mark a disk as a spare for a disk group
    13 Turn off the spare flag on a disk
    14 Unrelocate subdisks back to a disk
    15 Exclude a disk from hot-relocation use
    16 Make a disk available for hot-relocation use
    17 Prevent multipathing/Suppress devices from VxVM's view
    18 Allow multipathing/Unsuppress devices from VxVM's view
    19 List currently suppressed/non-multipathed devices
    20 Change the disk naming scheme
    21 Change/Display the default disk layouts
    22 Dynamic Reconfiguration Operations
    list List disk information
    
    ? Display help about menu
    ?? Display help about the menuing system
    q Exit from menus
    
    Select an operation to perform: 5
    Replace a failed or removed disk
    
    Menu:: VolumeManager/Disk/ReplaceDisk
    Use this menu operation to specify a replacement disk for a disk
    that you removed with the "Remove a disk for replacement" menu
    operation, or that failed during use. You will be prompted for
    a disk name to replace and a disk device to use as a replacement.
    You can choose an uninitialized disk, in which case the disk will
    be initialized, or you can choose a disk that you have already
    initialized using the Add or initialize a disk menu operation.
    Select a removed or failed disk [<disk>,list,q,?] list
    Disk group: sfsdg
    
    DM NAME      DEVICE TYPE PRIVLEN PUBLEN STATE
    dm emc0_2273 -      -    -       -      NODEVICE
    
    Select a removed or failed disk [<disk>,list,q,?] emc0_2273
    The following devices are available as replacements:
    emc0_2305
    You can choose one of these devices to replace emc0_2255. Choose 
    "none" to initialize another device to replace emc0_2255.
    Choose a device, or select "none" [<device>,none,q,?] 
    (default: emc0_2305) emc0_2305
    VxVM INFO V-5-2-382
    The requested operation is to use the initialized device emc0_2305
    to replace the removed or failed disk emc0_2273 in disk group sfsdg.
    
    Continue with operation? [y,n,q,?] (default: y)
    Use FMR for plex resync? [y,n,q,?] (default: n) VxVM vxrecover 
    ERROR V-5-1-16084 Disk group: sfsdg is shared. The command can be 
    executed only on the CVM master. Use -c option to recover all the shared 
    disk groups from slaves.
    VxVM INFO V-5-2-282 Replacement of disk emc0_2273 in group sfsdg 
    with disk device emc0_2305 completed successfully.
    Replace another disk? [y,n,q,?] (default: n)
  6. Run the following command to trigger a recovery for the affected volumes.
    # vxrecover -b -c -s vol1
  7. Rename the disk to the disk access name to avoid the vxdg issue.
    # vxedit -g sfsdg rename emc0_2273 emc0_2305
    
    # vxdisk list | grep emc0_2305
    emc0_2305 auto:cdsdisk emc0_2305 sfsdg online shared
  8. Rename the subdisks as per the naming convention that is followed for the newly added disk.
    # vxedit -g sfsdg rename emc0_2273-02 emc0_2305-02
    # vxedit -g sfsdg rename emc0_2273-03 emc0_2305-03
    
    # vxprint -pvs | grep -i emc0_2305
    sd emc0_2305-02 vol1-P02 ENABLED 699136 0 - - -
    sd emc0_2305-03 vol1_dcl-02 ENABLED 67840 0 - - -
    # vxprint -pvs | grep -i emc0_2273