Unsolved
This post is more than 5 years old
35 Posts
0
3922
Setting up CTA to achive to AmazonS3
Hello,
We are currently using EMC CTA to archive files to Amazon S3. Right now I cannot get it to work. If I setup to archive from say our NS960 to our VNX7500, it works fine, creates the stub file and everything.
I keep running into the same error when trying to go out to Amazon. The thing I am finding is that a "dummy" file is created on the cloud, but my migration failed, so my file I'm trying to migrate never show's up.
What is unclear to me is which device actually transfers the file, is the cta, or the VNX datamover. Below is a segment of the error I am getting.
The HTTP server failed to respond to an OPTIONS method of the HTTP protocol.
1. Diagnose based on the status code.
2. If the status code is '1006 Connection Disconnected' this means that the Data Mover was unable to establish or use a TCP connection to the HTTP server.
Verify that the HTTP server is up and running on the correct port. This may be done with ... telnet {HTTP server} {port}.
Verify that the HTTP server is accessible to the Data Mover on the network. This can be done by executing server_ping server_x {HTTP server} on the Control Station.
3. Verify that a non-CGI connection is desired; use a CGI option if that was intended.
4. If necessary contact the HTTP server vendor to verify that they support the OPTIONS method for non-CGI connection.
I have also attached the entire log.
When we watch traffic from the datamover to our firewall, we never see it hit the firewall, however when we run a ping, we do see it.
Thank you! Any help would be appreciated.
Brandon
BAronson1
35 Posts
0
November 1st, 2013 13:00
Thank you Joe for responding.
Would you be able to give me an example of how the setup for the CID should look, maybe what the command is?
Also how can I check the ACD is running? I went though the guide, and honestly the ACD setup was somewhat confusing to me.
Thanks again.
JosephPGTS
12 Posts
0
November 1st, 2013 13:00
Hello Brandon,
Communication with AmazonS3 requires the REST protocol which a data mover does not use natively. All communication between AmazonS3 and a Celerra or VNX must happen through the CTA. You must have the Cloud recall service initialized and running. This was called Atmos Callback Daemon or ACD previously. Your DHSM CID is between the NAS file system and the CTA FQDN for ACD. You should only see firewall traffic from the CTA to AmazonS3.
If the CTA did not auto create your CID for you, make sure to create it to the CTA on port 9000. This requires that ACD has been initialized.
Regards,
JosephP
JosephPGTS
12 Posts
0
November 1st, 2013 13:00
You will want to review the section of the CTA Getting Started Guide titled:
Prerequisites for Celerra or VNX as an archive source
This will walk you through the commands needed on the CTA and VNX or Celerra to set this up.
For examples specifically for creating the CID, you will want to review section of the Guide called:
Configuring manually created DHSM connections for file migration or archiving
I highly recommend carefully reviewing the guide to make sure you have all the parameters correct, but the command to create it is:
fs_dhsm -connection -create -type http –secondary ' http:// /fmroot' -httpPort 9000 -cgi n -user -timeout 60
The command to check the ACD status on the CTA is atmoscallback status.
Regards,
JosephP
BAronson1
35 Posts
0
November 1st, 2013 13:00
Thanks again.
Does the ACD url need to point back to my VNX, or does it need to point to Amazon?
This is my output. id=17 is the filesystem that I am attempting to archive.
[nasadmin@AFCVNXCS0 ~]$ fs_dhsm -info id=17
SCCMFilesFS1:
state = enabled
offline attr = on
popup timeout = 0
backup = passthrough
read policy override = none
log file = on
max log size = 10MB
This is the command I ran to create the dhsm on the VNX-
fs_dhsm -connection SCCMFilesFS1 -create -type http -secondary 'http://ctaacd.nt.local/fmroot' -httpPort 9000 -cgi n -user cta -timeout 60
CTAACD.nt.local is pointing to my cloud tiering appliance. Maybe that is incorrect?