by Kenneth » 15 Jul 2019, 13:07
TeamDrive uploads your files as Binary Large Objects, which are better known as BLOBs. In very rare occasions, incomplete and/or unreferenced BLOBs can end up on your cloud storage depot and take up needed cloud storage.
A common example of how this can happen is when, for example, you start uploading a file and in the midst of uploading the file you quit and uninstall TeamDrive because you were under the impression TeamDrive needed to be uninstalled before updating to the latest version. Well, uninstalling TeamDrive deletes the TeamDrive data directory, which is where BLOBs to be uploaded are stored until they have been completely uploaded and your client receives a confirmation from the server, that the file has been successfully uploaded. After reinstalling TeamDrive, this BLOB can neither continue to be uploaded nor can it be confirmed by the server, since the TeamDrive data directory was deleted during the inadvertent uninstalling of TeamDrive.
To free your cloud storage depot of these incomplete/unreferenced BLOBs it is necessary to run the function "cleanup storage" on the Space, in which the upload of the file took place.
To run the function "cleanup storage", please do the following (please be advised, that administrator rights in the Space are required):
Navigate to "Active Spaces". Hover the mouse over the desired Space (on iOS and Android swipe the Space from right to left) and click on “i” to open the Space’s “Information” page. From there, click on "server" and then on "cleanup storage".