Search Results: DataSync
Browse through the questions and answers listed below or filter and sort to narrow down your results.
KVM DataSync Agent partial network connectivity failure
I am attempting to deploy a KVM DataSync Agent on my CentOS7 host, and I am stuck on the activation step. After the DataSync agent starts it is supplied with an address 192.168.122.19 I have configured an AWS VPC (CIDR 10.0.0.0/16) and established a site-to-site VPN tunnel to my on-prem private network. I can ping and ssh from my site to an EC2 instance (10.0.1.252) in my VPC. I can ping from an EC2 instance in my VPC back to various machines in my private network (192.168.1.0/24). I have created a datsync Endpoint in my VPC it was assigned 10.0.1.138 address When I run the "Test Network Connectivity" option from within the DataSync Agent console it partially fails 10.0.1.138:443 FAILED 10.0.1.138:1024-1064 10.0.1.138:1026 FAILED 10.0.1.138:1027 FAILED 10.0.1.138:1029 FAILED 18.104.22.168:22 PASSED 0.amazon.pool.ntp.org:123 PASSED 1.amazon.pool.ntp.org:123 PASSED 2.amazon.pool.ntp.org:123 PASSED 3.amazon.pool.ntp.org:123 PASSED Any suggestions on what I might have configured incorrectly? thanks
AWS DataSync - Control Traffic Details
A customer is working to enable AWS DataSync to be consumed. A question from the Security Architect is what does the control traffic on 1024-1064 include? Is this traffic encrypted ? I do understand this is a communication requirement between the DataSync Agent EC2/VM and DataSync Service per https://docs.aws.amazon.com/datasync/latest/userguide/datasync-network.html Thanks
AWS DataSync Error
Hi Team, we are facing some issues in the AWS Datasync while running datasync task in a specific testing agent, while the job is executing it is showing some error like "cannot allocate memory". so Please suggest some articles or any source that would be resolved the issue which we are facing. Thanks in Advance,
Datasync Agent in VPC
A customer is interested in DataSync and their security department is telling them to use VPC Endpoints/PrivateLink. As the team is looking through the documentation to provide the security department, a point of clarification is needed (https://docs.aws.amazon.com/datasync/latest/userguide/datasync-in-vpc.html). Documentation states that the agent can be "either on-premises or in-cloud and the DataSync service doesn't need to travel across the public internet or need public IP addresses". The following paragraph goes on to describe considerations when deploying the agent in a VPC. The customer would prefer to deploy the VMWare Datasync agent on-premises. East question that I would like answered: Does the agent have to be deployed in a VPC to use VPCE? Thank you in advance.
DataSync Agent on EC2 VM
Hello I would like to ask about DataSync Agent deployed on EC2 VM. We have EC2 machine with DataSync Agent installed and we noticed that both the machine kernel and the agent itself are outdated. According to FAQ (https://aws.amazon.com/datasync/faqs/): A: Updates to the agent VM, including both the underlying operating system and the AWS DataSync software packages, are automatically applied by AWS once the agent is activated. Updates are applied non-disruptively when the agent is idle and not executing a data transfer task. But it doesn't seem to be working for us. So the question is how to fix the automatic update or update the machine and agent manually? I would appreciate any help on this topic. Best regards
DataSync for Amazon FSx
Hello I would like to ask what is the difference between these two configuration methods: Way 1: https://aws.amazon.com/blogs/storage/how-to-replicate-amazon-fsx-file-server-data-across-aws-regions/ Way 2: https://www.youtube.com/watch?v=c4XQMDUVHU8 The case is as follows. I have 2 Amazon FSx, in two different regions, and I would like to implement synchronization between Amazon FSx in region X, and Amazon FSx in region Y using DataSync. Which method should I choose? I think method number 2 is better because of the lack of additional VM, I think it will be more cost effective. But I am not sure if there is not some hidden issue here that I should pay attention to? I would appreciate any help on this topic. Best regards.
How do DataSync incremental transfers work?
A customer is planning to use DataSync to copy data to EFS and a question came up about incremental transfers: If a single byte is changed on a source file after an initial transfer, does DataSync transfer the entire file or just the changed bytes during a subsequent transfer? The [documentation] states only files that have been added, modified, or deleted are transferred. This suggests to me that an incremental transfer copies an entire file if it has changed, not just a delta of changed bytes. Is that the case or does it work like rsync and transfers only the changed bytes? : https://docs.aws.amazon.com/datasync/latest/userguide/how-datasync-works.html
VPC Private Endpoint Service for Datasync
A customer is going to use Datasync to migrate data on-prem to S3 bucket through private network, DX connection has been established between on-prem and aws VPC. In Datasync, we can create VPC private endpoint according to our documentation: https://docs.aws.amazon.com/datasync/latest/userguide/datasync-in-vpc.html The DataSync agent will be deployed in EC2 in the VPC, I wonder if we also need to create another VPC endpoint for S3 to ensure end-to-end traffic remain in private traffic.
AWS Datasync mount.nfs: Connection timed out
Hi - Attempting to test a local environment with AWS Datasync Running AWS Datasync Agent in Windows Hyper-V Created the agent record in AWS console and registered the AgentID NFS is running locally using: haneWIN NFS Server (https://www.hanewin.net/doc/nfs/nfsd.htm) I have some NFS shares that I can mount successfully in a windows cmd prompt. Every time I create a task, I get a Task Status of "Unavailable" *mount.nfs: Connection timed out* How can I fix this?
EFS to s3 DataSync task failed to access location
Hi guys, I'm trying to copy data from efs that is in us-east-1 to a s3 in us-east-1, so I created a new datasync to do the job. The mount target is the ip address of the EFS filesystem and it's complaining about security group issue. Here is the error: Task failed to access location loc-0426eaa718cb13c76: x40016: Failed to connect to EFS mount target with IP: 10.107.196.128. Please ensure that mount target's security group allows 2049 ingress from the DataSync security group or hosts within the mount target's subnet. The DataSync security group should also allow all egress to the EFS mount target and its security group. I am having hard time deciphering the 2 statements. 1) Please ensure that mount target's security group allows 2049 ingress from the DataSync security group or hosts within the mount target's subnet. Is the mount target the EFS or the EC2 instance that EFS is mounted on? If I am not mistaken, EFS do not have security groups but the EC2 instance does, so is the 1st statement asking me to ensure that EC2 instance security group allow 2049 in bound from DataSync security group? 2) The DataSync security group should also allow all egress to the EFS mount target and its security group. after creating DataSync security group, do I add this new group to the EC2 instance that EFS is mounted to? Thank you.
Datasync EFS to S3 not working
Hi AWS team, I am trying to following https://aws.amazon.com/premiumsupport/knowledge-center/datasync-transfer-efs-s3/ to transfer data from EFS to S3 but currently I am unable to select S3 as destination location. The only options available are EFS & SMB. Not sure why this is happening. I have tried to create locations separately but even then S3 location is not present for destination. Datasync agent is created as EC2 & activated. I have tried with & without endpoints but still unable to find S3 when selecting destination location. Attached are few screenshots. Regards, Vikas Edited by: vikassachdeva on Apr 6, 2020 5:52 AM