Use the srv4 changevolume command to change the volume used by data content attributes of existing objects - i.e. to move the binary data from a volume to another one. This way uses the GN4 procedures and loads the database server. If you want to do something quick and dirty, look at the next section of this topic. Example srv4 changevolume 6766,6765,6764 -attr image.preview -name images moves the binary data of the previews (i.e. the image.preview attribute) of the objects with id 6766, 6765 and 6764 to the volume 'images'. If the binary data was inside the database, it is moved to newly created files within the 'images' volume; if the binary data was already in files in a volume these files are moved to the 'images' volume (and the references in the database are updated accordingly. srv4 changevolume 6766,6765,6764 -attr image.preview -name "" moves the binary data of the previews of the objects with id 6766, 6765 and 6764 into the databse, removing the volume files (if any). srv4 changevolume -conditions folderObjectInFolder -pars folderPath:/Archive -attr folderObject.variants.data -name variantsArchives moves the binary data of the variants of all the folder objects in the folder '/Archive' to the volumes 'variantsArchive'. |
1.Stop all Back4 ingestion queues that import data you're about to change paths for. 2.Export volumes into volumes.xml as explained in Export/import volumes data to/from XML file.# 3.Open the file in an ASCII editor, change the paths, save the file. 4.Reimport volumes. 5.Copy the related folders to a new device. 6.Delete the related folders from the old device. 7.Reset all IIS. 8.Restart all Back4. |
Notes
•For the description of the changevolume command, see changevolume.
•For additional information, see the discussion on Tera forum in http://forum.teradp.com/topic.asp?TOPIC_ID=737.
See also
Move volumes to another device