Skip to main content

running a lab to test veeam v12.2 with storeonce VSAs. No firewalls, flat network etc. Simple stuff.

Backup test works then the copy (storeonce stores copies) fails with:

Backup copy was cancelled: ServerIncorrectAddressOrProtocol

Its all IP based, single NIC, all options allowed for storeonce NICs too….

any ideas?? Odd one if you ask me

Hi @MavMikeVBR -

Haven’t really seen this issue on here before. A brief search led me to see a Forums post from a couple yrs ago.

https://forums.veeam.com/veeam-backup-replication-f2/backup-copy-was-canceled-serverincorrectaddressor-protocol-t75173.html

Not really much was shared there, and no resolution was given.

Have you looked at the process of creating a Backup Copy (I assume that’s what you’re attempting to do?...a Veeam Backup Copy Job?) with StoreOnce?

https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_hpe_storeonce.html?ver=120


Hi @MavMikeVBR -

Haven’t really seen this issue on here before. A brief search led me to see a Forums post from a couple yrs ago.

https://forums.veeam.com/veeam-backup-replication-f2/backup-copy-was-canceled-serverincorrectaddressor-protocol-t75173.html

Not really much was shared there, and no resolution was given.

Have you looked at the process of creating a Backup Copy (I assume that’s what you’re attempting to do?...a Veeam Backup Copy Job?) with StoreOnce?

https://helpcenter.veeam.com/docs/backup/vsphere/backup_copy_hpe_storeonce.html?ver=120

yes I saw that link but sadly it didnt reveal a solution. I’ve gone through the logs and I can see the error but nothing is pointing me to anything specific. I’ve configured it all correctly and I can see items getting to the destination storeonce in the inbound queue but then it disappears…..very odd. Will dig deeper


Ok, keep me posted. You could open a Support case to see if they have any ideas. Logs are located in:
C:\ProgramData\Veeam\Backup\<job-name>.log . Maybe more detail will be in there.


after analysis of logs and checking the storeonces directly, DNS wasnt working.

Adding storeonce hosts and IPs into the local /etc/hosts on the VSAs solved the problem.

I’m surprised Veeam logs didnt show this….


Interesting. Well, glad you got it sorted. 

Best. 😊


Hello @MavMikeVBR ..I am also facing same issue. Please let us know ..how did you fix the issue. Please let me know. Thank you

 

I didn’t understand this “Adding storeonce hosts and IPs into the local /etc/hosts on the VSAs”


Hello @MavMikeVBR ..I am also facing same issue. Please let us know ..how did you fix the issue. Please let me know. Thank you

 

I didn’t understand this “Adding storeonce hosts and IPs into the local /etc/hosts on the VSAs”

yes you will need to obtain the storeonce hpeadmin user passwords via HP support so you can login via the CLI. Once you are in, edit /etc/hosts and add the storeonce IPs. Once this is done, should resolve the issue


Comment