Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

Elviz42

37 Posts

1710

May 22nd, 2007 06:00

Moving NAS Media to another Server

Hi there! We are using DX 5.60.049 (together with EX). We are migration to a NAS-Media (fileshare on Windows Server 2003). The NAS-media is about to get full, so I want to move this media to another server. I took a look in the registry at HKLM\SOFTWARE\Legato\XMS\Media where all the neccecary information is located. But I didn´t dare to change this information because of the OTGXMSNAS file that is located in the share of the old location. What do I have to do?

fschlupp

397 Posts

May 23rd, 2007 07:00

Create new NAS media using the new path. Add the new piece of media to the existing media group. Then compact the existing NAS piece of media. This will fetch back each EX container file to the server and rewrite it to the new media. Once compaction is complete the existing piece will drop out of the existing media group. You can then cleanup the container files in the original path. Hope this helps.

mblair1

1 Message

September 29th, 2011 13:00

t

Question posed by a client? I have questions regarding the DX instance running in our Synergy test environment and specifically how it integrates with the "OtgXmsNas" System file that apparently lives on each of the NAS Snaplock volumes. I need to know if DX needs to have access to read and write to this file at all times? I have done some research on the file OtgXmsNas and understand that the file gets created at the time the NAS device is created. I believe the answer is yes but do you know the answer?

Vinodraj_Daniel

12 Posts

September 29th, 2011 23:00

Yes, "OtgXmsNas" file gets created when NAS media is created and removed when it gets deleted. In case of snaplock(retained NAS media), there would be one more file called "OtgXmsNAS.zzz" that would also be created to check if retention is enabled on the backend. Both these files are not accessed duing normal file write/read operations, but the expectation is that these files should be accessible.

View More

View All

No Events found!

Top