none
Error 30169: "the data source is not available", migrated data source RRS feed

  • Question

  • Hi,

     

    Ive recently been migrating VMs to different HyperV hosts using SCVMM, and noticed that the changes are not being noticed by DPM, the DPM agent is installed on the hyper V blades and not on the VMs themselves, and DPM is throwing the below error on those VMs which have been moved:

    The operation failed for "Data Source" on "Hyper V Blade" because the data source is not available

    Would I be able to change the data source (add the VMs as new protected memebrs) in DPM to point to the new location and remove the one throwing an error without it removing all the backups that have already been taken?

     

     

    Thursday, August 4, 2011 4:04 AM

Answers

  • Hi gloomy99,

    this is no problem at all. Simply go to the protection group with the VM in the protection tap - right click the protection group and modify it. In one of the first wizard window on the right hand side are all your currently protected data sources displayed. Simply remove the problematic VM and then finish the wizard. In the protection tap you will now see a new entry called "Inactive protection for previously protected data". So for the duration of your configured retention periode the backed up data of the VM is still present.

    If you go to the recovery tap you will see the backups of this vm is still available.

    In case you want to delete the protection group just make sure to say "Retain data". This will also keep the backups.

     

    Just curious - when you moved the vm's this was not to another cluster host it was to another standalone Hyper-V host?

    • Marked as answer by gloomy99 Friday, September 2, 2011 3:57 AM
    Thursday, August 4, 2011 10:00 AM

All replies

  • Hi,

    are you using CSV cluster ? In that case if the agent is installed on all the nodes then it should reflect the changes and apply it to your Protection.

    If not you need to add the VM to the protection group and remove the old one keeping the data.

    Thursday, August 4, 2011 9:55 AM
  • Hi gloomy99,

    this is no problem at all. Simply go to the protection group with the VM in the protection tap - right click the protection group and modify it. In one of the first wizard window on the right hand side are all your currently protected data sources displayed. Simply remove the problematic VM and then finish the wizard. In the protection tap you will now see a new entry called "Inactive protection for previously protected data". So for the duration of your configured retention periode the backed up data of the VM is still present.

    If you go to the recovery tap you will see the backups of this vm is still available.

    In case you want to delete the protection group just make sure to say "Retain data". This will also keep the backups.

     

    Just curious - when you moved the vm's this was not to another cluster host it was to another standalone Hyper-V host?

    • Marked as answer by gloomy99 Friday, September 2, 2011 3:57 AM
    Thursday, August 4, 2011 10:00 AM
  • Hi Sorry for the late reply, they are all stonealone hyperv hosts.
    Friday, September 2, 2011 3:58 AM