| Aspera Sync |
264
Display only the requested information. Use with
-f
/
--file-info
to disable abbreviating file
names in the output.
-s, --summary
Report the number of files in each state. When
-s
is used alone, a brief summary from the
async
database's counters table is reported back (same as the cached counters as in the
-t
option).
CAUTION:
The use of this option is not recommended on Windows, as it can cause
the database to lock and
async
to fail. An alternative is to use the
-t
option below.
-s -v
When
-s
is used with
-v
, every record in the
async
database is counted.
Important:
This should only be used when
async
is not running.
-T, --terminate
Shut down
async
if it is running. This option cannot be used if the storage style set for
<async_db_spec>
is LMS and outputs an error message.
-t
num
, --tail=
num
Report status of last
num
files.
Note:
Use of this option on Windows as an alternative to the
-f
and
-s
options above.
--touch=
path
Change the recursive mtime of the node and all its parents to current time if they are older. This
option is only applied if
async
has been run using the
--exclude-dirs-older-than
option.
-v, --verbose
Increase the verbosity of summary (
-s
) or file info (
-f
).
-x, --init
Delete all file system snapshot records.
Logging
By default, Aspera Sync logs all file system synchronization events and transfers, including any errors that were
encountered by synchronizing hosts, to
syslog
. You can set the logging location on both endpoints when you start
async
.
Important:
If you attempt to synchronize a directory without the proper read/write permissions, the directory and
files it contains are
not
marked with an ERROR flag in the file directory status output. However, the error will be
noted in the log file.
Troubleshooting Aspera Sync
Many Aspera Sync problems can be corrected by using required options, ensuring users have necessary permissions
to access files, and configuring the endpoints as required.
Troubleshooting General Aspera Sync Errors
Fixes for common Aspera Sync issues.
The Aspera Sync client displays failure to start sync error
When the
async
binary on the remote computer cannot initialize, the
async
client gets a generic error similar to the
following:
Failed to start sync session