I've configured FileZilla accordingly, created a backup schedule for testing. The backup was estimated to be approx 365mb in size. The schedule kicked in and started uploading content to the FTPS server. At the 297mb mark, vcsa start deleting all the content and spits out and error, "BackupManager encountered an exception." The logs on FileZilla do not show anything unusual, but checking the /var/log/vmware/applmgmt/backup.log, I found this entry:
BackupManager encountered an exception: While reading from '/etc/systemd/network/10-eth0.network' [line 8]: option 'address' in section 'Network' already exists
I checked the file the error is referencing and that particular line is the IPv4 address of the vcsa.
I disabled IPv6 on the VCSA and grep'd the file again to ensure the IPv6 entry is gone (which it was), and the backup completed.
I've been told that disabling IPv6 can mess up patching? Can anyone clarify? If so, is this still a thing in 6.7?
TimR26 - i dont know really about the patching thing, but just a heads up that you will encounter the same exception if you are planning to have multiple static routes configured. We are encountering same exception with backup manager. Till now it appears that there are no workarounds.
It seems, even though we are writing 2019 on the calendar, that IPv6 is still not fully supported.
I have recently tried the VCSA backup feature on a number of VCSAs and they all fail consequently at about 35%. When I look in the backup.log, I find an error like this:
BackupManager encountered an exception: While reading from '/etc/systemd/network/10-eth0.network' [line 7]: option 'gateway' in section 'Network' already exists
The 10-eth0.network file looks like this:
Which is a perfectly legal dual-stack config file.
All our VCSAs are running 6.7U2 (188.8.131.52000)