Дмитрий Максимов (dmitry_maximov) wrote,
Дмитрий Максимов

как это бывает

1. При попытке бэкапить виртуальную машину Hyper-V на DPM 2010 при помощи Backup Using Child Partition Snapshot вываливается ошибка:

DPM encountered a retryable VSS error. (ID 30112 Details: VssError:The writer experienced a transient error. If the backup process is retried,
the error may not reoccur.

2. Гуглим

3. Со временем находим http://chicagotech.net/netforums/viewtopic.php?f=3&t=15798&sid=de74b1ef0dba373e5de228436158f900#p24409. Там написано:

The retryable VSS error can also occur if there is a problem with one of the VSS writers within the VM itself (e.g. writer in a failed/retryable state). Have you executed the "vssadmin.exe list writers" command within the problem VM?

4. делаем, что сказано, получаем, что все ок, кроме:

Writer name: 'SPSearch4 VSS Writer'
Writer Id: {35500004-0201-0000-0000-000000000000}
Writer Instance Id: {4aa57128-be13-4d43-a379-9b8ec524701b}
State: [8] Failed
Last error: Inconsistent shadow copy

5. Удивляемся, лезем в Application log, находим:

The Execute method of job definition Microsoft.SharePoint.Search.Administration.SPSearchJobDefinition (ID dc13bcc0-6c9b-4241-ae1b-88d219898ae1) threw an exception. More information is included below.

The device is not ready.


The mount operation for the gatherer application 06a326ab-9e6d-4ed2-a640-c24cf9f7c3f7 has failed because the schema version of the search administration database is less than the minimum backwards compatibility schema version supported for this gatherer application. The database might not have been upgraded.

6. удивляемся, гуглим дальше. Находим http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-after-installing-sharepoint-foundation-2010-sp1.aspx. Читаем:

Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1) was recently released through Microsoft Update. On a default installation, Windows SBS 2011 Standard administrators should be able to see it in the SBS Console and would need to approve it for installation before it is offered for installation on the server.

Since SharePoint Foundation 2010, patching SharePoint is a two-step process. The updated binaries are first installed and then PSCONFIG must be completed to update the SharePoint databases.
Without completing PSCONFIG, you might experience unexpected SharePoint search failures and all backups may stop working on the affected server.


7. дальше просто. Проверяем

(get-spserver $env:computername).NeedsUpgrade в консоли Sharepoint. получаем True. Наш вариант.

8. чиним. Идем в %ProgramFiles%\Common Files\Microsoft Shared\Web Server Extensions\14\BIN и запускаем PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures. Ждем завершения.

9. Запускаем бэкап. PROFIT!
Tags: работа
  • Post a new comment


    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.