Managing network share storage can be a constant battle against bloat. Large logs, uncompressed media, and forgotten archives can quickly drain your expensive server storage. Automating file compression is the most efficient way to reclaim gigabytes of space without manual intervention.
Here is a step-by-step guide to setting up automated file compression on Windows and Linux network shares.
Method 1: Windows Server (NTFS & File Server Resource Manager)
Windows Server offers a built-in feature called File Server Resource Manager (FSRM) that allows you to target and compress files automatically based on specific rules. Step 1: Install File Server Resource Manager Open Server Manager. Click Manage > Add Roles and Features. Advance to Server Roles. Expand File and Storage Services > File and iSCSI Services.
Check File Server Resource Manager and complete the installation. Step 2: Create a File Management Task
Open File Server Resource Manager from your administrative tools. In the left pane, expand File Management Tasks.
Right-click File Management Tasks and select Create File Management Task. Step 3: Configure Target Paths and Conditions
In the General tab, give your task a name (e.g., “Compress Old Files”).
In the Scope tab, click Add and select the network share folder you want to target. In the Condition tab, click Add.
Set a condition, such as Days since last modified, and set the value to 90 days. Step 4: Set the Action to Compress Go to the Action tab. Select Custom from the dropdown menu.
Under the command executable, point it to a PowerShell script designed to compress files, or set the folder properties to native NTFS compression by running a command-line utility like compact.exe /c /s. Step 5: Schedule the Automation Go to the Schedule tab. Click Create Schedule.
Choose a time during off-peak hours (e.g., 2:00 AM every Sunday) to prevent performance degradation for active users. Click OK to save and enable the task. Method 2: Linux Samba Shares (Bash & Cron)
If you host your network shares on Linux using Samba, you can combine a simple Bash script with a cron job to automatically find and zip old files. Step 1: Create the Compression Script Open your terminal and create a new script file: sudo nano /usr/local/bin/compress_share.sh Use code with caution. Step 2: Paste the Automation Logic
Add the following script, replacing /mnt/samba/share with your actual network share path. This script searches for files older than 30 days that are not already zipped, compresses them individually, and deletes the uncompressed original.
#!/bin/bash # Target directory SHARE_DIR=“/mnt/samba/share” # Find files older than 30 days, excluding already compressed formats find “\(SHARE_DIR" -type f -mtime +30 ! -name "*.zip" ! -name "*.gz" ! -name "*.rar" | while read -r file; do echo "Compressing: \)file” gzip “$file” done Use code with caution. Step 3: Make the Script Executable
Save and exit the file (Ctrl+O, Ctrl+X in Nano). Give the script execution permissions: sudo chmod +x /usr/local/bin/compress_share.sh Use code with caution. Step 4: Schedule with Cron Open the system crontab configuration: sudo crontab -e Use code with caution.
Add the following line at the bottom of the file to run the script every night at 3:00 AM:
0 3/usr/local/bin/compress_share.sh > /var/log/share_compression.log 2>&1 Use code with caution.
Save and close. The system will now manage your Samba share storage automatically. Best Practices for Network Compression
Always Backup First: Before deploying an automated deletion or compression script across an entire company share, ensure you have a verified, isolated backup.
Exclude Active Databases: Never compress active databases, virtual machine disks (.vhdx, .vmdk), or live application configuration files, as this can cause corruption and severe performance lags.
Notify the Users: Let your team know that files older than a specific timeframe will be zipped. This prevents panic when extensions change from .docx to .docx.gz. To help me tailor this article further, could you tell me:
What operating system (Windows Server, Ubuntu, TrueNAS, etc.) does your network share run on?
What types of files (logs, images, office documents) make up the bulk of your storage?
Leave a Reply