Should you ever want to move GN4 volumes to another disk or device, follow the below procedure.
In a new GN4 database
If the database is new, so no data is actually loaded, you can simply change the root URL to something else, e.g., if the device is physically attached to the server (SAN device), use:
<add key="Db.RootVolumeUrl" value="file://C:/tera/volumedata/" />
If the device is mapped (NAS device), use:
<add key="Db.RootVolumeUrl" value="\\server\share\Tera\VolumeData" />
It is mandatory to use UNC and not mapped drives, as mapped drives are visible for the current session only, and IIS does not run in the user’s session.
Read more about it here: http://technet.microsoft.com/en-us/library/dd296641(WS.10).aspx
In an used GN4 database
Run srv4 volumes -out volumes.xml, to export volumes in a file.
Then, edit the volumes.xml and establish new paths.
Finally, reimport it by running:
srv4 volumes -in volumes.xml
Restart IIS for the application to catch these changes.
Notes
•For the description of the volumes command, see volumes.
•For additional information, see the discussion on Tera forum in http://forum.teradp.com/topic.asp?TOPIC_ID=737.
See also