#1 Global Leader in Data Resilience

Dell PowerPath - Veeam Agent for Linux Limitations

KB ID: 2771
Product: Veeam Agent for Linux | 3.0 | 4.0 | 5.0 | 6.0 | 6.1 | 6.2 | 6.3
Published: 2018-09-19
Last Modified: 2024-06-04
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Challenge

If a Linux server has Dell PowerPath devices attached, all the underlying block devices representing the network paths to the server are skipped from processing. This will result in the error "No objects to backup" or PowerPath devices missing from the backup. If non-PowerPath devices are part of the backup scope (i.e., the Entire Computer scope is selected), the backup will technically be green, but the PowerPath devices will be silently skipped.

Cause

Veeam Agent for Linux detects only the DM-Multipath-based devices as aggregated. Additionally, block devices with the same MBR/GPT ID cannot be backed up. Because of this, both individual paths and aggregated devices are considered different block devices and are skipped from processing.

Solution

All individual IO paths must be excluded using the ignoreDevices parameter within the /etc/veeam/veeam.ini configuration file.

The ignoreDevices parameter must be manually created under the [backup] section of the veeam.ini file.
 

Example
  1. Use the following command to list the Dell PowerPath aggregated device name and underlying devices:
    For more information about powermt and PowerPath CLI, please review: CLI and System Messages Reference
powermt display dev=all 

Example output

[root@localhost ~]# powermt display dev=all
 
Pseudo name=emcpowerea
Symmetrix ID=000343607604
Logical device ID=07BA
Device WWN=60000980000262604497023030364553
state=alive; policy=SymmOpt; queued-IOs=0
==============================================================================
--------------- Host ---------------   - Stor -  -- I/O Path --   -- Stats ---
###  HW Path               I/O Paths    Interf.  Mode     State   Q-IOs Errors
==============================================================================
   6 lpfc                   sdef       FA 10f:00 active   alive      0      0
   5 lpfc                   sdcm       FA  6f:00 active   alive      0      0
   4 lpfc                   sdau       FA  7f:00 active   alive      0      0
   3 lpfc                   sdb        FA 11f:00 active   alive      0      0

In this example, there are the following devices:

  • /dev/emcpowerea — aggregated Dell (formerly EMC) PowerPath device
  • /dev/sdef, /dev/sdcm, /dev/sdau, /dev/sdb — underlying block devices representing the network paths

Accordingly, the mount table lists /dev/emcpowerea device mounted under /data folder:

root@localhost:~# mount | grep emcpowerea
/dev/emcpowereap1 on /data type ext4 (rw,relatime,errors=remount-ro,stripe=256,data=ordered)
  1. From the example above, the following is a formatted list of individual IO paths for the /dev/emcpowerea block device:
    /dev/sdef;/dev/sdcm;/dev/sdau;/dev/sdb
    
  2. Specify those paths with the ignoreDevices parameter created under the [backup] section of the veeam.ini file. Use a semicolon without whitespace as a separator.

    Example:
    [backup]
    # Backup cluster alignment logarithm
    # clusteralign= 3
     
    # Ignore inactive LVM logical volumes during backup
    # ignoreinactivelvm= false
     
    # IO rate limit, from 0.01 to 1.0
    # ioratelimit= 0.9
     
    # CPU priority for veeamagents, from 0 to 19
    # priority= 10
      
    # Verbose logging of device enumeration
    # verbosedevenumlogging= false
     
    ignoreDevices= /dev/sdef;/dev/sdcm;/dev/sdau;/dev/sdb
    
  3. Save the veeam.ini file and ensure no backup or restore sessions are running on the Veeam Agent machine. If no backup or restore sessions are running, restart the veeamservice daemon to pick up the new values from the configuration file.
systemctl restart veeamservice
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.