Questions tagged with Amazon FSx for Windows File Server
Content language: English
Sort by most recent
A customer is exploring the FSx HDD option. While looking at the cost of backup of FSx(https://aws.amazon.com/fsx/windows/pricing/), it seems the backup cost is higher then the actual storage cost. Like for single Az deployment , HDD storage capacity cost is 0.013per GB-month, while backup is 0.050 per GB-month, Is there any specific reason? Is it due to the fact that backup is going to be stored in S3?
A customer has files on S3 (provided by Transfer Family) and they need to copy/move files uploaded to S3 to their FSx for Windows. This could be done with a dedicated machine to do this job. However, I wonder whether it is possible to solve this without the need to manage a dedicated EC2 instance.
My best guess so far is to use DataSync. I know that I can't use the combination "Location S3, destination FSx". However, the combination "Location S3, destination SMB" is possible.
1) Is it possible to use DataSync for the combination "Location S3, destination SMB (and this is actually FSx)"?
2) Are there any pitfalls to solve the customer's problem in this way?
3) Do you see a better solution to move files from S3 to FSx?
I'm trying to use Amazon FSx for SAP on Windows High Availability environment, but run into an issue where I can’t assign a CNAME to Amazon FSx Multi-AZ file system deployment. (CNAME works fine in Single-AZ file system deployment)
I also can’t use the native AWS naming of the Amazon FSx file system ID as this is more than 13 chars, which is not supported by SAP.
Are you able to provide some guidance around how we set up the SAP Central Services to use Amazon FSx Multi-AZ file system for our SAPGlobalHost share ?
(Have seen some documents that loosely implies you need to setup DFS replication between 2 Single-AZ file system deployments, is this correct as it seems very clunky and not a straight forward solution?)
Customer would like to know the IOPS performance when the volume is <1TiB. From doc ( https://docs.aws.amazon.com/fsx/latest/WindowsGuide/performance.html ), it stated 3,000 Disk IOPS per TiB of storage, what if customer provisioned 500GiB volumes, will it be 3,000/1,500 IOPS? (Shall we consider 3 IOPS per GiB?)
For SQL Server running on EC2 and using FSx, when the FSx maintenance window happens, will there be an interruption to SQL Server ? Do the databases become disconnected?
Hi,
I can't deploy FSx in my application account because it doesn't like AD Connector.
I've tried deploying FSx in my shared services account but, although DNS resolves, mapping a drive results in "resource ... is not responding".
The default security group limits outgoing traffic to itself. Should I add another rule for my application account's VPC?
Thanks,
TL
Hello
Currently, 100TB of data is compressed to 50TB using the deduplication function of Windows.(EC2 on AWS)
I want to migrate this data to FSx for windows.
(The FSx pricing structure costs because of storage and throughput capacity)
ec2⇒robocopy⇒FSx for windows
However, if you remove the deduplication function when performing data migration, the data capacity will return to 100 TB and a lot of costs will be incurred.
Is there a specific way to migrate data to FSx with the data deduplicated?
We want to reduce the cost and migrate data to FSx.
I want to use windows robocopy as the data migration method.
Hello,
We have really been looking forward to the HDD storage-type and now with it being launched we want to try this out and migrate to FSx from our legacy fileshares.
However when reading the CF-documentation here:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-fsx-filesystem.html
I can see it mentions:
```
For Windows file systems:
If StorageType=SSD, valid values are 32 GiB - 65,536 GiB (64 TiB).
If StorageType=HDD, valid values are 2000 GiB - 65,536 GiB (64 TiB).
```
however neither in "AWS::FSx::FileSystem" or in "AWS::FSx::FileSystem WindowsConfiguration" I can find where to specify that parameter to set the FSx resource to the HDD storage-type.
A blocker for us to launch FSx using the HDD-option, would appreciate assistance / how and where to specify storagetype to HDD.
Best Regards - TheSwede86
**Update 2020-04-02**:
Heard it was going to be fixed / added soon so I'm closing this.
Hello, a customer has 30TB of Windows shares and would like to have a DR solution for it in AWS.
I thought first about using FSx for Windows and using DataSync to continuously import data from on-prem to FSx. However I would like to decrease the price of the solution: is it possible to have this kind of flow?
1. First import the data from on-prem to S3
2. Store the data in S3 when the DR is not activated
3. Make incremental backups regularly to S3
4. Finally, import to FSx when the DR is activated ?
The customer is also using CommVault as a third-party tool.
Thank you in advance.
Hello everyone ,
Instead of finding the solution for my last post i thought it would be better to ask .
I have this enveironment :
- one Load Balancer with a target group of 2 windowss EC2 instances running a web app on port 80
- both windowss ec2 must have a shared drive eg: an " D:\ "
What would be the best aproach for this situation ?
I already created this env. but i cannot succed in creating the shared drive.
What i have tried :
1. an FSX share but after i joined the windows ec2 instances the tomcat service cannot see that drive. I have tried to run the tomcat service either with the Local System user(default) or the Domain User that is an local Admin and also with the Local Workgroup Adminstrator.
Here i have also tried with MKLINK and same outcome.
2. I thought in creating a FailOverCluster between the nodes and then add a storadge and create a Cluster Shared Volume.
This might work but i think its an "overkill" as infrustructure and also prices.
(even thou im not sure what type of storage to add to the ec2 instances , in phisical env. this would require a SAN with ISCSI).
So , please let me know if there are other solution i should take in consideration.
Thank you for reading my post.
We are currently migrating to AWS and have around 90 TB of CIFS/SMB shares to be migrated to AWS and we are thinking of using FSX. However, there is a requirement within the applications to use the same share name as on prem. Can this be achieved by FSx for Windows?
Example: On prem application reads/writes to a share - \\nanpfssvfp01a\VMS_Entapps_1\Active_X
Is it possible to retain the same naming convention on FSx?
Example: The application reads and writes to share "\\nanpfssvfp01a\VMS_Entapps_1\Active_X". Can this be share name be retained?
Hello,
I have been stuck on trying to mount FSx on ec2 instances and workspaces. Both are joined in the AWS managed active directory. The security group associated with FSx is the default wide open one. I've attempted this as the domain admin but always get network path not found. Any help would be greatly appreciated.
Thank you.