Why is there a difference in the what the backup job shows for Linux agent 3.0 backup job for RHEL 7 compared to the backup copy job:
Agent shows this:
Backed up sysvg 1.9 GB at 46.7 MB/s
Backed up moodlevg 61.1 GB at 95.1 MB/s
Backed up pgsqlvg 106.5 GB at 256.3 MB/s
Backed up sdb 2 MB at 67.2 KB/s
Backed up sdc 11 MB at 1.4 MB/s
Backed up sda 2 MB at 209.6 KB/s
Backup copy shows this:
Hard disk 1 (107.5 GB) 904.0 MB read at 89 MB/s
Hard disk 2 (8.7 TB) 60.9 GB read at 50 MB/s
Hard disk 3 (445.8 GB) 106.4 GB read at 102 MB/s
Hard disk 4 (10.9 TB) 0.0 B read at 0 KB/s
Hard disk 5 (136.1 GB) 9.0 MB read at 9 MB/s
Hard disk 6 (557.3 GB) 0.0 B read at 0 KB/s
There are 6 in each list, but the backed up amounts don't line up (I'm assuming for the agent job the amount, 1.9 GB for example, is the incremental amount but there is no 1.9 GB in the BC job; however, 2 do match sorta: 60 GB and 106 GB for each job) and they are called by different names. Additionally, there are only 3 disks defined:
sudo parted -l
Disk /dev/sda: 598GB
Disk /dev/sdb: 12.0TB
Disk /dev/sdc: 146GB
However, sdb is a virtual disk made up of VGs in a Dell Powervault MD shelves.
Here is more Linux info:
sudo pvs
PV VG Fmt Attr PSize PFree
/dev/sda1 pgsqlvg lvm2 a-- <557.25g <111.45g
/dev/sdb1 moodlevg lvm2 a-- 10.91t 2.18t
/dev/sdc3 sysvg lvm2 a-- 134.12g 26.62g
sudo vgs
VG #PV #LV #SN Attr VSize VFree
moodlevg 1 1 0 wz--n- 10.91t 2.18t
pgsqlvg 1 1 0 wz--n- <557.25g <111.45g
sysvg 1 2 0 wz--n- 134.12g 26.62g
sudo lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
moodlelv moodlevg -wi-ao---- <8.73t
pgsqllv pgsqlvg -wi-ao---- <445.80g
slash sysvg -wi-ao---- <106.50g
swap sysvg -wi-ao---- 1.00g
sudo df -hT -x tmpfs -x devtmpfs
Filesystem Type Size Used Avail Use% Mounted on
/dev/mapper/sysvg-slash xfs 107G 8.6G 98G 9% /
/dev/sdc2 xfs 1014M 213M 802M 21% /boot
/dev/sdc1 vfat 1022M 9.7M 1013M 1% /boot/efi
/dev/mapper/moodlevg-moodlelv xfs 8.8T 5.4T 3.4T 62% /usr/local/moodle
/dev/mapper/pgsqlvg-pgsqllv xfs 446G 401G 46G 90% /var/lib/pgsql
So why called by different names, why are amounts different? Are things getting backed up twice? Should I be not backup "Entire Computer"?
-
- Enthusiast
- Posts: 27
- Liked: 4 times
- Joined: Dec 21, 2018 4:35 pm
- Contact:
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: disk look different in agent job vs. backup copy
Hello rgmueller,
Can you please check if that was a first backup copy job run or not? Copy job creates first full backup from the source agent backup on disk, while agent backup shows you the incremental changes (I assume the stats from the agent job run are incremental), thus you see the difference in the transferred data size. Cheers!
Can you please check if that was a first backup copy job run or not? Copy job creates first full backup from the source agent backup on disk, while agent backup shows you the incremental changes (I assume the stats from the agent job run are incremental), thus you see the difference in the transferred data size. Cheers!
-
- Enthusiast
- Posts: 27
- Liked: 4 times
- Joined: Dec 21, 2018 4:35 pm
- Contact:
Re: disk look different in agent job vs. backup copy
Both the agent and backup copy job statistics are not for the first BC job run. Both the agent and the BC jobs have been running for a long time (> year). Agent is a forever forward incremental.
-
- Product Manager
- Posts: 14726
- Liked: 1707 times
- Joined: Feb 04, 2013 2:07 pm
- Full Name: Dmitry Popov
- Location: Prague
- Contact:
Re: disk look different in agent job vs. backup copy
Thanks for sharing. If both job runs were incremental I'd suggest to raise a ticket and share the debug logs with the support team. Cheers!
Who is online
Users browsing this forum: No registered users and 6 guests