Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

Tedponczka

5 Posts

653

March 12th, 2009 11:00

Recovering Windows dynamic disk with recover point

The only way I have been able to consistently recover a dynamic disk using recover point is the following:
1) convert failed dynamic disk to basic
2) rescan disk with diskpart or dev manager
3) RPA option recover production
4) Enable image access
5) Rescan or rboot
6) add new drive letter

I would like to know if any other process is recommended or works better?

AranH1

2.2K Posts

March 13th, 2009 08:00

I think the issue is the fact that it is a dynamic disk and not the replication transport. Doesn't Windows store some specific information regarding the dynamic disk layout? And if you move that disk to another Windows box it will recognize that the disk is dynamic but will not have the configuration information stored on the original host.

I believe that is why replicating basic instead of dynamic disks is better. The basic disk format does not require any disk configuration data be stored on the host, and the disk can be remounted on other hosts easily.

JamesBEMC

257 Posts

March 18th, 2009 02:00

Dynamic Disks are tricky regardless of which way you go.

The first disk in the group needs to be addressed and trying to move a dynamic disk group to another host is even trickier because there is no uniqueness set in the dyncdisk group numbering, so a dyndisk group #1 on host A will cause a clash to dyndisk group #2 on host B.

Was this post helpful?

View All

No Events found!

Top