Releases: EMCECS/ecs-sync
Releases · EMCECS/ecs-sync
ecs-sync v2.1.3
- Fixed bug where S3Target was not copying metadata from a filesystem
- S3Source should now be compatible with Google Storage
ecs-sync v2.1.2
- Added clip name property to CasSimpleTarget to allow setting a generic clip name
ecs-sync v2.1.1
- Added plugin to support non-CAS to CAS migrations (including File to CAS)
- Added source file list option to FilesystemSource
- Minor UI tweaks
ecs-sync v2.1
- New browser-based UI available for Filesystem <-> ECS S3 syncs
- Connects to ecs-sync running on the localhost in
--rest-only
mode - Support for multiple jobs and scheduling
- Provides sync completion reports and basic email alerts
- Resilient configuration, history and reports (stored in an ECS bucket)
- Connects to ecs-sync running on the localhost in
- FilesystemSource now preserves POSIX user/group and mode which FilesystemTarget will attempt to restore (must run as root)
ecs-sync v2.0
- New REST service and rest-only mode allows interaction over HTTP to start, pause, resume and stop sync jobs as well as change thread counts and provide progress information
- New CLI tool to interact with a running sync process (uses the REST service). Provides pause, resume, thread-counts and progress info (note: the ecs-sync jar itself still supports the legacy CLI)
- New EcsS3 plugins using EMC's smart object client with client-side load balancing, node discovery and automatic retry
- Sync process allows for configurable retry attempts on failure (default is 2 retries)
- TrackingFilter removed and new optional DbService added with better status granularity and more metadata about objects (size, mtime, etc.). Supports MySQL and SQLite (file-based)
- Optional split thread pools for large and small objects
- New performance monitoring provides real-time bandwidth and throughput information for all plugins that support it
- New source plugin estimation feature to estimate scope and provide for progress determination
- Filesystem metadata is now encapsulated in the source as object metadata and restored in the target if present
- Decoupled sync tasks from query tasks (crawling is now done independent of syncing; i.e. children could potentially be synced before their parent directories). allows for significantly faster crawling since directories do not need to be synced just to crawl their children
ecs-sync v1.4
https://community.emc.com/docs/DOC-38905
- changed project name to ecs-sync
- fixed SDK-116 (memory leak in CAS plugins when many clips fail)
- added docker support via config and scripts inside the docker/ folder of the distribution
- S3Source: when migrating the root of a bucket, now uses flat enumeration instead of crawling the prefixes (which is not necessary in this case)
- reduced source_id column in tracking table and reverted back to a primary key for performance
- other minor bug fixes
vipr-sync v1.3.6
https://community.emc.com/docs/DOC-38905
- fixed bug in CLI parsing of S3 URIs
vipr-sync v1.3.5
https://community.emc.com/docs/DOC-38905
- fixed bug in S3 plugins that prevented migrating a single key
- changes in tracking DB table to allow for longer identifiers and more error details
vipr-sync v1.3.4
https://community.emc.com/docs/DOC-38905
- when auto-creating a bucket with includeVersions enabled, S3Target now checks to see if the source bucket has versioning enabled before enabling it on the new bucket
vipr-sync v1.3.3
https://community.emc.com/docs/DOC-38905
- added support for versioned buckets in S3 plugins (optionally copy all versions to target)
- added option in S3Target to automatically create the bucket if it doesn't exist