Jump to content
NAKIVO Community Forum

How do you configure Transporter for pre-existing AWS VPC?


mike_howell_beardon
 Share

Recommended Posts

Hi everyone,

Has anyone successfully implemented Backup from AMS/EC2?  I'm not having much luck.  I have a local VMware Nakivo Director appliance targeting an Ubuntu EC2 instance for Backup.  I followed these steps: 

https://helpcenter.nakivo.com/display/NH/Deploying+Transporters+in+Amazon+EC2

When I let the transporter deploy with Automatic settings, I get a new Nakivo VPC which my local Director can reach, but it cannot initiate a backup (I get an error message).  However when I create the transporter Manually, the deployment fails partway through with an error that the transporter can't be reached.  Since the automatically deployed Transporter was at least reachable from my Director, I've focused on trying to get that working, but I've not had real success.

With the separate Nakivo VPC, I tried setting up a VPC Peer and adjusting my routing tables.  I can get the AWS Transporter to ping my target EC2 box, but I don't know what else is needed.

Has anyone had success with this kind of setup?  Essentially...what is "X" below?

[VMware Director appliance] ====> (internet) ==== (Nakivo VPC [Nakivo Txport])...X...(Target VPC [target EC2 Ubuntu])

Any help is greatly appreciated!

--Mike

  • Like 1
Link to comment
Share on other sites

There is no X in the mentioned schema, NAKIVO director sends the API request to the EC2 to attach the source instance volume to the transporter then the transporter sends the backup data to the repository.

The transporter must have the access to the source instance security group to have the access to the volumes and the transporter port 9446 must be reached by the director and the target transporter and the ports 9448-10000 must be reached by the target transporter.

It is better to contact NAKIVO support at support@nakivo.com so you can resolve this case much faster in this case.

Please make sure that the required ports are opened -https://helpcenter.nakivo.com/display/NH/Deployment+Requirements#DeploymentRequirements-RequiredTCPPorts .

Then deploy a transporter on AWS -https://helpcenter.nakivo.com/display/NH/Deploying+Transporters+in+Amazon+EC2 .

Create and run an EC2 backup job -https://helpcenter.nakivo.com/display/NH/Creating+Amazon+EC2+Backup+Jobs .

In case of any failure, please generate and send a support bundle to NAKIVO support -https://helpcenter.nakivo.com/display/NH/Support+Bundles .

Link to comment
Share on other sites

Hi Mod,

Thanks for the info--just to clarify I did also follow your linked steps previously.  Using my Transporter with Automatic settings, I deployed a new test Nano instance with a small (8g) disk into the same VPC as the Real target.  That Test target *does* back up (using your EC2 job steps).  However another Test Nano with a large (100g) disk fails with an error.  I transmitted a support request, but haven't seen a reply yet. 

The Real target instance has a 500g data volume mounted to it, so I'm very interested in knowing if size is a limiting factor.  My next trials will be to add a volume to my Test instance and see if there's some point where I can't fetch it.

  • Like 1
Link to comment
Share on other sites

@mike_howell_beardon NAKIVO transporter that was deployed in AWS is reading EC2 EBS volumes as-is, volume capacity should not act as a limited factor preventing EC2 volume that was deployed in AWS from being read by the NAKIVO transporter.

If you experience any error while using NAKIVO, please refer to NAKIVO support providing details of circumstance under which this error has occurred. To better assist we suggest you include the support bundle (http://www.nakivo.com/helpcenter/display/NH/Support+Bundles) to support@nakivo.com, reflecting the issue as well as the screenshots of the various stages of running the job.

Link to comment
Share on other sites

Just to follow up ... I was able to backup a test instance with a 500g attached volume successfully.  But the production target server still fails.  I transmitted a support bundle to Nakivo using the built in tool.  Unpacking the bundle, I found in the events.log an error "NoAppropriateTransporterInAwsRegionAlarm ... There was a problem with the "SelectAndLockTransporters" action ("<hex> <name>" instance). Time spent: 0 seconds. Reason: cannot select transporters."  Not sure how it would be different...

  • Like 1
Link to comment
Share on other sites

I got an answer from Support which sparked a realization.  I believe I have figured out the problem.  The transporter instance size was much smaller than the target EC2 instance.  I deployed a new transporter of a size that matched the target instance and kicked off the backup.  It is running now and no errors so far, knock wood.

 

  • Like 1
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...