odlaw_J5
asked on
ntbackup "Disable volume shadow copy"
Hello experts,
I am trying to backup our information store using ntbackup to a USB external hdd.
But when I go to settings the "Disable volume shadow copy" is not available.
All the following services are running and set to automatic, (please let me know if any of this is incorrect or I have missed anything):
- Volume Shadow Copy
- Microsoft Software Shadow Copy Provider
- Remote Procedure Call
- COM+ Event System
- System Event Notification Service
and I have set the usb hdd to "Optimise for performance", but not sure this has any bearing since the issue is there if I try to backup to internal hdd.
but after all that "Disable volume shadow copy" is still greyed out... what gives what givvvves
OS is windows server 2003 std with SP2
Exchange is also 2003
thanks in advance
Jake
I am trying to backup our information store using ntbackup to a USB external hdd.
But when I go to settings the "Disable volume shadow copy" is not available.
All the following services are running and set to automatic, (please let me know if any of this is incorrect or I have missed anything):
- Volume Shadow Copy
- Microsoft Software Shadow Copy Provider
- Remote Procedure Call
- COM+ Event System
- System Event Notification Service
and I have set the usb hdd to "Optimise for performance", but not sure this has any bearing since the issue is there if I try to backup to internal hdd.
but after all that "Disable volume shadow copy" is still greyed out... what gives what givvvves
OS is windows server 2003 std with SP2
Exchange is also 2003
thanks in advance
Jake
ASKER
very very good point,
do you know what , at the very high risk of coming across as dense I'm not to sure now. :(
What happened was, I ran a backup yesterday and it failed part way through and for some reason I wanted to try disabling the VSS......but now typing this out with you it has suddenly dawned on me that the problem was that the service was not running before.......
I'll get my coat.... and go and try the backup again.
it does help to talk though , i'll let you know if it worked and thanks
do you know what , at the very high risk of coming across as dense I'm not to sure now. :(
What happened was, I ran a backup yesterday and it failed part way through and for some reason I wanted to try disabling the VSS......but now typing this out with you it has suddenly dawned on me that the problem was that the service was not running before.......
I'll get my coat.... and go and try the backup again.
it does help to talk though , i'll let you know if it worked and thanks
You're welcome :)
I'm awaiting for further information :) and yes, sometimes short chat allows to review the issue once again with fresh eye ;)
So, in meantime I would also suggest you to see VSS writers status in command-line
and see their status
Krzysztof
I'm awaiting for further information :) and yes, sometimes short chat allows to review the issue once again with fresh eye ;)
So, in meantime I would also suggest you to see VSS writers status in command-line
vssadmin list writers
and see their status
Krzysztof
ASKER
Well the first backup came up with "an inconsistency was encountered in the requested backup".
I then tried splitting it into 2 backups; first I backed up the public store which succeeded.
I then tried the mailbox store and that succeeded as well.
SO all seems ok.
Many many thanks Krzysztof for reading (listening) and helping me out,
I ran vssadmin list writers and the result was:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>vss admin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1 050253ae22 0}
Writer Instance Id: {0b246023-c487-4f57-bbbd-2 9f12355142 2}
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2 958fb88ce2 9}
Writer Instance Id: {1aebd4a8-c8db-43c3-b676-b cb527735ad 6}
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3 cf38448475 7}
Writer Instance Id: {7bd94f07-0458-4481-99f2-b 652af6cfe9 d}
State: [1] Stable
Last error: No error
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6 c267a62974 1}
Writer Instance Id: {92a2081d-e63e-4b81-8106-f 94d3881347 1}
State: [1] Stable
Last error: No error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-6 3063e3a1f8 6}
Writer Instance Id: {07dc9974-6d9d-4f26-b2c8-8 91fc35ff06 5}
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-3 90603070d0 0}
Writer Instance Id: {f224137a-4c57-401d-8a8b-f 468da80912 a}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6 ca8b293836 6}
Writer Instance Id: {2034a613-050e-49e4-9bad-2 8d9458c6e3 9}
State: [1] Stable
Last error: No error
Writer name: 'TermServLicensing'
Writer Id: {5382579c-98df-47a7-ac6c-9 8a6d7106e0 9}
Writer Instance Id: {2864dfd7-105f-47e7-92f5-e fbac254f21 0}
State: [1] Stable
Last error: No error
Writer name: 'Removable Storage Manager'
Writer Id: {5d3c3e01-0297-445b-aa81-a 48d7151e23 5}
Writer Instance Id: {46fe9f1d-ad12-4408-9cbb-8 6450b48b1a b}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f 328f07ac1e 0}
Writer Instance Id: {26eb6f71-e596-4346-89bf-2 c72b3189a0 e}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4 9d8f43532f 0}
Writer Instance Id: {b12f4993-fb82-400e-8c54-8 eb34d1bd67 c}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8 e1acb462fb 7}
Writer Instance Id: {11c5be87-68b7-4d0a-a445-7 fef7b3b3c5 9}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7 847f01fc64 f}
Writer Instance Id: {7e99cb99-bd1b-4fda-a36c-8 984deeb36e 8}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7 1dbb18f848 5}
Writer Instance Id: {15b02925-baa3-4a9b-b2a8-7 58aeb53128 d}
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f 7ee00b0327 7}
Writer Instance Id: {09e0a042-e15b-4502-a0ab-4 3f1bbae75f 8}
State: [1] Stable
Last error: No error
I then tried splitting it into 2 backups; first I backed up the public store which succeeded.
I then tried the mailbox store and that succeeded as well.
SO all seems ok.
Many many thanks Krzysztof for reading (listening) and helping me out,
I ran vssadmin list writers and the result was:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>vss
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1
Writer Instance Id: {0b246023-c487-4f57-bbbd-2
State: [1] Stable
Last error: No error
Writer name: 'FRS Writer'
Writer Id: {d76f5a28-3092-4589-ba48-2
Writer Instance Id: {1aebd4a8-c8db-43c3-b676-b
State: [1] Stable
Last error: No error
Writer name: 'NTDS'
Writer Id: {b2014c9e-8711-4c5c-a5a9-3
Writer Instance Id: {7bd94f07-0458-4481-99f2-b
State: [1] Stable
Last error: No error
Writer name: 'WINS Jet Writer'
Writer Id: {f08c1483-8407-4a26-8c26-6
Writer Instance Id: {92a2081d-e63e-4b81-8106-f
State: [1] Stable
Last error: No error
Writer name: 'Certificate Authority'
Writer Id: {6f5b15b5-da24-4d88-b737-6
Writer Instance Id: {07dc9974-6d9d-4f26-b2c8-8
State: [1] Stable
Last error: No error
Writer name: 'Event Log Writer'
Writer Id: {eee8c692-67ed-4250-8d86-3
Writer Instance Id: {f224137a-4c57-401d-8a8b-f
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6
Writer Instance Id: {2034a613-050e-49e4-9bad-2
State: [1] Stable
Last error: No error
Writer name: 'TermServLicensing'
Writer Id: {5382579c-98df-47a7-ac6c-9
Writer Instance Id: {2864dfd7-105f-47e7-92f5-e
State: [1] Stable
Last error: No error
Writer name: 'Removable Storage Manager'
Writer Id: {5d3c3e01-0297-445b-aa81-a
Writer Instance Id: {46fe9f1d-ad12-4408-9cbb-8
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f
Writer Instance Id: {26eb6f71-e596-4346-89bf-2
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-4
Writer Instance Id: {b12f4993-fb82-400e-8c54-8
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Exchange Writer'
Writer Id: {76fe1ac4-15f7-4bcd-987e-8
Writer Instance Id: {11c5be87-68b7-4d0a-a445-7
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7
Writer Instance Id: {7e99cb99-bd1b-4fda-a36c-8
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-7
Writer Instance Id: {15b02925-baa3-4a9b-b2a8-7
State: [1] Stable
Last error: No error
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f
Writer Instance Id: {09e0a042-e15b-4502-a0ab-4
State: [1] Stable
Last error: No error
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
However, if your Windows Server 2003 is after SP1 then it is not available anymore
http://support.microsoft.com/kb/104169
Regards,
Krzysztof