Deploying regularly to target machines can cause the disk space used on those machines to increase over time. Some of this space may be used by deployments that you no longer need. Deployment Manager identifies old deployments that can safely be deleted from each target machine.

Checking the space on target machines

Deployment Manager will warn you if you are running low on disk space on a target machine in two places:

• When you are about to deploy a release to one or more machines with low disk space

• On the Environments page

Target machines can have the following statuses:

	Insufficient disk space	The amount of disk space remaining is less than 500MB. Deployment Manager requires a minimum of 500MB to deploy a release. You will need to free up disk space on the target machine before continuing with the deployment.
	Low disk space	The amount of disk space remaining is less than 10% You can continue to deploy to this machine. To free up space on the machine, use Purge old deployments, or manually clear up space on the machine.

Deployment Manager updates the status of target machines every 30 minutes. To refresh the status manually, go to the Environments page and click Check health.

Freeing space on target machines

Click Purge old deployments to view the amount of space on each target machine that can be freed by deleting old deployments. As SQL Servers do not store deployments, they aren't included here. To view the folders that Deployment Manager will delete from a target machine, click

When you click Purge, Deployment Manager starts to delete folders that it can safely remove. The Activity history > Purge old deployments page shows you the progress and results of the Purge task.

To view details of the deletion, under Output, click Expand all.

What does Deployment Manager delete?

All deployment folders on target machines are deleted except the following:

• Active deployments

• The previous successful deployment

• The last complete successful deployment

• Any data between the last complete successful deployment and the active deployment

Note: If you deploy a project and skip a step, this isn't considered a complete successful deployment. If you skip steps regularly, this will limit the amount of data that can be purged.

A file may not be deleted for the following reasons:

• File is locked (in use) by an application

• File is read-only

• The agent doesn't have enough permissions

If Deployment Manager can't delete a file, it will skip the folder and continue the purge. Check the log output for details of any errors.