AUSST verzeichnis zu gross

@Tobias Frank Germany,

Your --cleanup command appears to be correctly formatted. However, please note that the --cleanup option operates based on the filters used during the most recent --incremental sync. If no specific filters were applied during the sync, the cleanup may not remove all older versions as expected.

Based on the logs, I recommend reviewing the --filterProducts parameters used in the last sync to ensure that no unintended files are being retained. Additionally, verify the status of the last incremental sync to ensure that older versions are being excluded as anticipated.

Verify Last Filters Used: To confirm the filters applied during the last sync, check the ffc.xml file:

In command window (for Windows) or the terminal (for macOS), run the following commands:
Windows
powershell -command "& {Get-Content <path for ffc.xml file> -Tail 5}"
Sample path if the FFC file is on a server: /<server>/ACC/services/ffc/products/ffc.xml
macOS:
tail -f <path for ffc.xml file>
Sample path if the FFC file is on a server: /<server>/ACC/services/ffc/products/ffc.xml
These commands will display the last few lines of the ffc.xml file. 

Hi @Tobias Frank Germany,

Thank you for reaching out. It seems you're encountering challenges with the AUSST not properly cleaning up old versions. Here are some steps to help resolve this issue:

Using the Cleanup Command:
Ensure that the --cleanup command is being executed correctly. This command removes obsolete or unnecessary products from the server. To retain specific products, use the --filterProducts parameter. For detailed guidance, refer to Adobe’s official documentation on maintaining AUSST.

Incremental Sync and Cleanup:
Execute the --incremental and --cleanup commands separately to better manage product versions. The incremental sync ensures only new updates are downloaded, while cleanup removes older, unnecessary files based on the last used filters. For detailed guidance, refer to Adobe’s official document on common use cases.

If the issue continues, check the server logs for errors during cleanup or synchronization to identify why older versions are not being removed.

I hope these steps help. Please let me know if the issue persists, and we can explore further troubleshooting options together.

Regards,