Script creates a file with 0 KB but it takes over 12GB REAL SPACE on disk.

Mar 5, 2015 at 3:48 PM
HI, all

First a huge thanks for an awesome script.

Now to my "problem":

When the script runs it creates a file in the folder \servername\farmbackups$\Sites\ and the file name is the same as the servername.

So what I have is a file the windows says is 0 KB, even when trying to do a file defrag of it with contig(https://technet.microsoft.com/en-us/library/bb897428.aspx) it too says the file is 0 kb.

When i try to copy the file to a drive with less that 10GB free space, windows says it can NOT copy it as there is NOT enough free space.

I have tried to see from the logs from what in the script creates this files as this eventually builds up to take all the space on the drive as the purge do not "see" this and do not purge it.

Any help on this matter is greatly appropriated.

Regards
Mar 6, 2015 at 7:47 AM
Unubtanium wrote:
HI, all

First a huge thanks for an awesome script.

Now to my "problem":

When the script runs it creates a file in the folder \servername\farmbackups$\Sites\ and the file name is the same as the servername.

So what I have is a file the windows says is 0 KB, even when trying to do a file defrag of it with contig(https://technet.microsoft.com/en-us/library/bb897428.aspx) it too says the file is 0 kb.

When i try to copy the file to a drive with less that 10GB free space, windows says it can NOT copy it as there is NOT enough free space.

I have tried to see from the logs from what in the script creates this files as this eventually builds up to take all the space on the drive as the purge do not "see" this and do not purge it.

Any help on this matter is greatly appropriated.

Regards
Posted in wrong place, can admin move to issues or should I re create it?
May 12, 2015 at 10:38 AM
Hello,

I encountered the same problem, this is related to the site Name:

https://spfarmbackup.codeplex.com/workitem/1133

You can see the space actually used only with Disk Usage tool https://technet.microsoft.com/fr-fr/sysinternals/bb896651.aspx

The easiest way is to delete the corrupt file and modify the script with the code shown in the issue.

Regards,
May 12, 2015 at 11:06 AM
A huge THANK YOU, for this information. :)
Cannot believe i did not find that bugpage