Archive for the ‘Data Protection Manager’ Category

Recently a Backup Admin from a client had an issue with DPM  the error read: “DPM encountered error from VMware while trying to get ChangeTracking information. Server – vcenter.mydomain.com ErrorCode – FileFaultFault (ID 33621 Details: Internal error code: 0x80990EF3)”

DPM-_ID_33621

I researched the error and found a solution by:  Josh Gulick, Support Engineer, Microsoft  Change Block Tracking needs to be reset if another backup product has protected a VMWare VM prior to DPM

After implementing consistency check was running, after 5 minutes a error pops-up

“DPM is out of disk space for the replica. (ID 58 Details: There is not enough space on the disk (0x80070070))”

DPM-OutOfDisk

I modified the disk allocation and re-ran the job; Completely Successful.

ConsistencyCheck-OK

Thank you very much: “Josh Gulick” for this contribution.

Advertisements

Ever since System Center 2012 R2 Data Protection Manager started to support VMWare I’ve been trying to get it to work, I would end up getting stuck on the Certificate issue. A couple of days ago I saw this post:

implementingmicrosoftdpmhostlevelprotectionvmwarevms

To my benefit they solved the certificate issue, and I was able to implement the solution perfectly. A very special thanks  J.C. Hornbeck [MSFT] to for this Post.

Ever since System Center 2012 R2 Data Protection Manager started to support VMWare I’ve been trying to get it to work, I would end up getting stuck on the Certificate issue. A couple of days ago I saw this post:

implementingmicrosoftdpmhostlevelprotectionvmwarevms

To my benefit they solved the certificate issue, and I was able to implement the solution perfectly. A very special thanks  J.C. Hornbeck [MSFT] to for this Post.

A couple of days ago I receive a call from a colleague:

He has System Center Data Protection Manager and a couple of days before he starts receiving notifications that there are “No Recovery Point Available” for Tape backups. He’s already checked the console and all Protection Groups have the Green Check mark.

I ask if he’s checked the latest recovery point on each item of the Protection Groups. He checks and replies back that they show the latest recovery point a month ago. I ask him if any of the storage disks have recently disconnected from DPM. He replies that indeed they did.

  1. Open System Center Data Protection Manager Power Shell.
  2. Insert command “dpmsync -sync”dpm-sync

After you execute the command DPM will sync with the information recorded on SQL Server database and compare.dpmsync2

*VERY IMPORTANT; after the sync is complete you will need to create new Recovery Points. After they have completed you should be able to run tape backups successfully.

Enjoy he Post.

AAII

This one is an old draft that i forgot to Post…

Application: System Center 2012 R2: Data Protection Manager

Protected Server: Windows Server 2012 R2

Protected Server Roles: Hyper-V

Protected Server File System for VM’s: ReFS (Resilient File System)

I created a Protection Group for Hyper-V, and while replication… WHAM!, critical Alert, Replica Inconsistent.

I check under Monitoring

dpm-alerts

Affected area:   \Online\HYPERV-VM

Occurred Since:  01/29/2015 11:22:47 AM

Description:

The replica of Microsoft Hyper-V \Online\HYPERV-VM on HYPERVSERVER.TEST.LOCAL is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.
For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

An unexpected error occurred while the job was running. (ID 104 Details: Do not attach the filter to the volume at this time (0x801F000F))

********************************************************************

In this particular case the error is related to the File System type of the Protected Server (ReFS). DPM does not support to ReFS File System (at least at the time when i wrote the post).

What you need to do:

There is a quick fix, so roll up sleeves… Registry…

Open the Registry

  1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Data Protection Manager\Agent\2.0
  2. Create a DWORD (32 bit value)
  3. Name it “ForceFixup” (don’t forget to remove the quotation marks)
  4. Value data will be 1
  5. Base will be Hexadecimal
Close the registry, then go to Power Shell and execute:
  1. net stop dpmra (if you receive “The DPMRA service is not started”, execute the net start…)
  2. net start dpmra
close Power Shell, Open DPM Management Console and re-run the replicacion Job.
YOU ARE DONE, CONGRATULATIONS!

 

 

As a backup administrator it’s important to backup and restore your servers and data on it.  You have you network set out (you probably use the production network for your backups, in non operating hours) your routines for backups, everything is set to go. All is going well until a backup did not run with the rest and now you have to run it during “Business Hours”.

DPM-Production

DPM Production network

That where it gets tricky, running backups after hours is easy during business hours, not likely to be approved by Management. What do you do?

Configure a “Backup Network”, this way you can run your backups anytime you want without affecting production.

backupnetwork

DPM Backup Network

  1. Network Addresses ( my production network runs on 10.0.0.0/24 and my backup network runs on 192.168.0.0/24).
  2. Configure the a secondary NIC on all DPM and Protected server with the address for your backup vlan (Example: IP: 192.168.0.1, Mask: 255.255.255.0,  NO gateway or DNS).
  3. On your DPM Server Hosts file configure Backup IP addresses (Example  192.168.0.1 dpmserver.test.local, 192.168.0.1 dpmserver, 192.168.0.2 protectedserver1.test.local, 192.168.0.2 protectedserver) you need both FQDN and NetBIOS.

    hosts file

    Hosts

  4. On the protected Servers Host file add the DPM Server address matching the backup network using both FQDN and NetBIOS. (Example:  192.168.0.1 dpmserver.test.local , 192.168.0.1 dpmserver)
  5. On the DPM Server open DPM Management Shell and run the following command: Get-DPMBackupNetworkAddress (for remote servers “Get-DPMBackupNetworkAddress – DPMServerName %servername%”, where you substitute %servername% for the actual name of your server) and it should return nothing because we don’t have a backup network configure yet.

    get-dpmbackupnetworkaddress

    Get-DPMBackupNetworkAddress

  6. Next we will configure the DPM Backup Network Address, by running the command: Add-DPMBackupNetworkAddress -DPMServerName %servername% -Address 192.168.0.0/24 -SequenceNumber 1 (On this command were already familiar with basically most of the command we add the -Address and the network, the -SequenceNumber will allow us to have multiple Backup Networks and it sets priority, on this example we only have one)

    Add-DPMBackupNetworkAddress

    Add-DPMBackupNetworkAddress

  7. After this has been set, we can run the Get-DPMBackupNetworkAddress and we will see the new network.
  8. On the DPM Server execute command: restart-service DPM

    restart-service-DPM

    Restart-Service DPM

  9. After this we go to the console and run a consistency check or Recovery Point on any protected server and after a while you will begin to see data being sent from protected server to DPM Server.

*Very important, you must be able to ping your DPM Server from the protected server and only the Backup Network IP respond, same from the DPM Server to a protected server only the backup network address must respond using both FQDN and NetBIOS (Example: ping dpmserver, dpmserver.test.local 192.168.0.1 …..).

I hope this information helps you out! and Merry Christmas and a Happy New Year.

 

I start my morning checking by Backups and I find myself with a particular error: “Recovery point creation failed” I go below the error and I see the More Information option, it didn’t work before but after a recent update to Data Protection Manager redirected to the System Center Data Protection Manager error code page which is very useful. I find my error code:

30172 [click on the picture below for more information]

ErrorDPM30172

So I tried the solution but really could not find “Readable Secondary” so I re-analyzed the issue SQL is refusing connection, I went to the SQL Server Management Console + Security and verified that all the appropriate users and permissions were correct:

NT AUTHORITY\SYSTEM was missing , I re-added it with Sys Admin role

ErrorDPM30172-2ErrorDPM30172-3

Went  back to DPM Console and re-ran all the SQL Server backup jobs

ErrorDPM30172-4