locked
WHS 2011 - Delete backup but space not recovered. RRS feed

  • Question

  • Hi,

    I ran out of space on my drive where the backups are stored, so, I changed the backup options to only keep one monthly backup (it was 6 month) and deleted all backups of all machines except the last one.  I had 1GB left.

    Then, I lauched the cleanup task from the server.  After only a few minutes, it was finished.  I looked and the backup was gone except the last one, so far so good.  But I still have only 1GB left on my disk.

    The space occupied by the deleted backup is not recovered.

    It seems there is some dlls missing.  I dit not delete them, but I recently installed the fix KB2686857 to resolve the "monitoring error".  Here is a part of the RunTask-Cleanup.log file :

    [2116] 120422.163127.0619: RunTask: Executing RunTask with arguments [/asm:C:\Program Files\Windows Server\Bin\BackupServerProvider.dll /class:Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupServerManager /method:DoCleanup /task:Cleanup]

    [2116] 120422.163127.3649: RunTask: AssemblyBasePath = [C:\Program Files\Windows Server\Bin]
    [2116] 120422.163127.3649: RunTask: Load assembly [C:\Program Files\Windows Server\Bin\BackupServerProvider.dll]
    [2116] 120422.163127.3719: RunTask: Non-static method detected.
    [2116] 120422.163127.4489: ProviderFramework: Information: [0] : Register to listen to ProviderRegistryConnectionMgmt connected event.
    [2116] 120422.163127.4559: ProviderFramework: Information: [0] : ProviderRegistryProxy: Beginning connection attempt.
    [2116] 120422.163127.4779: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
    [2116] 120422.163127.5009: ProviderFramework: Information: [0] : ConnectionMgmt: _CreateChannel address generated = [net.tcp://server:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
    [2116] 120422.163127.5049: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
    [2116] 120422.163127.5109: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
    [2116] 120422.163127.5109: ProviderFramework: Information: [0] : Address: [net.tcp://server:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry]
    [2116] 120422.163127.5109: ProviderFramework: Information: [0] : Binding: []
    [2116] 120422.163127.5109: ProviderFramework: Information: [0] : Identifier: []
    [2116] 120422.163127.5109: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [2116] 120422.163127.5109: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [None]
    [2116] 120422.163127.5109: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [2116] 120422.163127.5789: PfBinding: Information: [0] : Adding service dns identity [SERVER] in proxy endpoint.
    [2116] 120422.163127.6659: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [2116] 120422.163127.7499: ProviderFramework: Information: [0] : ConnectAsync was NOT able to synchronously connect to the provider registry.
    [2116] 120422.163127.7799: ProviderFramework: Information: [0] : (current thread: 0x844): PfSynchronizationContext not needed.
    [2116] 120422.163127.7829: ProviderFramework: Information: [0] : ProviderConnector: Querying for provider info: Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider, True, 
    [2116] 120422.163127.7889: Backup: Waiting for connection with the provider.
    [3580] 120422.163127.8459: ProviderFramework: Information: [0] : _OnConnected called.
    [3580] 120422.163127.8479: ProviderFramework: Information: [0] : _CoreConnected is called.
    [8924] 120422.163127.9109: RunTask: AssemblyResolverEventHandler - File [C:\Program Files\Windows Server\Bin\System.Runtime.Serialization.resources.dll] does not exist
    [8924] 120422.163127.9119: RunTask: AssemblyResolverEventHandler - File [C:\Program Files\Windows Server\Bin\System.Runtime.Serialization.resources.dll] does not exist
    [8924] 120422.163127.9479: ProviderFramework: Information: [0] : ProviderConnector: received ProviderInfo Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider net.tcp://server:6602/Microsoft.WindowsServerSolutions.wssg_pc_backup_server/Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [8924] 120422.163127.9519: ProviderFramework: Information: [0] : ProviderConnector: Beginning connection attempt for Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [8924] 120422.163127.9629: ProviderFramework: Information: [0] : CreateWithCallback: Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [8924] 120422.163127.9639: ProviderFramework: Information: [0] : GetDuplexChannelFactory()
    [8924] 120422.163127.9649: ProviderFramework: Information: [0] : Contract: [Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider]
    [8924] 120422.163127.9649: ProviderFramework: Information: [0] : Address: [net.tcp://server:6602/Microsoft.WindowsServerSolutions.wssg_pc_backup_server/Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider]
    [8924] 120422.163127.9649: ProviderFramework: Information: [0] : Binding: [net.tcp]
    [8924] 120422.163127.9649: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.wssg_pc_backup_server]
    [8924] 120422.163127.9649: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [8924] 120422.163127.9649: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [User]
    [8924] 120422.163127.9649: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [8924] 120422.163127.9869: PfBinding: Information: [0] : Setting Windows ClientCredential to , *, 
    [8924] 120422.163127.9869: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [8924] 120422.163128.0149: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [8924] 120422.163128.0209: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.DataProtection.PCBackup.BackupUtil.WcfContracts.IPCBackupServerProvider
    [8924] 120422.163128.0239: Backup: New connection detected. Try fetching all data
    [8924] 120422.163128.0539: Backup: Connected to Provider Successfully
    [2116] 120422.163128.0559: RunTask: Invoke method.
    [7664] 120422.163128.0839: Backup: Got NotifyBackupOperationStatusChange notification 

    The last line is repeated about 50 times.

    I checked a server backup dated long before the KB install and the file was not there.
    • Edited by sbeaudoin Sunday, April 22, 2012 8:48 PM
    Sunday, April 22, 2012 8:27 PM

Answers

  • No, backups are not done on a file name basis but sector content

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    • Marked as answer by sbeaudoin Sunday, April 22, 2012 10:04 PM
    Sunday, April 22, 2012 9:45 PM

All replies

  • Deleting old backups does not necessarily save much space as they are incremental.

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    Sunday, April 22, 2012 9:38 PM
  • I know, but I renamed about 150GB of files two weeks ago.  So I suppose those 150GB could be freed if I delete the backup who contains the old file name.  Because, I suppose a backup as been taken with the old file name and another later with the new file name, doubling the amount of space taken in the backup disk.
    Sunday, April 22, 2012 9:42 PM
  • No, backups are not done on a file name basis but sector content

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.

    • Marked as answer by sbeaudoin Sunday, April 22, 2012 10:04 PM
    Sunday, April 22, 2012 9:45 PM
  • This explains everything.  Thank you.
    Sunday, April 22, 2012 10:04 PM