Forum Discussion
Can you post the bpbkar log?
Also, when loading the page for your post, the sidebar showed a few posts with error 69 mentioned. One of them talks about tech note: http://www.veritas.com/docs/000017926 Check that too.
As your problem seems to be related to VSS/System state this blog:
might be of help. In my experience most often the problem is a too small shadow storage area.
- haboulainain8 years agoLevel 3
I tried many things:
1) I checked the VSS Writers: (all good):vssadmin list writersvssadmin 1.1 - Volume Shadow Copy Service administrative command-
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {6f2cc347-8109-45b5-a9b5-bcb3a45a1816}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {b6e524b8-04a5-406c-8153-0a0187317e5b}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {8e3b348b-086f-40e7-a963-44a5fed92bf1}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {7a0504c6-6770-473d-a3d7-b6f87b764db7}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {5312c4be-1c60-4162-a3d8-aaac86c70890}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {9ef4cbe3-3a82-4645-9e20-425cc0997a51}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {f0da1a64-6376-40d5-a725-60671f9dc9ac}
State: [1] Stable
Last error: No error
Writer name: 'Dhcp Jet Writer'
Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
Writer Instance Id: {86e1afd4-3f48-448a-981d-b239fbd8879a}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {d97a0e4e-8db6-4d05-970b-b2a3e6358911}
State: [1] Stable
Last error: No error
2) I checked the VSS provider (all good)
vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
3) There are volumes that exceed 62 TB, I extended the registry key value HKEY_LOCAL_MACHINE \ SOFTWARE \ Veritas \ NetBackup \ BEDS \ Engine \ Misc \ BescLargeDiscBlock to 68 and I started the job but still the same thing
https://www.veritas.com/support/en_US/article.TECH206217
4) To registre the VSS, the OS is already Windows 2008 R2 SP1 (so Nothing to do)
https://www.veritas.com/support/en_US/article.000015843
5) I rebooted the server several times, but still the same problem
Version: 1.0.0.7
- Lowell_Palecek8 years agoLevel 6
Is this the most verbose bpbkar log you can provide? For example, bpbkar enumerates the providers.
Michael suggested that you may not have enough space allocated to snap the G: drive. You can use vssadmin to answer check your snapshot limit.
You migrated to 7.6.0.4? Why not 7.7.x?
- haboulainain8 years agoLevel 3
Hello Lowell_palecek,
I already configured No limit in shodow copie setting for G.
We did not migrate directly to 7.7, because we tried to avoid the conversion of segments deduplication twice, it will be scheduled for a later time
- X28 years agoModerator
There seems to be something missing from the end of your last post.
One more question: have you noticed anything on the server (being backed up) at the time the backup fails in event logs?
also, check out what Michael linked above.
- Marianne8 years agoLevel 6
Have you tried to backup SCC using Windows Backup utility?
Related Content
- 2 years ago