Developing a VSS writer app:
see this error during backup, initiated by windows backup tool,
is there defined error codes for 2155348129 from Microsoft?
The backup operation that started at ‘2010-07-20T02:54:19.354000000Z’ has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code ‘2155348129’
This does not happen when VSSwriter service (my application) is stopped.
Any help is appreciated. Nothing useful found on TechNet.
Hackish workaround:
Interestingly the back up works is when «windows partition is made active». Of course this leaves the system non-boot-able upon restart
asked Jul 20, 2010 at 14:20
3
Sharepoint Foundation is causing the issue. By running the «Sharepoint 2010 Products Configuration Wizard», it will fix the backup issue.
answered Aug 22, 2011 at 16:57
I had a similar problem with VSS errors vs a SBS backup.
Wasn’t low disk space in my case
Dell Pro Support (very good) discounted the issue being with the HDD configuration which is referred to all over the www. They did say to watch out for HDDs that are very low on space causing VSS issues for Server backup but this was not the case.
Check VSS writer status
My Fix:
Run vssadmin list writers and see if they have stalled as part of the backup. A reboot or two should set these back to normal. Try a backup now.
Check to see if any SharePoint updates are causing the issue. Run the SharePoint Configuration Wizard from the start menu (Next, Next, Finish), reboot and rerun the backup.
Hope this helps someone else out there — let me know if you need any more info.
www.mtechnical.co.uk
answered Jul 11, 2011 at 15:37
I had a SQL server installed. With too many databases. When I deleted some databases the error went away and the backup could continue as normal.
answered Feb 21, 2014 at 10:05
The answer by mtechnical put me on the right track, sorry don’t have enough rep to vote you up.
Cause was SharePoint VSS writer
Basically vssadmin list writers allowed me me to see that SPSearch4 VSS Writer was holding everything up with an inconsistent shadow copy error and a few quick Google searches later I was all good.
Hopefully that helps you get to where you need to be.
Underlying cause was SharePoint Service Pack
In case anyone else gets here due to backup failing with SBS 2011 even on a clean install with all patches, the cause is due to the SharePoint Server service pack. To resolve run the Sharepoint 2010 Products Configuration Wizard. And after that you should be able to re-run vssadmin list writers and see all errors are cleared.
Cheers
Kactus
answered Jul 15, 2011 at 6:39
KactusKactus
1237 bronze badges
- Remove From My Forums
-
Question
-
I have been crawling >100’s of forums for a week trying to find a solution to this problem and I am now beyond frustrated. This problem is so circumstantial to individual machines. I read that someone fixed this issue and how they resolved it but that
fix doesn’t apply to my situation. So please understand that I have searched very hard and long for a solution to my backup failure and this is my last hope.I am a teacher and have limited resources, so I built a server on a PC that served its purpose and we have now outgrown its hardware capabilities. I have built a new machine to use as my server. I have a domain with 20 PC’s, 72 users with redirected Desktop
and Documents using my policy. I have a C:\ OS Volume that is set as Active, D:\ that is the working drive. I looked up Server Migration and all signs pointed to do a Full System Backup and BMR to the new server, so that is what I am trying to do with no success.I have tried that 45GB Backup to my USB HDD that is a .5TB and to a network share to a drive that is 160G.
Old server is a Server 2008 Standard 32-bit with SP2.
Under Application Log, the Error is: Backup started at ‘9/20/2011 7:24:12 PM’ failed as Volume Shadow copy operation failed for backup volumes with following error code ‘2155348129’. Please rerun backup once issue is resolved.
Under Backup/Operational Log, the Error is: Backup started at ‘{d5f7dbb2-37e6-4cd3-9544-2eb0891a6b2d}’ failed as Volume Shadow copy operation failed for backup volumes with following error code ‘2155348129’.
I ran «vssadmin list writers» and the ‘NTDS’ Writer has a Non-retryable error. I was unable to find a resource detailing how to repair this error…
I am not running an SQL server. I disable the AV service, started the Volume Shadow Copy and set it to Automatic.
The Status from Details — Last Backup: Failed; A Volume Shadow Copy Service operation failed. Detailed Error: The volume shadow copy operation failed with error 0x800423F4. View the event log for more details.
I am at the end of my rope and considering tying it in to a noose.
Answers
-
Hi,
Firstly, I have seen that there are several errors in «VSS writers», I suspect that it maybe the problem.
Generally speaking, you can try the following steps when encountering VSS writer related issues:
1. Retry the backup or restore operation that caused the error condition.
2. If this does not resolve the issue, restart the service or process that hosts the writer, and retry the operation.
3. If this does not resolve the issue, open Event Viewer as described in the «Open Event Viewer and view events related to VSS» section and look
for events related to the service or process that hosts the writer. If necessary, restart the service or process, and retry the operation.
4. If this does not resolve the issue, restart the computer, and retry the operation.
5. If restarting the computer does not resolve the issue, provide the Event Viewer information to the vendor whose application is indicated in
the event text.For more information ,please refer to :
http://technet.microsoft.com/en-us/library/ee264212(WS.10).aspx
If you does not resolve the issue through above method, you can try to re-register the VSS writers, you can refer to :
http://www.symantec.com/business/support/index?page=content&id=TECH70486
secondly, if it still can’t works, please take the following steps and see whether it can works.
1) Uninstall antivirus.
2) Re-install Windows Server Backup role.
3) Check and uninstall any third party Backup Software.
For the rest:
As we know, the system partition should be marked Active so that the Windows Server Backup can read information there. However, sometimes when we create the partition and
install the operating system with OEM tools (ex. Intel Embedded Server RAID II) , the OEM partition will be created and marked active. This could cause this backup failure.I don’t know if it is related to your OEM issues, please check it.
Best regards,
Jeff Ren
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
-
Edited by
Thursday, September 22, 2011 8:41 AM
-
Proposed as answer by
Jeff Ren
Monday, September 26, 2011 2:10 AM -
Marked as answer by
Jeff Ren
Monday, September 26, 2011 2:36 AM
-
Edited by
У меня была аналогичная проблема с ошибками VSS в сравнении с резервной копией SBS.
В моем случае это не было связано с нехваткой дискового пространства.
Служба поддержки Dell Pro Support (очень хорошая) отказалась признать, что проблема связана с конфигурацией жесткого диска, на которую ссылаются по всему www. Они сказали, что нужно следить за жесткими дисками, на которых очень мало места, что вызывает проблемы с VSS при резервном копировании сервера, но это был не тот случай.
Проверить статус записи VSS
Мое решение:
Запустите vssadmin list writers и посмотрите, не застопорились ли они в процессе резервного копирования. Перезагрузка или две перезагрузки должны вернуть их в нормальное состояние. Попробуйте выполнить резервное копирование сейчас.
Проверьте, не вызвали ли проблему обновления SharePoint. Запустите SharePoint Configuration Wizard из стартового меню (Next, Next, Finish), перезагрузитесь и повторно запустите резервное копирование.
Надеюсь, это поможет кому-то еще — дайте мне знать, если вам нужна дополнительная информация.
www.mtechnical.co.uk
разработка приложения VSS writer:
см. эту ошибку во время резервного копирования, инициированного средством резервного копирования windows,
есть ли определенные коды ошибок для 2155348129 от Microsoft?
операция резервного копирования, которая началась с «2010-07-20T02:54: 19.354000000 Z» не удалось, потому что операция Службы теневого копирования томов для создания теневой копии томов резервного копирования не удалось со следующим кодом ошибки «2155348129»
этого не происходит, когда VSSwriter служба (мое приложение) остановлена.
любая помощь приветствуется. Ничего полезного не найдено на TechNet.
Hackish обходной путь:
Интересно, что резервное копирование работает, когда «раздел windows активен». Конечно, это оставляет систему без загрузки после перезагрузки
6 ответов
у меня была аналогичная проблема с ошибками VSS против резервной копии SBS.
не хватает свободного дискового пространства в моем случае
поддержка Dell Pro (очень хорошая) со скидкой на проблему с конфигурацией HDD, которая упоминается во всем www. Они сказали, чтобы следить за HDDs, которые очень мало места, вызывая проблемы VSS для резервного копирования сервера, но это не так.
проверьте состояние VSS writer
Мое Решение:
Запустить vssadmin list writers и посмотреть, есть ли у них застрял как часть резервной копии. Перезагрузка или две должны вернуть их в нормальное состояние. Попробуйте сделать резервную копию.
Проверьте, не являются ли какие-либо обновления SharePoint причиной проблемы. Запустите SharePoint Configuration Wizard в меню Пуск (далее, Далее, Готово) перезагрузите и повторно запустите резервную копию.
надеюсь, это поможет кому — то еще-дайте мне знать, если вам нужна дополнительная информация.
www.mtechnical.co.uk
Sharepoint Foundation вызывает проблему. Запустив «мастер настройки продуктов Sharepoint 2010», он устранит проблему резервного копирования.
У меня был установлен SQL server. Слишком много баз данных. Когда я удалил некоторые базы данных, ошибка исчезла, и резервное копирование могло продолжаться как обычно.
на ответ mtechnical поставьте меня на правильный путь, извините, не хватает репутации, чтобы проголосовать за вас.
причиной был SharePoint VSS writer
в принципе vssadmin list writers позволил мне увидеть это SPSearch4 VSS Writer держал все вверх с inconsistent shadow copy ошибка и несколько быстрых поисков Google позже я был все хорошо.
надеюсь, это поможет вам добраться туда, где вам нужно быть.
основной причиной была служба SharePoint Пак
в случае, если кто-то еще попадает сюда из-за сбоя резервного копирования с SBS 2011 даже при чистой установке со всеми патчами, причина связана с SharePoint Server service pack. Чтобы разрешить запуск Sharepoint 2010 Products Configuration Wizard. И после этого вы должны быть в состоянии повторно запустить vssadmin list writers и увидеть, что все ошибки очищены.
Ура
Kactus
Error when you click on SBS Console — A Volume Shadow Copy Service operation failed. Unknown error (0x800423f4).
Or Server Backup did not finish successfully on 18/12/2016 7:01 PM. See the Event Log for details.
Then on Event Viewer Applications and Services Logs -> Microsoft -> Windows -> Backup -> Operations, error is “Backup started at ’18/12/2016 7:00:00 PM’ failed as Volume Shadow copy operation failed for backup volumes with following error code ‘2155348129’. Please rerun backup once issue is resolved.” with Event ID 9.
Or Backup started at ‘{726fef76-17ae-4966-b054-57c55906d367}’ failed as Volume Shadow copy operation failed for backup volumes with following error code ‘2155348129’. with Event ID 9.
Solution:
- Restart Com+ Event System and Volume Shadow Copy.
Also, restart the Microsoft Exchange Information Store service if you are using BackupAssist with Granular Exchange module.
Also, restart the Cryptographic Services (which is the System Witer) if you are doing Windows system state backup. - Run vssadmin list writers, and make sure result is not empty. Below is the appropriate result of vssasmin list writers, to have a successful backup before and after an SBS built-in Backup.
If you get an error NTDS (Non-retryable error), NPS (not stable) – just try to restart the Com+ Event System service. No need to restart the server because you will get same error re. NTDS anyway.
- Issue a backup once with Custom (VSS Full option enabled). Then the next scheduled backup should be successful.