Failed to get whole disk by device number

Backup agent for Linux servers and workstations on-premises or in the public cloud

Re: Failed to get whole disk by device number

Veeam Logoby Daniel N. » Mon Feb 20, 2017 1:07 pm

PTide wrote:Hi,

No, currently we don't have that functionality on the list due to a low demand. Anyway your feedback is noted, thank you!


Please increase the demand counter by one. :)
I run a VPS by www.hosteurope.de and also see the error message
Code: Select all
boost::filesystem::directory_iterator::construct: No such file or directory: "/sys/block/ploop23837p1/slaves"
Daniel N.
Enthusiast
 
Posts: 28
Liked: 3 times
Joined: Sun Feb 15, 2015 7:03 am

Re: Failed to get whole disk by device number

Veeam Logoby willinit » Tue Mar 14, 2017 3:36 am

Would love to see this feature as well. Currently have about 30+ OpenVZ servers and being able to set up jobs for specific container folders would be a huge help.

To chime in on the error front, what I get when trying to add a backup job is the following error (CTID is in place of the actual container ID). But the thing is, this isn't an NFS or SMB mounted partition.
"Network filesystems (NFS, SMB) cannot be backed up. Please exclude: /vz/root/CTID/sys."

Another container gave the following error:
"Network filesystems (NFS, SMB) cannot be backed up. Please exclude: /vz/root/CTID/proc."
willinit
Lurker
 
Posts: 1
Liked: never
Joined: Tue Mar 14, 2017 3:24 am

Re: Failed to get whole disk by device number

Veeam Logoby efranklin » Wed Jun 21, 2017 3:42 pm

I also love to have this feature as well. Encountered this trying to backup a VPS at Media Temple.
efranklin
Service Provider
 
Posts: 4
Liked: never
Joined: Thu Jan 26, 2017 8:36 pm
Full Name: Eric Franklin

Previous

Return to Veeam Agent for Linux



Who is online

Users browsing this forum: No registered users and 5 guests