none
DPM 2012 Cannot modify or create protection groups after upgrading from DPM 2010 RRS feed

  • Question

  • Hi,

    We have recently upgraded from DPM 2010 to 2012.  Since the upgrade we have been unable to create new protection groups or add new datasources to an existing group.  Existing backups are running without errors. 

    We have tried checking the DPM sql user account permissions as described in this article but with no luck.  More searching has not provided any other relavent fixes.  We are now stuck on how to troubleshoot this any further.

    In the DPM console we get the following error adding a VM to an existing protection group:

    Modify protection group: Virtual Machines failed:
    Error 207: An unexpected error occurred on DPM server machine during a VSS operation.
    Error details: VssError:Shadow copying the specified volume is not supported.
     (0x8004230C)
    Recommended action: Retry the operation.

    Allocate Replica For \Backup Using Saved State\Cacti failed:
    Error 207: An unexpected error occurred on DPM server machine during a VSS operation.
    Error details: VssError:Shadow copying the specified volume is not supported.
     (0x8004230C)
    Recommended action: Retry the operation.

    In the event log we see:

    The description for Event ID 955 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

    If the event originated on another computer, the display information had to be saved with the event.

    The following information was included with the event:

    The consistency check resulted in the following changes to SQL Server Agent schedules: Schedules added: 1 Schedules removed: 1 Schedules updated: 0.  

    Problem Details:
    <ConsistencyCheck><__System><ID>26</ID><Seq>1534</Seq><TimeCreated>23/04/2012 09:33:29</TimeCreated><Source>SchedulerImpl.cs</Source><Line>719</Line><HasError>True</HasError></__System><Tags><JobSchedule /></Tags></ConsistencyCheck>

    the message resource is present but the message is not found in the string/message table

    Thanks in advance for any advice.

    Monday, April 23, 2012 9:40 AM

Answers

  • Hi,

    The error 0x8004230C VSS_E_VOLUME_NOT_SUPPORTED: Shadow copying the specified volume is not supported, can only come when trying to enable shadow copies on new volumes created when trying to add new datasources to protection.   Generally speaking Only NTFS volumes greater that 1GB with a minimum of 300MB free space can be shadow copied, so something is going wrong with the volume creation / format process.  Please investigate that, see if two new volumes get created when protecting a new data source, and the sizes are greated that 1GB and also verify it's formatted NTFS.


    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. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, May 10, 2012 10:02 PM
    Moderator

