Backup Exec 2010 VSS error

Marcusolini

  Thanx for the reply, and finally, there is something that makes sense.  I had never heard of that 4k block size issues, but after reading up on Microsoft, it looks like it may be an issue.

   The microsoft notice directed installing some patches, but does anyone know if it would fix things to simply reformat the drive down to 512k block sizes?

    Unfortunately, another exchange on another help site pointed out the Advanced Open File wizard and to check permissions.  When I did, It tells me the Advanced Open File is not installed correctly, and the best solution is to uninstall BE 2010 and reinstall.  I have uninstalled BE2010, but that requries a reboot, which I will do tonight, then reinstall and try again with the AOF options.  If that fails, Ill try either reformatting the USB drive, or installing the microsoft patches.

Ill let you know what I find.

Unfortunately, all of the described approaches will not help.  The MSFT updates will not address the issues you have been experiencing.  There is no way to perform a low-level reformat of the disk to be a legacy 512 byte sector size.   The Backup Exec Advanced Open File Open message pertains to the Symantec Volume Snapshot Provider (VSP), for which a reinstall may correct the AOFO message but will not address the originally experienced issues.

I might be able to provide an alternate suggestion.  When able, please execute the following command-line utilities and attach the output to this post for review.   Ensure the USB drive is NOT attached when executing the commands.  Thank you.

(1)  C:\>VSSADMIN LIST VOLUMES

(2)  C:\>VSSADMIN LIST WRITERS

(3)  C:\>VSSADMIN LIST PROVIDERS

(4)  C:\>VSSADMIN LIST SHADOWS

(5)  C:\>VSSADMIN LIST SHADOWSTORAGE

(6)  C:\>BCDEDIT /ENUM ALL

(7)  C:\>MOUNTVOL

(8)  C:\>DISKPART

(8)(a)   DISKPART> LIST DISK

(8)(b)   DISKPART> LIST VOLUME

(8)(c)   DISKPART> exit

Marcusolini, here are the results of the commands.  Let me know if it tells you anything useful:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>vssadmin list volumes
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Volume path: F:\
    Volume name: \\?\Volume{90601b11-d301-42bf-ace4-5fc027be3c56}\
Volume path: Z:\
    Volume name: \\?\Volume{d08ac883-a1b6-11df-b853-806e6f6e6963}\
Volume path: G:\
    Volume name: \\?\Volume{1cbca1aa-a549-494d-8f30-7ca6bb0bad0a}\
Volume path: C:\
    Volume name: \\?\Volume{d08ac884-a1b6-11df-b853-806e6f6e6963}\
Volume path: D:\
    Volume name: \\?\Volume{d08ac885-a1b6-11df-b853-806e6f6e6963}\
Volume path: E:\
    Volume name: \\?\Volume{d08ac886-a1b6-11df-b853-806e6f6e6963}\

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(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: {ad8086f7-76e0-47dd-b6ce-0b2a7baf5610}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {34244e92-5876-4e94-bafb-a83a26280a47}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {c522e2aa-d418-4330-b5ee-fd79ad3e003d}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {a4da8359-07d5-49d7-b007-c85d44d4a855}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {429f676b-2101-4aac-946c-9ef7ddc31350}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {93af4f27-b209-4472-81bc-7f9539d2ced5}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {63f3e100-f167-4e63-a3af-c149c54eb4fc}
   State: [1] Stable
   Last error: No error
 

c:\temp>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}
   Version: 1.0.0.7

vssadmin list shadows: huge output, so attached as a file

c:\temp>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.

Shadow Copy Storage association
   For volume: (F:)\\?\Volume{90601b11-d301-42bf-ace4-5fc027be3c56}\
   Shadow Copy Storage volume: (F:)\\?\Volume{90601b11-d301-42bf-ace4-5fc027be3c
56}\
   Used Shadow Copy Storage space: 2.389 GB (0%)
   Allocated Shadow Copy Storage space: 5.275 GB (0%)
   Maximum Shadow Copy Storage space: UNBOUNDED (614797768%)

