DR – Pagefile showing up as wrong drive

pts.
Tags:
Backup and Recovery
We have 20 DR Windows servers that we use SRDF - EMC - IP replication between two sites. We test these servers often. We have drives in both locations that are not synced - the P drive which is where we have the page file. When we boot these boxes in the remote location the p drive will show up as the next available drive letter. Even though the disk has been formated - labeled the same and has had the pagefile written on it. We separate the page file off because it is not needed for replication. Now when we boot up the servers, there is no page file because it is trying to write to the P drive, but it is in disk management as e, f, or whatever the next letter is. We have to change the drive letter and reboot, then the server is fine. I want to know why the drive letter does not show up as P. It would save a lot of time. Any help would be great! Thanks.

Answer Wiki

Thanks. We'll let you know when a new response is added.

Are you replicating the C: and the registry?

The GUID for the “P:” drive on the DR server may not be in the replicated registry which can cause it to be added as the next available drive. Drive letter assignments, or specifically drive GUID to mount point assignments, is held in the registry. So if you’re replicating the %systemroot% drive, you’re going to ignore any drive assignments on the DR servers because the registry is going to be overwritten.

If that’s the case, the solution is to replicate the production “P:” drive once. This will replicate the GUID to the paging volume on the DR server. Once the GUID on the DR server matches the GUID on the production server, mount point “P:” will be the same on the production and DR sites. After it’s been replicated one, you can drop it from the list of replicated drives–the point is to get the GUID to match between P: drives at both sites.

Of course, if you’re *really* handy w/ registry delving, you can manually edit the registry on the production server to include the GUID for the remote drive… If you’re not replicating the %systemroot% drive, then P: should not change mount points after you’ve assigned it a location.

You can view existing disk GUID to mount point assignments by using the “mountvol” command on Win2k and Win2k3 from a DOS prompt.

Discuss This Question:  

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following