Syncs initiated using the Volume tab

When you make selections in the Volume GUI, Xinet issues commands on the server. The commands depend both on the initial state of the volume and the options you select in the GUI. Seven possibilities exist:

Case 1: Enabling a volume for the first time (storing files only)

Literally this means:

•	You’ve selected a Web Volume with the pop-up list.

•	You’ve checked the Enabled Database button.

•	You’ve clicked Submit.

Xinet will run the following process:

userperms -sync -progress -del path_to_volume

This process can be seen in its entirety on Unix systems. On Windows installations, it will be seen as userperms.exe in the Task Manager. This is, in fact, true for the other six cases too.

As a result:

•	Files are read into the database.

•	XMP and IPTC data are read into the database.

•	Any file information about archived files is read into the database.

•	Previews of images, InDesign files, and PDFs are not read into the database.

For more information on the -del flag, refer to Syncs: to -delnorm or not to -delnorm. The flag, which is analogous to using the -delnorm flag with syncvoltodb(8, will set everything to be offline. This is the most complete check of the file system. It is also the only way to read in information about archived files.

Case 2: Enabling a volume for the first time (storing files and any combination of previews)

Literally this means:

•	You’ve selected a volume from the pop-up list.

•	You’ve checked Enabled Database, Store Small Web Preview, and/or Store Large Web Preview.

•	You’ve clicked Submit.

The following process will be run:

userperms -sync -progress -del path_to_volume

This result will be:

•	Files are read into the database

•	XMP and IPTC data is read into the database.

•	Previews of images, InDesign files and PDFs are stored in the database.

•	Any file/preview information about archived files is read into the database.

Case 3: Adding flags to store previews on a volume that was already enabled

Literally this means:

•	You’ve selected a volume from the pop-up list.

•	The volume already had the Enable Database button checked.

•	You have checked the Store Small Web Preview and/or Store Large Web Preview button(s).

•	You have clicked Submit.

The following process will be run:

userperms -sync -progress -del path_to_volume

This should result in the following behavior:

•	Files are read into the database.

•	XMP an IPTC data are read into the database.

•	Previews/ of images, InDesign files and PDFs are stored in the database.

•	XMP and IPTC data are read into the database.

•	Any preview information about archived files is read into the database

Note that all the file information, XMP and IPTC data will be read into the database again.

Case 4: Re-submitting a volume without changing any flags

Literally this means:

•	You’ve selected a volume from the pop-up list.

•	You’ve clicked the Submit button.

The following process will be run:

userperms -sync -progress path_to_volume

This should result in the following behavior: a “quick” sync of the volume will be run.

Note the absence of the -del flag with the userperms process above. For more information on syncs that do not use -del, see "Syncs: to -delnorm or not to -delnorm” on page 638.

Case 5: Unchecking flags for storing one or more type of previews while leaving volume enabled

Literally this means:

•	You’ve selected a volume from the pop-up list.

•	The volume already had the Enable Database plus one or more of the Store Preview buttons checked.

•	You have now deselect one or more of the Store Preview buttons.

•	You’ve clicked the Submit button.

The following process will be run:

userperms -sync -progress path_to_volume

This should result in the following behavior:

•	The volume will no longer store previews of files added.

•	File table entries remain the same.

•	Previews of existing files will remain in the database.

•	However, they will not be accessed when a user is browsing Xinet.

The current behavior of Xinet is to continue to display previews stored in the database for volumes that have had one or more preview flags disabled. If this isn’t the behavior you’d like, uncheck the flag and let the sync run. Once the sync is done, run:

Unix: /usr/etc/venture/bin/dbmgr -dbclean
Windows: C:\Progra~1\Xinet\Venture\bin\dbmgr -dbclean

This won't remove all previews, just ones for files that are in volumes set to not store those types of previews. This will make the database smaller.

Case 6: Unchecking Enable Database for a volume but leaving flags for storing one or more type of previews checked

Literally this means:

•	You’ve selected a volume from the pop-up list.

•	The volume already has the Enable Database and one or more of the Store Preview buttons checked.

•	You’ve deselected only the Enable Database button.

•	You’ve clicked the Submit button.

The following process will be run:

userperms [with no flags]

This should result in the following behavior:

•	The volume no longer stores file or preview information about new files added.

•	Existing files and preview information will be kept in the database, but won’t be accessed by Xinet users.

This means that the size of the database does not decrease. The information is still stored. Generally, this action is only done if you want to temporarily disable Xinet on a particular volume. When you re-enable it, less file/preview information has to be read in again; thus the sync process will be much quicker. However, if your goal is to just disable the database altogether for a brief time (and not just on one volume), it’s better to just stop the database (using the xinet ADMINISTRATION view) and restart it later.

Case 7: Unchecking flags for files and all stored previews — completely disabling the database for a volume.

Literally this means:

•	You’ve selected a volume from the pop-up list.

•	The volume already had the Enable Database and one or more of the Store Preview buttons checked.

•	You’ve then deselected the Enable Database button and all the Store Preview buttons.

•	You’ve clicked the Submit button.

The following process will be run:

userperms [with no flags]

This should result in the behavior described in Case 6. It’s exactly the same.

Generally people use this option when they want to completely disable a volume and don’t intend to re-enable it. To remove all trace of the files from this volume from the database, do the following:

1.	Find the volume id of the volume being removed. From the msyql client run select * from volume. The volume id is the first column.

2.	Use dbmgr(8) to remove all files that were within that volume. For example, if the volumeid were 3:

dbmgr -remove -vid 3