snapshot location

[alex77t]

Hi,

how can see where volume snapshots are stored for full machine backups?
I have a job that i stopped but want to make sure that local volume snapshot files are eventually removed.

thanks,
Alex

[PTide]

Hi,

If you grep these logs you can see where exactly the snapshot was placed:

Code: Select all

cat /var/log/veeam/Backup/<jobname/Session_<date>_<ID>/Job.log | grep veeamsnap

For example, I got this:

Code: Select all

[22.07.2019 20:08:58] <140207482177280> lpbcore|       Snapshot host device: 253:0, path on device: veeamsnapstore.{4601de08-b9ce-488d-98b7-c8184d251407}, fsuuid: 148345db-92ab-4f5b-b062-b3e1a48b1df8

I checked lsblk and it turns out that 253:0 is my root LV:

Code: Select all

[root@dhcp ~]# lsblk
NAME            MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
fd0               2:0    1    4K  0 disk
sda               8:0    0   16G  0 disk
├─sda1            8:1    0    1G  0 part
└─sda2            8:2    0   15G  0 part
  ├─centos-root 253:0    0 13.4G  0 lvm  /
  └─centos-swap 253:1    0  1.6G  0 lvm  [SWAP]
sdb               8:16   0   16G  0 disk
└─centos-lvol0  253:2    0   10G  0 lvm  [SWAP]
sr0              11:0    1 1024M  0 rom

To check FSUUID use lsblk with -f:

Code: Select all

[root@dhcp ~]# lsblk -f
NAME            FSTYPE      LABEL UUID                                   MOUNTPOINT
fd0
sda
├─sda1          xfs               faa73925-50b5-439d-8d11-1c1241751d95
└─sda2          LVM2_member       ZsKXjr-2inR-foEd-7W3A-zwRn-dakz-nHVgDL
  ├─centos-root xfs               148345db-92ab-4f5b-b062-b3e1a48b1df8   /

Thanks!

[alex77t]

thanks a lot for your prompt response, P.Tide

i've got these in the logs

Code: Select all

[28.07.2019 23:20:25] <139794349172480> lpbcore|       Snapshot host device: 9:3, path on device: /veeamsnapstore.{8ee2cb40-02d2-40ba-91c6-7e177e627eaa}, fsuuid: ad49559f-422f-44f4-a8d7-6b0ca7d09174
[28.07.2019 23:20:27] <139794349172480> vsnap  |       Try to cleanup old veeamsnap logs
[28.07.2019 23:20:28] <139794349172480> lpbcore|       Removing snapstore [/tmp/{76c7e250-123d-48e6-963f-01efe6ee16fb}/veeamsnapstore.{8ee2cb40-02d2-40ba-91c6-7e177e627eaa}] from snapshot

and it looks like it was trying to snaphot /home partition, and also tried to allocate 1.7Tb for the snapshot on the same partition in /home/veeamsnapstore.{8ee2cb40-02d2-40ba-91c6-7e177e627eaa}  ? 
[28.07.2019 23:20:18] <139794349172480> lpbcore|   Taking snapshot.
[28.07.2019 23:20:18] <139794349172480> lpbcore|     Requesting snapshot for device md3 [9:3].
[28.07.2019 23:20:18] <139794349172480> lpbcore|     Requesting snapshot for device sdb5 [8:21].
[28.07.2019 23:20:18] <139794349172480> lpbcore|     Device md0 [9:0] contains swap and will be excluded from snapshot.
[28.07.2019 23:20:18] <139794349172480> lpbcore|     Requesting snapshot for device sda5 [8:5].
[28.07.2019 23:20:18] <139794349172480> lpbcore|     Requesting snapshot for device md1 [9:1].
[28.07.2019 23:20:18] <139794349172480> lpbcore|     Requesting snapshot for device md2 [9:2].

so instead of doing full machine image, how would i back it up in this case ? Would it be possible to assign a different path to the snapshot? OR run it without creating a snapshot?

sudo lsblk -f

Code: Select all

NAME    FSTYPE            LABEL    UUID                                 MOUNTPOINT
sda
|-sda1  linux_raid_member rescue:0 420e59c3-4b5d-2ec0-a095-6ebfe451b42b
| `-md0 swap                       17524531-9440-4ff8-80dd-c6ef35379e3f [SWAP]
|-sda2  linux_raid_member rescue:1 439be26d-bdc8-f67a-fcd2-1aad72980bc1
| `-md1 ext3                       2510617e-078c-4d9e-a3a9-998a8dfd571c /boot
|-sda3  linux_raid_member rescue:2 961818fd-c7fe-c6ea-0430-ed30eb5333d1
| `-md2 ext4                       ff1e5a04-1c17-43a7-ab4d-eae3e3f17676 /
|-sda4  linux_raid_member rescue:3 95b2d36e-fca9-8c25-c23a-0f8a6ccfdeea
| `-md3 ext4                       ad49559f-422f-44f4-a8d7-6b0ca7d09174 /home
`-sda5
sdb
|-sdb1  linux_raid_member rescue:0 420e59c3-4b5d-2ec0-a095-6ebfe451b42b
| `-md0 swap                       17524531-9440-4ff8-80dd-c6ef35379e3f [SWAP]
|-sdb2  linux_raid_member rescue:1 439be26d-bdc8-f67a-fcd2-1aad72980bc1
| `-md1 ext3                       2510617e-078c-4d9e-a3a9-998a8dfd571c /boot
|-sdb3  linux_raid_member rescue:2 961818fd-c7fe-c6ea-0430-ed30eb5333d1
| `-md2 ext4                       ff1e5a04-1c17-43a7-ab4d-eae3e3f17676 /
|-sdb4  linux_raid_member rescue:3 95b2d36e-fca9-8c25-c23a-0f8a6ccfdeea
| `-md3 ext4                       ad49559f-422f-44f4-a8d7-6b0ca7d09174 /home
`-sdb5
loop0   ext3                       1223fd72-e41d-440b-99cc-c7c4edda890e /var/tmp

[PTide]

In your case the snapshot has been placed on /home partition. If you see any snapstore remnants there, then you should contact our support team.

If you want to specify snapshot location manually, you need to set location=/path/to/directory in /etc/veeam/veeam.ini file under [snapshot] section and reload veeamservice.

Thanks!