You may experience a delay when you create a Groove file sharing workspace to replicate a large folder (914624)
The information in this article applies to:
- Groove Virtual Office 3.1 File Sharing Edition
- Groove Virtual Office 3.1 Professional Edition
- Groove Virtual Office 3.1 Project Edition
- Groove Virtual Office 3.1 Trial Edition
- Groove Virtual Office 3.0 File Sharing Edition
- Groove Virtual Office 3.0 Professional Edition
- Groove Virtual Office 3.0 Project Edition
- Groove Virtual Office 3.0 Trial Edition
SYMPTOMSWhen you create a file
sharing workspace to replicate a large folder
in Groove Virtual Office, you may experience a delay
as the computer processes the data.WORKAROUNDTo work around this behavior,
you can share an empty folder at first
if the folder that you want to replicate contains an unusually large number of
files. Then, move the data into the empty folder 100 files at a time. Alternatively,
you can start the shared workspace without other members.
Then, add
members one at a time. Both workarounds help distribute the required
processing over several operations.STATUS This
behavior is by design.MORE INFORMATIONWhen
you create a file sharing workspace, Groove
first catalogs
all the files in that folder. For each file, Groove creates a unique signature
and adds to this signature other information about the file, such as the
name and the
time stamp. This index of files is encrypted and stored
in the workspace
on the computer. This process
is similar to what occurs when a file is dropped into
a standard Groove Files tool.
The major
difference is
that the actual file contents are not duplicated in
the file sharing workspace or transmitted to the other members at first. If the
workspace
has other members, Groove sends this index to each member by using the usual
communication path for that endpoint (member
or computer).
As with other transmissions
of Groove
data, a copy of the data for each member
or computer
endpoint is temporarily stored in the outgoing communications database in the
Groove data directory until the
data is
actually sent.
When the file index is received on the other endpoint,
the receiving Groove client processes the information for each listed file.
First, Groove will test for a preexisting file that has the same name in the
destination folder. If no match is found, a stub file is created on the file
system without the actual file contents. If a file that has the same name is
found, a digest is computed for the file
to determine whether it matches
the source file's digest. If the digest matches, Groove does not have to download the actual data from the source. If the digest does not match, a conflicting file is
created.
Next,
Groove can start to synchronize the actual contents of the files. The
Groove download settings are consulted to determine which files will be
automatically fetched from the source computer. When a file is manually
or automatically downloaded, a
fetch request is sent to the source computer
that must read the file from the hard disk, encrypt the
file, and then
send it. When
the destination computer
receives the file, the computer decrypts the file and then
writes it to
the file system.
| Modification Type: | Major | Last Reviewed: | 3/23/2006 |
|---|
| Keywords: | kbprb kbExpertiseInter kbtshoot KB914624 kbAudKnowledgeWorker |
|---|
|