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.


Assign unowned disk in NetApp

Posted: September 26, 2016 in NetApp

A couple of days ago I receive and E-mail from one of our NET APP storage with the following header: HA Group Notification from NetApp04 (FILESYSTEM DISK FAILED) WARNING. Next Day I checked the storage and I found failed disk with a flashing amber led. To my benefit I had purchased 4 spare disks a couple of months back and replaced the failed disk.  

  1. I opened in the NetApp OnCommand System Manager 3.0
  2. Logged in to the storage
  3. Found an unassigned disk



  4. If you try to assign it the options are grayed out.
  5. Login to Storage using SSH (putty or another app)
  6. On the Shell enter command “disk show -n”12
  7. Next on the Shell insert command “disk assign %disk name%” (in this case disk name is 0C.008)3
  8. After disk has been reassigned you will begin to see that reconstruction has begun.4
  9. On the NetApp OnCommand System Manager 3.0 you will see that the disk has been assigned and data is showing up.5

System is now running smoothly, enjoy the post.


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


Affected area:   \Online\HYPERV-VM

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


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.



Shotokan Dojo Kun

Posted: January 27, 2016 in Health and wellness, Shotokan

Shotokan Dojo Kun

Shotokan Dojo Kun

Hitotsu. Jinkaku kansei ni tsutomuru koto
Hitotsu. Makoto no michi wo mamoru koto
Hitotsu. Doryoku no Seishin wo yashinau koto
Hitotsu. Reigi wo omonzuru koto
Hitotsu. Kekki no yu wo imashimuru koto

  • Seek Perfection of Character
  • Be Faithful Protect the Way of the Truth
  • Foster the Spirit of Effort
  • Respect the Principles of Etiquette and Respect Others
  • Guard Against Impetuous Courage and Refrain from Violent Behavior


ISKF Dojo Kun

Posted: January 27, 2016 in Health and wellness, Shotokan
Dojo Kun - Calligraphy by Master Masatoshi Nakayama -

– Calligraphy by Master Masatoshi Nakayama –


ISKF Dojo Kun

  • Seek Perfection of Character
  • Be Faithful
  • Endevor
  • Respect Others
  • Refrain from Violent Behavior

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 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.


DPM Backup Network

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

    hosts file


  4. On the protected Servers Host file add the DPM Server address matching the backup network using both FQDN and NetBIOS. (Example: dpmserver.test.local , 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.



  6. Next we will configure the DPM Backup Network Address, by running the command: Add-DPMBackupNetworkAddress -DPMServerName %servername% -Address -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)



  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

  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 …..).

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


How to Check and Exchange Mailbox for corruption

About a year ago I was migrating exchange 2003 mailboxes to Exchange 2010, after all is working a received a complaint from a user that emails, calendar were not available. I began troubleshooting and after checking the EMC (Exchange Management Console) that particular mailbox had a lot of corrupted items that did not migrate. I proceeded to check mailbox corruption:

  1. Open Exchange Management shell Exch-Management-Shell
  2. Run command:
    1. New-MailboxRepairRequest -mailbox <mailbox alias> -CorruptionType AggregateCounts -DetectOnly
    2. New-MailboxRepairRequest -mailbox <mailbox alias> -CorruptionType FolderView –DetectOnly
    3. New-MailboxRepairRequest -mailbox <mailbox alias>  -CorruptionType SearchFolder –DetectOnly
    4. New-MailboxRepairRequest -mailbox <mailbox alias>  -CorruptionType ProvisionedFolder –DetectOnly

To actually repair them run the commands without the -DetectOnly.