Shadow Copy Storage association
   For volume: (C:)\\?\Volume{d08ac884-a1b6-11df-b853-806e6f6e6963}\
   Shadow Copy Storage volume: (C:)\\?\Volume{d08ac884-a1b6-11df-b853-806e6f6e69
63}\
   Used Shadow Copy Storage space: 5.539 GB (9%)
   Allocated Shadow Copy Storage space: 5.836 GB (9%)
   Maximum Shadow Copy Storage space: 5.85 GB (10%)

Shadow Copy Storage association
   For volume: (D:)\\?\Volume{d08ac885-a1b6-11df-b853-806e6f6e6963}\
   Shadow Copy Storage volume: (D:)\\?\Volume{d08ac885-a1b6-11df-b853-806e6f6e69
63}\
   Used Shadow Copy Storage space: 1.23 GB (0%)
   Allocated Shadow Copy Storage space: 1.877 GB (1%)
   Maximum Shadow Copy Storage space: 14.648 GB (10%)

Shadow Copy Storage association
   For volume: (E:)\\?\Volume{d08ac886-a1b6-11df-b853-806e6f6e6963}\
   Shadow Copy Storage volume: (E:)\\?\Volume{d08ac886-a1b6-11df-b853-806e6f6e69
63}\
   Used Shadow Copy Storage space: 5 GB (0%)
   Allocated Shadow Copy Storage space: 7.915 GB (1%)
   Maximum Shadow Copy Storage space: 72.643 GB (10%)

c:\temp>bcdedit /enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=Z:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {25ed8223-a1b9-11df-8bfb-9a91bfde8eb5}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {25ed8221-a1b9-11df-8bfb-9a91bfde8eb5}
device                  ramdisk=[C:]\Recovery\25ed8221-a1b9-11df-8bfb-9a91bfde8e
b5\Winre.wim,{25ed8222-a1b9-11df-8bfb-9a91bfde8eb5}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\25ed8221-a1b9-11df-8bfb-9a91bfde8e
b5\Winre.wim,{25ed8222-a1b9-11df-8bfb-9a91bfde8eb5}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows Server 2008 R2
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {25ed8225-a1b9-11df-8bfb-9a91bfde8eb5}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {25ed8223-a1b9-11df-8bfb-9a91bfde8eb5}
nx                      OptOut

Windows Boot Loader
-------------------
identifier              {25ed8225-a1b9-11df-8bfb-9a91bfde8eb5}
device                  ramdisk=[C:]\Recovery\25ed8225-a1b9-11df-8bfb-9a91bfde8e
b5\Winre.wim,{25ed8226-a1b9-11df-8bfb-9a91bfde8eb5}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\25ed8225-a1b9-11df-8bfb-9a91bfde8e
b5\Winre.wim,{25ed8226-a1b9-11df-8bfb-9a91bfde8eb5}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {25ed8223-a1b9-11df-8bfb-9a91bfde8eb5}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=Z:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {emssettings}
bootems                 Yes

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {25ed8222-a1b9-11df-8bfb-9a91bfde8eb5}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\25ed8221-a1b9-11df-8bfb-9a91bfde8eb5\boot.sdi

Device options
--------------
identifier              {25ed8226-a1b9-11df-8bfb-9a91bfde8eb5}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\25ed8225-a1b9-11df-8bfb-9a91bfde8eb5\boot.sdi

c:\temp>mountvol
Creates, deletes, or lists a volume mount point.

MOUNTVOL [drive:]path VolumeName
MOUNTVOL [drive:]path /D
MOUNTVOL [drive:]path /L
MOUNTVOL [drive:]path /P
MOUNTVOL /R
MOUNTVOL /N
MOUNTVOL /E

    path        Specifies the existing NTFS directory where the mount
                point will reside.
    VolumeName  Specifies the volume name that is the target of the mount
                point.
    /D          Removes the volume mount point from the specified directory.
    /L          Lists the mounted volume name for the specified directory.
    /P          Removes the volume mount point from the specified directory,
                dismounts the volume, and makes the volume not mountable.
                You can make the volume mountable again by creating a volume
                mount point.
    /R          Removes volume mount point directories and registry settings
                for volumes that are no longer in the system.
    /N          Disables automatic mounting of new volumes.
    /E          Re-enables automatic mounting of new volumes.

