Backup windows server 2008 fails - shadow copy
I want to back up my Windows Server, but it fails when making shadow copy. I have seen that it only fails when I want to make a complete backup of the system (and not if I select only D or E drive).
I think that the problem is the empty 100 MB system drive that is not NTFS. Any ideas? There could be also another reason.
I use Windows backup tool; see error messages in tool and event log: screenshots
I do total system back up but I will also backup drives seperately in the future
drive partitions
Backup tool error
Event log error
windows backup ntfs windows-server-2008 windows-server-2008-r2
asked Dec 19 '18 at 10:40
KonoKono
13
add a comment |
I want to back up my Windows Server, but it fails when making shadow copy. I have seen that it only fails when I want to make a complete backup of the system (and not if I select only D or E drive).
I think that the problem is the empty 100 MB system drive that is not NTFS. Any ideas? There could be also another reason.
I use Windows backup tool; see error messages in tool and event log: screenshots
I do total system back up but I will also backup drives seperately in the future
drive partitions
Backup tool error
Event log error
windows backup ntfs windows-server-2008 windows-server-2008-r2
asked Dec 19 '18 at 10:40
KonoKono
13
2
You should edit your original post, not delete it and create a new one.
– Keltari
Dec 19 '18 at 10:45
Just in case it's applicable or helpful to the issue, read over support.microsoft.com/en-us/help/970770/…
– Pimp Juice IT
Dec 19 '18 at 15:03
add a comment |
I want to back up my Windows Server, but it fails when making shadow copy. I have seen that it only fails when I want to make a complete backup of the system (and not if I select only D or E drive).
I think that the problem is the empty 100 MB system drive that is not NTFS. Any ideas? There could be also another reason.
I use Windows backup tool; see error messages in tool and event log: screenshots
I do total system back up but I will also backup drives seperately in the future
drive partitions
Backup tool error
Event log error
windows backup ntfs windows-server-2008 windows-server-2008-r2
asked Dec 19 '18 at 10:40
KonoKono
13
I want to back up my Windows Server, but it fails when making shadow copy. I have seen that it only fails when I want to make a complete backup of the system (and not if I select only D or E drive).
I think that the problem is the empty 100 MB system drive that is not NTFS. Any ideas? There could be also another reason.
I use Windows backup tool; see error messages in tool and event log: screenshots
I do total system back up but I will also backup drives seperately in the future
drive partitions
Backup tool error
Event log error
windows backup ntfs windows-server-2008 windows-server-2008-r2
windows backup ntfs windows-server-2008 windows-server-2008-r2
asked Dec 19 '18 at 10:40
KonoKono
13
asked Dec 19 '18 at 10:40
KonoKono
13
asked Dec 19 '18 at 10:40
KonoKono
13
asked Dec 19 '18 at 10:40
KonoKono
13
asked Dec 19 '18 at 10:40
KonoKono
13
13
2
You should edit your original post, not delete it and create a new one.
– Keltari
Dec 19 '18 at 10:45
Just in case it's applicable or helpful to the issue, read over support.microsoft.com/en-us/help/970770/…
– Pimp Juice IT
Dec 19 '18 at 15:03
add a comment |
2
You should edit your original post, not delete it and create a new one.
– Keltari
Dec 19 '18 at 10:45
Just in case it's applicable or helpful to the issue, read over support.microsoft.com/en-us/help/970770/…
– Pimp Juice IT
Dec 19 '18 at 15:03
2
2
You should edit your original post, not delete it and create a new one.
– Keltari
Dec 19 '18 at 10:45
You should edit your original post, not delete it and create a new one.
– Keltari
Dec 19 '18 at 10:45
Just in case it's applicable or helpful to the issue, read over support.microsoft.com/en-us/help/970770/…
– Pimp Juice IT
Dec 19 '18 at 15:03
Just in case it's applicable or helpful to the issue, read over support.microsoft.com/en-us/help/970770/…
– Pimp Juice IT
Dec 19 '18 at 15:03
add a comment |
2 Answers
2
active
oldest
votes
Further checks:
- Check disk space.
- Run the command
vssadmin list writersin an elevated cmd and see if any
writer is listed as having an error. - See if Volume Shadow Copy Service and Shared Protection Point added messages
to the Windows application event log
(they use VSS and SPP as their event-Source-identifier).
If you can't find any error, this might be a temporary timeout.
You may increase the timeout using regedit and navigating to:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionSPP
Create a new DWORD value named CreateTimeout and set its value.
For example, 2 minutes is 1200000 (2*60*1000) in decimal,
but set your own.
If the registry key SPP does not exist, then this advice does not apply.
Source: Microsoft blog.
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
Comments are not for extended discussion; this conversation has been moved to chat.
– DavidPostill♦
Dec 20 '18 at 17:00
add a comment |
I fixed this issue by starting backups without SQL server services.Just stop all SQL related services. Thanks for your help!
answered Dec 26 '18 at 10:06
KonoKono
13
add a comment |
protected by Community♦ Dec 29 '18 at 3:43
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Further checks:
- Check disk space.
- Run the command
vssadmin list writersin an elevated cmd and see if any
writer is listed as having an error. - See if Volume Shadow Copy Service and Shared Protection Point added messages
to the Windows application event log
(they use VSS and SPP as their event-Source-identifier).
If you can't find any error, this might be a temporary timeout.
You may increase the timeout using regedit and navigating to:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionSPP
Create a new DWORD value named CreateTimeout and set its value.
For example, 2 minutes is 1200000 (2*60*1000) in decimal,
but set your own.
If the registry key SPP does not exist, then this advice does not apply.
Source: Microsoft blog.
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
Comments are not for extended discussion; this conversation has been moved to chat.
– DavidPostill♦
Dec 20 '18 at 17:00
add a comment |
Further checks:
- Check disk space.
- Run the command
vssadmin list writersin an elevated cmd and see if any
writer is listed as having an error. - See if Volume Shadow Copy Service and Shared Protection Point added messages
to the Windows application event log
(they use VSS and SPP as their event-Source-identifier).
If you can't find any error, this might be a temporary timeout.
You may increase the timeout using regedit and navigating to:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionSPP
Create a new DWORD value named CreateTimeout and set its value.
For example, 2 minutes is 1200000 (2*60*1000) in decimal,
but set your own.
If the registry key SPP does not exist, then this advice does not apply.
Source: Microsoft blog.
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
Comments are not for extended discussion; this conversation has been moved to chat.
– DavidPostill♦
Dec 20 '18 at 17:00
add a comment |
Further checks:
- Check disk space.
- Run the command
vssadmin list writersin an elevated cmd and see if any
writer is listed as having an error. - See if Volume Shadow Copy Service and Shared Protection Point added messages
to the Windows application event log
(they use VSS and SPP as their event-Source-identifier).
If you can't find any error, this might be a temporary timeout.
You may increase the timeout using regedit and navigating to:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionSPP
Create a new DWORD value named CreateTimeout and set its value.
For example, 2 minutes is 1200000 (2*60*1000) in decimal,
but set your own.
If the registry key SPP does not exist, then this advice does not apply.
Source: Microsoft blog.
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
Further checks:
- Check disk space.
- Run the command
vssadmin list writersin an elevated cmd and see if any
writer is listed as having an error. - See if Volume Shadow Copy Service and Shared Protection Point added messages
to the Windows application event log
(they use VSS and SPP as their event-Source-identifier).
If you can't find any error, this might be a temporary timeout.
You may increase the timeout using regedit and navigating to:
HKEY_LOCAL_MACHINESoftwareMicrosoftWindows NTCurrentVersionSPP
Create a new DWORD value named CreateTimeout and set its value.
For example, 2 minutes is 1200000 (2*60*1000) in decimal,
but set your own.
If the registry key SPP does not exist, then this advice does not apply.
Source: Microsoft blog.
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
answered Dec 19 '18 at 11:50
harrymcharrymc
255k14265566
255k14265566
Comments are not for extended discussion; this conversation has been moved to chat.
– DavidPostill♦
Dec 20 '18 at 17:00
add a comment |
Comments are not for extended discussion; this conversation has been moved to chat.
– DavidPostill♦
Dec 20 '18 at 17:00
Comments are not for extended discussion; this conversation has been moved to chat.
– DavidPostill♦
Dec 20 '18 at 17:00
Comments are not for extended discussion; this conversation has been moved to chat.
– DavidPostill♦
Dec 20 '18 at 17:00
add a comment |
I fixed this issue by starting backups without SQL server services.Just stop all SQL related services. Thanks for your help!
answered Dec 26 '18 at 10:06
KonoKono
13
add a comment |
I fixed this issue by starting backups without SQL server services.Just stop all SQL related services. Thanks for your help!
answered Dec 26 '18 at 10:06
KonoKono
13
add a comment |
I fixed this issue by starting backups without SQL server services.Just stop all SQL related services. Thanks for your help!
answered Dec 26 '18 at 10:06
KonoKono
13
I fixed this issue by starting backups without SQL server services.Just stop all SQL related services. Thanks for your help!
answered Dec 26 '18 at 10:06
KonoKono
13
answered Dec 26 '18 at 10:06
KonoKono
13
answered Dec 26 '18 at 10:06
KonoKono
13
answered Dec 26 '18 at 10:06
KonoKono
13
13
add a comment |
add a comment |
protected by Community♦ Dec 29 '18 at 3:43
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
2
You should edit your original post, not delete it and create a new one.
– Keltari
Dec 19 '18 at 10:45
Just in case it's applicable or helpful to the issue, read over support.microsoft.com/en-us/help/970770/…
– Pimp Juice IT
Dec 19 '18 at 15:03