All replies

  • Hi,

    A complete stab in the dark ... have you upgraded the agent of the resource you're adding to protect? Have you rebooted the DPM server since doing the upgrade?

    J

    Tuesday, April 24, 2012 4:05 PM
  • Hi John,

    Yes we have updated all agents to match the server and have rebooted the DPM Server several times.

    I think we may have to re-install the DPM server from scratch to fix but I'm desperate to find a way without doing this.

    Dan

    Monday, April 30, 2012 11:35 AM

  • I think we may have to re-install the DPM server from scratch to fix but I'm desperate to find a way without doing this.


    http://jeramythompson.blogspot.com/2012/04/dpm-2012-upgrade-from-2010.html

    just take a backup of the DPM database, uninstall dpm, uninstall SQL (if its installed locally) re-install both DPM with SQL.

    DPMSync –RestoreDB –DBLoc location of folder 
    DPMSync takes the DPM service offline and attaches the backed up database to SQL

    after that run
    DpmSync -sync
    then reboot the server.
    when it comes back up, re-scan your library, re-sync your restore points, you should be good to go.  "


    • Edited by Jeramy T Monday, April 30, 2012 6:24 PM
    Monday, April 30, 2012 6:23 PM
  • Thanks for the information Jeramy.

    I have followed your advice and completely uninstalled DPM and SQL.  Re-installed and then imported the database. 

    Sadly the errors are still identical.  I have tested a bit further and have found the following:

    • I can modify the retention and timings of any existing protection groups.
    • I can remove datasources from existing protection groups.
    • I cannot create new protection groups for any type datasource (Hyper-V, SQL, Volumes etc...).
    • I cannot add new datasources to existing protection groups.
    • All other DPM functionality is working absolutely fine. I can syncronise, backup, restore, incremental backup etc...

    At this point I am suspecting either something at fault in the underlying server os or with the actual DPM database itself.

    Any further sugestions?

    Wednesday, May 2, 2012 11:00 AM
  • Hi,

    Part of my DPM 2012 readyness installation is to install KB2223201 and then KB2615782. The first hotfix does address some VSS issues, it might we worth applying? I'm on 2008 R2 SP1 so I don't need the hotfix, out of interest what version are you running?


    J
    • Edited by John Grenfell Tuesday, May 8, 2012 3:02 PM added SP1 information
    • Proposed as answer by JvdB77 Thursday, April 25, 2013 7:34 AM
    Tuesday, May 8, 2012 3:00 PM
  • Sadly/fortunately we are already running Server 2008 SP1.

    My next step is to try re-installing DPM from scratch and not restore the database to see if that will let us create new datasources, ruling out any issues with our database. Won't be able to do that for a while though unfortunately.

    Wednesday, May 9, 2012 7:49 AM
  • Ok.

    Another long shot (sorry) but have you check how much free spaced your database has? You should be able to check this via SQL Management studio and increase the size if free space is tight (I've had a problem with SCOM where my DB needed to grow)

    Wednesday, May 9, 2012 7:59 AM
  • Long shots more than welcome, it's often those that randomly lead to a fix!

    I've had a look at the DB size, its listed as 4.8gb with 3.5gb available.  I assume this is due to an sql server limit of 8gb for the version shipped with DPM 2012.  Im assuming thats all fine, the primary database file is set to autogrow by 1mb with unrestricted growth.

    Wednesday, May 9, 2012 8:03 AM
  • Yeah that sounds good.

    Unfortunalty I'm no sql expert but I would look at doing a SQL profiler while I'm trying to make a change to see if you can "sniff" the error. It's probably bit of a tall order but it might highlight a SQL issue if one exisits?

    J

    Wednesday, May 9, 2012 8:32 AM
  • Thanks for the advice, I've had a look but can't see anything in the 20,000 or so events that get logged during the datasource update (unsuprisingly!)

    I have just noticed that the error event generated is an hour out of the data in the event.  The error logged at 11:15:37 server time is:

    <ConsistencyCheck><__System><ID>26</ID><Seq>3096</Seq><TimeCreated>09/05/2012 10:15:37</TimeCreated>etc......

    Could it be that the sql agents time is an hour off what dpm thinks, causing it to delete a job as soon as DPM adds it due to it being expired?

    Wednesday, May 9, 2012 10:41 AM
  • SQL will be picking it's time from the system ... it's probably just daylight saving offset.

    Have you tried adding via powershell?

    $ProtectionGroupName = "YOURProtectionGroupNameHERE"
    $DPMServer = "YOURDPMServeNameHERE"
    $ClientName = "THE Client you want to add"
    $ProtectionGroup = Get-ProtectionGroup -DPMServerName $DPMServer | Where-Object {$_.FriendlyName.ToUpper() -eq $ProtectionGroupName.ToUpper()}
    $ModifiableProtectionGroup = Get-ModifiableProtectionGroup -ProtectionGroup $ProtectionGroup
    $DataSource = Get-DataSource -ComputerNames $ClientName -DPMServerName $DPMServer
    Add-ChildDataSource -ProtectionGroup $ModifiableProtectionGroup -ChildDataSource $DataSource
    Set-ProtectionGroup -ProtectionGroup $ModifiableProtectionGroup

    Wednesday, May 9, 2012 10:54 AM
  • Powershell does the same, we have a script that runs nightly to query our hyper-v cluster and add protection for any new VM's.  That gives exactly the same errors.

    This morning I've completely removed DPM 2012 and SQL 2008 R2, re-installed DPM 2010 and restored the original database backup from before we tried any of this and sadly the same issue is still there with DPM 2010!

    Could it be there is another component of DPM 2010/SQL 2008 R2 that neesd to be removed to revert back to pre upgrade?

    My last straw now is to completely re-installed the entire OS and build the server from scratch. 

    Thursday, May 10, 2012 10:10 AM
  • Hi,

    The error 0x8004230C VSS_E_VOLUME_NOT_SUPPORTED: Shadow copying the specified volume is not supported, can only come when trying to enable shadow copies on new volumes created when trying to add new datasources to protection.   Generally speaking Only NTFS volumes greater that 1GB with a minimum of 300MB free space can be shadow copied, so something is going wrong with the volume creation / format process.  Please investigate that, see if two new volumes get created when protecting a new data source, and the sizes are greated that 1GB and also verify it's formatted NTFS.


    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. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    Thursday, May 10, 2012 10:02 PM
    Moderator
  • Hi Mike,

    Great sugestion, I hadn;t even thought to look at the storage array's in DPM's pool.

    We have two iSCSI arrays, one is at 94% the other is not yet in use.  I created a blank volume on the nearly full array to use up the rest of the space and DPM will now create new protection volumes on the second array fine.

    Problem now is why that array is now being dificult. Is there perchance a hard limit in the number of DPM volumes per storage disk?  This one currently has 28.

    I will also look at the array itself as I have a sneaky suspicion thin provisioning + cheap iSCSI vendor could be the issue.

    Thanks for all your help!

    Friday, May 11, 2012 7:43 AM
  • HI,

    There are no volume limits per dynamic disk, however there are volume limits for all dynamic disks, and DPM will warn you when you are at 80% of that threshold, and block you at 90% with appropiate messages.   I also suspect thin provisioning especially if you specified a virtuial Disk size larger than the underlying physical storage capacity of the array.  If you did that, then you would need to add more physical storage to accomodate the virtual size of the disk.

    Anyhow, glad you figured it out.


    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. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.

    • Proposed as answer by Jochen Wezel Friday, March 13, 2015 12:05 PM
    Friday, May 11, 2012 2:20 PM
    Moderator
  • I also suspect thin provisioning especially if you specified a virtuial Disk size larger than the underlying physical storage capacity of the array.  If you did that, then you would need to add more physical storage to accomodate the virtual size of the disk.

    Dropping the old too big virtual disk and creating 2 smaller ones changed the game. I'm wondering why MS DPM 2012 can't correctly handle those thin virtual disks...This is a calling for a bugfix update for DPM! :-)
    Friday, March 13, 2015 12:10 PM