Executive summary
Dynawiild Engineering, a maker of architectural and structural metal products, needed a reliable, secure and cost-effective way to copy its critical business data off site for disaster recovery, automatically and as data grew. DevOps TechLab set up automatic sync from its office systems to Amazon S3, with versioning, lifecycle archiving to S3 Glacier, encryption and least-privilege access, and trained the client’s team to run it day to day.
- Client
- Dynawiild Engineering · Manufacturing
- Business problem
- Critical business data lived only in the office, with no reliable automated off-site copy.
- What we delivered
- Automatic sync to Amazon S3 with versioning, S3 Glacier archiving, encryption and IAM policies.
- Engagement
- Discovery, setup and training, then ongoing optimisation and reporting by DevOps TechLab.
- Outcome
- Data copied off site automatically and recoverable from before a problem.
How the data moves
| Before | After | |
|---|---|---|
| Where the data lived | Office systems only | Office systems plus an off-site copy in Amazon S3 |
| How copies were made | Needed a reliable, automated way | Automatic sync with Seafile |
| Older versions | Not kept off site | S3 versioning keeps earlier versions |
| Long-term copies | No archive tier | Lifecycle rules move older data to S3 Glacier |
| Security | To be designed | Encryption, IAM policies and access controls |
The business challenge
The company needed critical business data from its on-premises systems copied to the cloud for disaster recovery, reliably, securely and cost-effectively, without anyone having to remember to do it. The solution also had to keep up as the amount of data grew.
Why it mattered
- One fire or theft away from loss
With data only in the office, a fire, theft or failed server could mean lost work.
- Manual backups get skipped
Any process that relies on people remembering will eventually fail.
- Ransomware syncs too
A plain copy would faithfully copy encrypted or overwritten files.
- Storage costs that grow
Keeping every copy in standard storage would grow the bill every month.
What Dynawiild Engineering set out to achieve
- Copy critical business data off site automatically.
- Keep earlier versions so files can be restored from before a problem.
- Move older data to low-cost archive storage on its own.
- Encrypt the data and limit who can reach it.
- Let the client’s own team manage it day to day.
The solution: automatic, versioned off-site copies on Amazon S3
Seafile synchronises the business data from the office systems to Amazon S3 automatically. S3 versioning keeps earlier copies of every file, and lifecycle rules move older data to S3 Glacier.
A file gets encrypted by ransomware on day 5
Drag to the day you want to restore from.
Restored, clean.
Illustration of how S3 versioning works.
Key design choices
- Automatic, not manual
Seafile synchronises the data without manual steps, so copies never drift out of date.
- Versions, not just copies
S3 versioning keeps earlier versions, so a file damaged by ransomware can be restored from before the problem.
- Cost managed by rules
Lifecycle rules move older data to S3 Glacier for low-cost archiving.
- Run by the client’s own team
DevOps TechLab trained the team to manage and monitor the setup themselves.
Security and governance
The off-site copy is protected as carefully as the original.
- Encrypted
Business data is encrypted.
- Least-privilege access
IAM policies give each person and system only the access it needs.
- Access controls on the bucket
Bucket access controls limit who can reach the data.
- Reviewed regularly
DevOps TechLab reports regularly on performance and cost.
Architecture on AWS
| AWS service | Role in the solution |
|---|---|
| Amazon S3 (versioning) | Off-site copy of business data, with earlier versions kept |
| Amazon S3 Glacier | Low-cost archive for older data |
| AWS IAM | Least-privilege access policies |
| Seafile | Automatic sync from office systems to Amazon S3 |
How we delivered
- 01Discover
Reviewed the existing setup, what data mattered most and where the gaps were.
- 02Set up
Installed and configured Seafile, and set up the S3 bucket with versioning, lifecycle rules, encryption and access controls.
- 03Train
Trained the client’s team to manage and monitor the setup themselves.
- 04Care
Ongoing optimisation, with regular reports on performance and cost.
Business outcomes
A failed server, theft or ransomware attack in the office no longer means lost work.
- Copied off site automatically
Critical business data is copied to Amazon S3 without anyone having to remember.
- Recoverable from before a problem
Earlier versions are kept, so overwritten or encrypted files can be restored.
- Storage costs kept in check
Older data moves to a cheaper archive tier on its own.
- Encrypted and access-controlled
The data is protected and only reachable by the people who need it.
- Run in-house
The client’s own team runs it day to day.
What’s next
As the data grows, the same setup scales without change. DevOps TechLab continues to optimise it and report regularly on performance and cost.
Lessons for leadership teams
- Disaster recovery starts with one off-site copy that updates itself. Manual backups get skipped.
- Keep versions, not just the latest copy. Ransomware and accidental overwrites sync too.
- Let lifecycle rules manage cost, so the archive doesn’t become the biggest line on the bill.
DevOps TechLab is an AWS Advanced Tier Services Partner with the AWS Generative AI Competency and AWS SMB Competency. We design, build and run cloud and generative AI solutions on AWS for growing businesses, with 265+ cloud environments under management.
Questions people ask
What did DevOps TechLab set up for Dynawiild Engineering?
Automatic sync of business data from its office systems to Amazon S3 using Seafile, with versioning, lifecycle rules to S3 Glacier, encryption, IAM policies and training for its team.
Why keep versions as well as a copy?
If a file is overwritten or encrypted by ransomware, the damaged version syncs too. Versions let you restore the file from before the problem.
Is S3 Glacier suitable for disaster recovery?
For older data you rarely need, yes: it costs much less to store. Recent data stays in standard S3 so it can be restored quickly.
Is your business data copied off site today?
Book a 20-minute review. We check what is backed up, how often, and how long a restore would really take.







