Standalone backup agents for Linux, Mac, AIX & Solaris workloads on-premises or in the public cloud
pama
Enthusiast
Posts: 42 Liked: 1 time
Joined: Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti
Contact:
Post
by pama » Sep 01, 2016 9:09 am
this post
Code: Select all
Known Issues and Limitations
• Backup job may fail if an onboard RAID is used
A lot of tester will be cut-off... any chanche to get it working?
Thank you
PTide
Product Manager
Posts: 6551 Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Post
by PTide » Sep 01, 2016 9:26 am
this post
Hi,
Dev team has already brought many improvements and yet more to be done so the research is still in progress. Have you tried BETA2 with your RAID configuration?
Thanks
pama
Enthusiast
Posts: 42 Liked: 1 time
Joined: Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti
Contact:
Post
by pama » Sep 01, 2016 10:53 am
this post
Thanks for your reply,
I have tested and backup fails immediately with
Code: Select all
2016-09-01 11:10:15 Job started at 2016-09-01 11:10:15
2016-09-01 11:10:15 Starting backup
2016-09-01 11:10:17 [error] No objects to backup.
2016-09-01 11:10:17 [error] Failed to perform backup
The result is the same both with "volume level backup" and "entire machine"
kylet
Lurker
Posts: 2 Liked: 1 time
Joined: Jun 24, 2016 2:23 pm
Full Name: Kyle Tucker
Contact:
Post
by kylet » Sep 02, 2016 1:47 pm
1 person likes this post
I got quite far along backing up a 1.5TB LVM which sits on a Dell R420 PERC RAID6 set. This is from the Agent.Target.log file.
Code: Select all
[01.09.2016 16:15:38] <140686242330368> cli | - 47%, workload rps: 88/6/0, client: {325621eb-a14c-42c3-8647-3c
99e98b2b94}
[01.09.2016 16:15:49] <140686242330368> cli | - 47%, workload rps: 88/6/0, client: {325621eb-a14c-42c3-8647-3c
99e98b2b94}
[01.09.2016 16:15:52] <140685793548032> | ERR |Asynchronous data reader has failed.
[01.09.2016 16:15:52] <140685793548032> | ERR |Snapshot overflow.
[01.09.2016 16:15:52] <140685793548032> | >> |--tr:Failed to read from aggregated device. Requested offset: [70
3637487616]. Data size: [1048576].
[01.09.2016 16:15:52] <140685793548032> | >> |--tr:Failed to read from memory backed device. Requested offset:
[703637487616]. Data size: [1048576].
[01.09.2016 16:15:52] <140685793548032> | >> |--tr:Failed to read the next block from the disk. Disk: [vg_syslo
g]. Current offset: [703,637,487,616]. Disk size: [1,495,337,533,440]. CBT tracker: [Incremental multi-tracker { bitmap
_tracker:// , bitmap_tracker:// , }].
[01.09.2016 16:15:52] <140685793548032> | >> |--tr:Next asynchronous read request cannot be processed.
[01.09.2016 16:15:52] <140685793548032> | >> |--tr:Asynchronous data reader has failed.
[01.09.2016 16:15:52] <140685793548032> | >> |Unable to retrieve next block transmission command. Number of alr
eady processed blocks: [436541].
PTide
Product Manager
Posts: 6551 Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Post
by PTide » Sep 02, 2016 4:04 pm
this post
Hi Kylet,
Please provide all logs (you can send me an archived /var/log/veeam directory) as well as outputs from lsblk -af and dmesg -T via any filesharing service of your choice.
Thanks
pama
Enthusiast
Posts: 42 Liked: 1 time
Joined: Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti
Contact:
Post
by pama » Sep 12, 2016 6:29 am
this post
Any news about this?
Thank you!
PTide
Product Manager
Posts: 6551 Liked: 765 times
Joined: May 19, 2015 1:46 pm
Contact:
Post
by PTide » Sep 12, 2016 11:24 am
this post
Hi Andrea,
Please run tar -hczvf sysfs_dev_block.tar.gz /sys/dev/block/* and send me the resulting file. Please note that the archiving process might take a while.
Thanks
pama
Enthusiast
Posts: 42 Liked: 1 time
Joined: Apr 20, 2011 1:02 pm
Full Name: Andrea de Lutti
Contact:
Post
by pama » Sep 12, 2016 12:31 pm
this post
Replied by pm.
Thank you
Users browsing this forum: AdsBot [Google] and 14 guests