Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
Post Reply
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

No suitable devices for snapshot data storage were found

Post by pmepereira »

Hi guys,

Trying Veeam Agent for Linux on a Fedora 14.

I get an error after 5 or 6 seconds of starting the job:

Code: Select all

[26.07.2016 11:06:24] <140219458246400> lpbcore| ERR |No suitable devices for snapshot data storage were found.
[26.07.2016 11:06:24] <140219458246400> lpbcore| >>  |--tr:Failed to create machine snapshot.
[26.07.2016 11:06:24] <140219458246400> lpbcore| >>  |--tr:Unable to create snapshot for session [{6bb67868-cdec-42ab-966f-9769e9ae14ff}].
[26.07.2016 11:06:24] <140219458246400> lpbcore| >>  |--tr:Failed to execute method [0] for class [N10lpbcorelib11interaction9proxystub21CResourcesServiceStubE].
[26.07.2016 11:06:24] <140219458246400> lpbcore| >>  |An exception was thrown from thread [1660933888].
Some info on the volumes i'm trying to backup:

Code: Select all

# cat /proc/mdstat
Personalities : [raid1] 
md2 : active raid1 sda3[0] sdb3[1]
      102398908 blocks super 1.1 [2/2] [UU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

md1 : active raid1 sda2[0] sdb2[1]
      82207676 blocks super 1.1 [2/2] [UU]
      bitmap: 0/1 pages [0KB], 65536KB chunk

md0 : active raid1 sda1[0] sdb1[1]
      51199928 blocks super 1.0 [2/2] [UU]
      bitmap: 1/1 pages [4KB], 65536KB chunk

unused devices: <none>
Link for /var/log/veeam tarball
https://drive.google.com/file/d/0B1mCHa ... sp=sharing
Top
PTide
Product Manager
Posts: 6551
Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Contact PTide

Re: No suitable devices for snapshot data storage were found

Post by PTide »

Could you please describe the dataset that you are trying to backup (Entire machine, volumes, files?) as well as the backup destination? Also please provide outputs of dmesg -T and lsblk -af

Thanks
Top
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

Re: No suitable devices for snapshot data storage were found

Post by pmepereira »

Sorry for the delay.

I tried backing up the entire machine, as well as just some volumes. I think I also tried just some files, but I can't be sure.
Backup destination is a cifs share, mounted manually on other servers, so the actual share and user/pass credentials are ok and working.

Code: Select all

# dmesg -T
dmesg: invalid option -- 'T'
Usage: dmesg [-c] [-n level] [-r] [-s bufsize]
Did "dmesg" only, output here:
https://drive.google.com/open?id=0B1mCH ... zczNUFKWnM

lsblk no found. I've tried:

Code: Select all

# lsblk
bash: lsblk: command not found...

# yum install lsblk
(...)
No package lsblk available.
Error: Nothing to do

# yum install util-linux-ng
Package util-linux-ng-2.18-4.8.fc14.x86_64 already installed and latest version
Nothing to do
Top
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

Re: No suitable devices for snapshot data storage were found

Post by pmepereira »

I've also tried reinstalling both veeamsnap and veeam RPMs.

EDIT: Exact same result on a Fedora 17 (had to install dkms and lvm2 packages as they were not on the system).

Code: Select all

# uname -a
Linux server.domain 3.5.1-1.fc17.x86_64 #1 SMP Thu Aug 9 17:50:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
Top
nielsengelen
Product Manager
Posts: 5797
Liked: 1215 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:
Contact nielsengelen

Re: No suitable devices for snapshot data storage were found

Post by nielsengelen »

Could you also post the Veeam logs found under /var/log.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
Top
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

Re: No suitable devices for snapshot data storage were found

Post by pmepereira »

On the 1st post (Google Drive link)
Top
PTide
Product Manager
Posts: 6551
Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Contact PTide

Re: No suitable devices for snapshot data storage were found

Post by PTide »

Hi,

Does the error occur every time you try run backup job? Please describe the system that you're backing up, is it physical or virtual? If the latter then please describe what is the hypervisor and machine settings are.

Thanks!
Top
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

Re: No suitable devices for snapshot data storage were found

Post by pmepereira »

Yes, every time.

The source is physical, and the target CIFS is also on a physical machine with Windows Server 2008 R2.
Top
PTide
Product Manager
Posts: 6551
Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Contact PTide

Re: No suitable devices for snapshot data storage were found

Post by PTide »

What disks do you have in the systems (Fedora 17)? You should have lsblk available in Fedora 17 as it was added on version 2.19 of util-linux. Please provide its output.

Thanks
Top
nielsengelen
Product Manager
Posts: 5797
Liked: 1215 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:
Contact nielsengelen

Re: No suitable devices for snapshot data storage were found

Post by nielsengelen »

Could you also post a df -h output?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
Top
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

Re: No suitable devices for snapshot data storage were found

Post by pmepereira »

The original test system is Fedora 14, so no lsblk.

I'll provide info on the second test server running Fedora 17 (actual server name and domain replaced with "server.domain"):

Code: Select all

$ df -h
Filesystem                               Size  Used Avail Use% Mounted on
rootfs                                    63G   22G   39G  36% /
devtmpfs                                  16G  8,0K   16G   1% /dev
tmpfs                                     16G     0   16G   0% /dev/shm
tmpfs                                     16G  1,6G   15G  10% /run
/dev/md0                                  63G   22G   39G  36% /
tmpfs                                     16G     0   16G   0% /sys/fs/cgroup
tmpfs                                     16G     0   16G   0% /media
/dev/md1                                 1,8T   11G  1,7T   1% /var
//server.domain/share                     14T  3,3T   11T  25% /mnt/backups

Code: Select all

$ lsblk -af
NAME    FSTYPE            LABEL              UUID                                 MOUNTPOINT
sda                                                                               
├─sda1  linux_raid_member server.domain:0 cc52d611-9766-0b15-c95a-ccfbf18bad37 
│ └─md0 ext4                                 2743a42b-7fb6-424f-ab20-c914a9364952 /
└─sda2  linux_raid_member server.domain:1 25734c6d-ae5c-2953-b277-3d588e254b45 
  └─md1 ext4                                 bb7f975f-cb0d-4d93-a0a0-da2eeca19dc3 /var
sdb                                                                               
├─sdb1  linux_raid_member server.domain:0 cc52d611-9766-0b15-c95a-ccfbf18bad37 
│ └─md0 ext4                                 2743a42b-7fb6-424f-ab20-c914a9364952 /
└─sdb2  linux_raid_member server.domain:1 25734c6d-ae5c-2953-b277-3d588e254b45 
  └─md1 ext4                                 bb7f975f-cb0d-4d93-a0a0-da2eeca19dc3 /var
sdc                                                                               
└─sdc1  swap                                 1de9d0d9-dba1-4b0f-87c8-c4ac7be0a46e [SWAP]
sr0                                                                               
loop0                                                                             
loop1                                                                             
loop2                                                                             
loop3                                                                             
loop4                                                                             
loop5                                                                             
loop6                                                                             
loop7
Top
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

Re: No suitable devices for snapshot data storage were found

Post by pmepereira » 1 person likes this post

As requested, logs from Fedora 17.
https://drive.google.com/file/d/0B1mCHa ... sp=sharing
Top
nielsengelen
Product Manager
Posts: 5797
Liked: 1215 times
Joined: Jul 15, 2013 11:09 am
Full Name: Niels Engelen
Contact:
Contact nielsengelen

Re: No suitable devices for snapshot data storage were found

Post by nielsengelen »

Is this hardware raid underneath and if so which controller is used for it?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
Top
PTide
Product Manager
Posts: 6551
Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Contact PTide

Re: No suitable devices for snapshot data storage were found

Post by PTide »

It's not a hardware raid - it's just linux sf raid built by mdadm

Pedro,
sorry for confusion but I need to ask you for dmesg output from Fedora 17 host as the previous one that you've sent me turned out to be from 14.

Thank you
Top
pmepereira
Novice
Posts: 8
Liked: 1 time
Joined: Jul 26, 2016 10:31 am
Full Name: Pedro Pereira
Contact:
Contact pmepereira

Re: No suitable devices for snapshot data storage were found

Post by pmepereira »

I ran

Code: Select all

dmesg -C
On Fedora 17, then ran the failing Veeam job, and then I ran

Code: Select all

dmesg -T
The result:

Code: Select all

[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ctrl_unlocked_ioctl IOCTL_TRACKING_COLLECT
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ioctl_tracking_collect Collecting tracking device:
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect dev_id=8:1
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect snap_number=0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect cbt_map_size=262144
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect dev_id=8:17
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect snap_number=0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect cbt_map_size=262144
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect dev_id=9:0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect snap_number=0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect cbt_map_size=262144
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect dev_id=9:1
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect snap_number=0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_collect cbt_map_size=7368764
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ctrl_unlocked_ioctl IOCTL_TRACKING_REMOVE
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ioctl_tracking_remove Removing from tracking device:
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ioctl_tracking_remove major=9
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ioctl_tracking_remove minor=0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_remove Removing. dev_id=9:0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Remove .
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove .
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove freezing
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove freezed
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker_queue.c:tracker_queue_Unref Tracker queue freed. pTrQ=0xffff88010d0ac0c0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove thawed
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove Unref device dev_id=9:0
[Qua Ago 17 02:12:36 2016]     veeamsnap:cbt_map.c:cbt_map_destroy CBT map destroy.
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ctrl_unlocked_ioctl IOCTL_TRACKING_REMOVE
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ioctl_tracking_remove Removing from tracking device:
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ioctl_tracking_remove major=9
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ioctl_tracking_remove minor=1
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_remove Removing. dev_id=9:1
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Remove .
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove .
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove freezing
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove freezed
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker_queue.c:tracker_queue_Unref Tracker queue freed. pTrQ=0xffff88010d0accc0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove thawed
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:__tracker_Remove Unref device dev_id=9:1
[Qua Ago 17 02:12:36 2016]     veeamsnap:cbt_map.c:cbt_map_destroy CBT map destroy.
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ctrl_unlocked_ioctl IOCTL_TRACKING_ADD
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_add Adding. dev_id=9:0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create .
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create dev_id 9:0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create bd_super=0xffff8807ef08b400
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create SectorStart    =0x0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create SectorsCapacity=0x7ffff70
[Qua Ago 17 02:12:36 2016]     veeamsnap:cbt_map.c:cbt_map_create CBT map create.
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create freezed
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker_queue.c:tracker_queue_Ref Creating tracker_queue for queue=0xffff8807efafbd40
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker_queue.c:tracker_queue_Ref Tracker queue created. pTrQ=0xffff88066a20e600
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create thawed.
[Qua Ago 17 02:12:36 2016]     veeamsnap:ctrl_fops.c:ctrl_unlocked_ioctl IOCTL_TRACKING_ADD
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracking.c:tracking_add Adding. dev_id=9:1
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create .
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create dev_id 9:1
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create bd_super=0xffff8807f29ea400
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create SectorStart    =0x0
[Qua Ago 17 02:12:36 2016]     veeamsnap:tracker.c:tracker_Create SectorsCapacity=0xe0e076f0
[Qua Ago 17 02:12:36 2016]     veeamsnap:cbt_map.c:cbt_map_create CBT map create.
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracker.c:tracker_Create freezed
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracker_queue.c:tracker_queue_Ref Creating tracker_queue for queue=0xffff8807efafc4e8
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracker_queue.c:tracker_queue_Ref Tracker queue created. pTrQ=0xffff88066a20e300
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracker.c:tracker_Create thawed.
[Qua Ago 17 02:12:37 2016]     veeamsnap:ctrl_fops.c:ctrl_unlocked_ioctl IOCTL_TRACKING_ADD
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracking.c:tracking_add Adding. dev_id=8:1
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracking.c:tracking_add Device already tracking. Device=8:1
[Qua Ago 17 02:12:37 2016]     veeamsnap:ctrl_fops.c:ctrl_unlocked_ioctl IOCTL_TRACKING_ADD
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracking.c:tracking_add Adding. dev_id=8:17
[Qua Ago 17 02:12:37 2016]     veeamsnap:tracking.c:tracking_add Device already tracking. Device=8:17
Top
Post Reply

Return to “Veeam Agents for Linux, Mac, AIX & Solaris”



Who is online

Users browsing this forum: No registered users and 2 guests