Possible values for VolumeName along with current mount points are:

    \\?\Volume{90601b11-d301-42bf-ace4-5fc027be3c56}\
        F:\

    \\?\Volume{d08ac883-a1b6-11df-b853-806e6f6e6963}\
        Z:\

    \\?\Volume{1cbca1aa-a549-494d-8f30-7ca6bb0bad0a}\
        G:\

    \\?\Volume{d08ac884-a1b6-11df-b853-806e6f6e6963}\
        C:\

    \\?\Volume{d08ac885-a1b6-11df-b853-806e6f6e6963}\
        D:\

    \\?\Volume{d08ac886-a1b6-11df-b853-806e6f6e6963}\
        E:\

    \\?\Volume{d08ac889-a1b6-11df-b853-806e6f6e6963}\
        H:\

    \\?\Volume{e8c5aff6-e2bd-11e1-8aca-78e7d1dd37b8}\
        I:\

c:\temp>diskpart

Microsoft DiskPart version 6.1.7601
Copyright (C) 1999-2008 Microsoft Corporation.
On computer: FILESERVER

DISKPART> list disk

  Disk ###  Status         Size     Free     Dyn  Gpt
  --------  -------------  -------  -------  ---  ---
  Disk 0    Online         2794 GB      0 B        *
  Disk 1    Online          931 GB      0 B
  Disk 2    Online         2794 GB      0 B        *

DISKPART> list volume

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     H                       DVD-ROM         0 B  No Media
  Volume 1     I                       DVD-ROM         0 B  No Media
  Volume 2     F   Data         NTFS   Partition   2794 GB  Healthy
  Volume 3     Z   System Rese  NTFS   Partition    100 MB  Healthy    System
  Volume 4     C                NTFS   Partition     58 GB  Healthy    Boot
  Volume 5     D                NTFS   Partition    146 GB  Healthy
  Volume 6     E                NTFS   Partition    726 GB  Healthy
  Volume 7     G   Backup       NTFS   Partition   2794 GB  Healthy

DISKPART>
 

Thank you again for all of the information!  Based on the provided information it appears that some of the volumes have Shadow Storage associations except for the Z: and G: volumes.  If the Z: and G: volumes were included in the backup job, then the first suggestion would be to:  (A) Create Shadow Storage for these volumes, as shown below (9 & 10).  (B) Reconnect the USB Drive.  (C) Rerun the failing backup job.   When able, please let me know about these volumes and\or about the outcome of the suggestion.  Thank you.

(9)   C:\>VSSADMIN ADD SHADOWSTORAGE /FOR=Z: /ON=Z:  /MaxSize=UNBOUNDED

(10) C:\>VSSADMIN ADD SHADOWSTORAGE /FOR=G: /ON=G:  /MaxSize=UNBOUNDED

One of the suggestions I found while troubleshooting the VSS errors was that the system partition at the beginning of the first physical drive needed to have a drive letter assigned to it.  I believe this is a Dell thing to have 100m partition for recovery, or system files or something.  So I assigned Z: to this partition.  It didn't fix the problem, but I never removed the drive letter assignment.

G: drive is where I have my main B2D folder.  There should be nothing on it, except a directory called backups and that is where Backup Exec should back things up to.

Given those two explinations, should I still add the shadowstorage to both drives?  Let me know, and Ill give it a try.

Marcusolini

   If I could, I would kiss you!!!!  Thank you for your assistance.  Finally, with the external USB Drive plugged in, the backups worked last night.  I had read about setting up the shadowstorage area on the drives, and I had done it for most of them, but I guess the trick was that you have to do it for ALL the drives, including that System Reserved partition.

   Now I can get back to duplicating a backup to that external drive and taking it off site. 

Thank you again for all your help.

Great news!  Glad I could help!  Thank you for all of your patience and assistance with the diagnostics.