Search Results

Without a cleanup policy, a remote archive grows indefinitely. Storage costs accumulate quietly, and eventually someone has to do a manual purge under time pressure. This article shows how to write a scheduled AFT! script that connects to an S3 bucket, inspect...

Many serious file transfer operations are parts of larger business workflows. A data pipeline might require a "claim" step where the downstream system registers its intent to process a batch before any files move, and a "completion" step where status is report...

A common integration pattern is moving files from a cloud object storage bucket (S3 or any S3-compatible service) to an SFTP server that a partner or downstream system expects to read from. The naive approach downloads each file to local disk first and then up...

Per-file notifications are noisy. A job that uploads fifty files and sends fifty Slack messages trains people to ignore all of them, which defeats the purpose. A better pattern is to collect the results of an entire batch, build a single formatted summary, sen...

This document lists every change in AFT! v4 that requires a script or configuration to be updated before it will run as expected. Read it before upgrading any production instance. The short answer for most users: the vast majority of AFT! v3 scripts will run ...

If you are running a Syncplify Server! v6/v7 HA cluster, then you probably already know that the most significant enhancement v8 bring to the game is its 100% new, much improved, and completely revolutionized HA subsystem. A 100% new HA subsystem, though, als...

Syncplify Server! is available as a Docker image on Docker Hub. This page covers how to deploy and operate it using Docker Compose. Prerequisites Docker Engine 24.0 or later Docker Compose v2 (the docker compose plugin, not the legacy docker-compose) The...