AutoBak 2

AutoBak 2: Asynchronous & Filtered Backup Utility

AutoBak 2 is a robust, lightweight C# utility designed for reliable, non-blocking backup of directory structures. It integrates advanced filtering and asynchronous execution to ensure efficient and controlled data migration and archiving..

🔧 Features

• ✅ Asynchronous Job Execution: All I/O tasks run off the UI thread, ensuring responsiveness.

• ✅ Decoupled UI/IO Logic: The core executor is free of UI code (no direct popups/messages).

• ✅ Graceful Job Cancellation: Full support for aborting running jobs safely via CancellationToken integrated into recursive functions.

• ✅ Accurate Progress Reporting: Reliable progress updates are calculated based on a two-phase file count and reported safely to the UI.

• ✅ Two Transfer Modes: Supports both recursive Directory Copy and Filtered ZIP Archiving.

• ✅ Comprehensive File Filtering: Files and folders specified in Excluded Items are skipped during both counting and processing (copy/archive).

• ✅ Dynamic Destination Naming: Automatic creation of unique, timestamped target subdirectories (yyyy-MM-dd-HH-mm__Name).

📝 Detailed Description

AutoBak 2 is a lightweight, high-control backup solution built on C# for Windows. Its primary strength lies in its asynchronous architecture, which offloads all potentially long-running I/O tasks—be it recursive directory copying or filtered ZIP archiving—to a background thread. This ensures the user interface remains responsive and usable even during extensive operations.

The utility provides high operational safety through graceful job cancellation, allowing the user to immediately and safely abort any running job via a integrated CancellationToken. Progress tracking is highly reliable; the system first performs an accurate file count, respecting all configured exclusions, before starting the transfer. This two-phase approach allows for precise progress reporting back to the UI.

In terms of data integrity, AutoBak 2 guarantees non-destructive backups by employing dynamic destination naming, creating a new, timestamped subfolder for every single run. The logic for comprehensive file filtering is consistently applied across both the counting phase and the final data transfer phase, ensuring unwanted files and folders are never processed. Finally, the architecture enforces a clean separation of concerns: the core executor solely focuses on execution and throws exceptions upon failure, while the UI handles all error messages and final status updates, ensuring stability.