Veeam: ‘Error Storage Not Initialized’

KB ID 0001614

Problem

I got tasked with looking at a failover plan for a customer recently, but I noticed their replications were failing, two of the VMs in the replication job were repeatedly failing with;

Error storage not initialized

Error: Storage not initialized

Error storage not initialized

Veeam Replication Error storage not initialized

Solution

This took a while to get to the bottom of! Essentially the problem was the ‘Metadata’ for these two VMs was either corrupt or could not be written to. So to fix the problem, the VMs had to be removed and re-added, though the procedure for this has to be done in the following sequence;

From the Replicas Ready section remove the affected VMs from configuration.

Veeam Remove VM From replication

Go to the ‘Replica VM‘ itself (within your hyper visor), and remove all the snapshots.

Veeam Replica Remove Snapshots

Edit the replication job, and add the affected VMs back in again.

Add VM to Veeam Replication.

Make Sure: You repoint the Replica Mapping back to your original replica VM again, (simply hitting ‘Detect‘ will do this, 99 times out of 100).

Replication mapping Veeam

Related Articles, References, Credits, or External Links

NA

Author: PeteLong

Share This Post On

Submit a Comment

Your email address will not be published. Required fields are marked *