Problems when move tapes to diferent AWS Storage Gateway VTL

[jmuro]

Hi,

We are in the process of setting up the offsite backup to AWS, I followed "using AWS VTL Gateway Deployment Guide", I did not have problems with the backup, neither with the restore, everything worked well.

The problem comes when I try to use another Veeam Server and another AWS Storage Gateway, The Veeam Server can import the tapes without problems but when i try to inventory tape or Catalog tape,it show me "Error Failed to inventory tape in Drive 3 (Server: VEEAM04, Library: AWS Gateway-VTL 0100, Drive ID: Tape3) Error: Tape erasure with type 1 finished with error Tape error: '1117' (The request could not be performed because of an I/O device error.) ",i try increase storport timeouts(https://www.veeam.com/kb1887) but dont work.

Server: Veeam 9.5 Update 3

Is anyone else having this issue?
Thank you very much.

[Dima P.]

Hello jmuro,

Please submit a support case (we need your debug logs to investigate this problem) and share the case id in this thread. Thank you in advance!

[jmuro]

The support case id is 02487369.
thanks

[Dima P.]

Javier,

Thanks. Found a good article about migrating virtual tapes from one gateway to another. Can you try to migrate a test tape using this approach: You Need to Recover a Virtual Tape from a Malfunctioning Tape Gateway. Thanks in advance.

[jmuro]

Hi Dima, I also followed instructions on that page, and still showing the same error. Thanks

[odge]

Did you manage to resolve this?

Getting the same error randomly on a VTL that wasn't migrated. just started giving errors this week

[Dima P.]

Hi guys,

Please share the text or the screenshot of the errors. Thanks.

[odge]

Hi

Check out http://prntscr.com/j3bor1

[odge]

If anyone was silly as me, I forgot to check the AWS control panel to see if the unit was reporting in...

I mean really! (Some firewall was changed, and it wasn't NATing the StorageGateway)

[Dima P.]

Matthew,

Thanks for the heads up, so the issue is resolved by adjusting the firewall settings?

[odge]

I think, more correct to say

"If you get this error, the AWS VTL appliance is functioning, but its not currently communicating with the AWS Datacenters".