|
|
Peersync Standard Server |
Peersync Standard Server
Download | Price - order |


|
- Repliker åbne filer
- En til mange replikering
- Mange til en replikering
 |
|
|
|
|
Peersync Standard Server Technical Information |
|
PeerSync Standard Product Sheet
|
|
Peersync Standard Server Technical Features |
- Synchronize files in real time
- Byte-Block segment copying
- Instant recovery of lost data
- Save unlimited versions of copies to ensure multi-level file recovery
- Multi-process/threading capability
- Copy Open and Locked Files
- Continuous data availability with minimal resource utilization
- Failed network connection retry and re-direct
- Update changes automatically
- Improved distribution of network traffic
- Distribute files and applications simultaneously system-wide
- Update Web content 24x7
- Save time and overhead by synchronizing only changed oradded files
- Multiple operation modes
|
|
Peersync Flash Demo |
|
View Online Demonstration of PeerSync in macromedia Flash
|
|
|
PeerSync version 4 |
|
New Features
- The PeerSync installation and executables will now require administrative
privilidges to run on Windows Vista and Server 2008. When a standard user
tries to install or start the application they will be prompted for
administrative authorization or approval.
- Added a new default setting in PeerSync to exclude any folders that have
reparse points. Such folders are commonly used in Windows Vista and would
cause recursive querying. The /LJU:n command line argument can be used to
modify this behavior:
/LJU:0 - Don't exclude folders that have a Reparse Point object
/LJU:1 - Exclude folders that have a Reparse Point object recursively
pointing back to itself (Default)
/LJU:2 - Exclude all folders that have a Reparse Point object
- Added ability to remove milliseconds, seconds, or minutes from files during
comparison
/QF+++ - Removes/ignores the milliseconds, seconds, and minutes from both
the source and target file time stamps during comparison
/QF++ - Removes/ignores the milliseconds and seconds from both the
source and target file time stamps during comparison
/QF+ - Removes/ignores the milliseconds from both the source and target
file time stamps during comparison
Synchronization
- Resolved an issue where the "Use intermediate file during copy" option was
being ignored when enabled automatically.
- Added new functionality in PeerSync that creates a "Sending" and "Receiving"
hidden .PSLOCK file during Normal bi-directional file processing.
Example:
Source File: FILENAME.EXT.{USER_S_COMPUTER}.pslock
Target File: FILENAME.EXT.{USER_T_COMPUTER}.pslock
This will ensure that any event detected corresponding on a file currently
being processed by PeerSync will be ignored by all participating PeerSyncs
and PeerLocks. Furthermore, this functionality provides users with a display
of files in transit.
- Added new Open Files option that improves real-time bi-directional
replication/collaboration between more then two hosts. The new "Deny access
to source file during transfer" option uses custom logic to allow PeerSync
to replicate a file from one source to multiple destinations, in parallel,
while at the same time protecting the source file from write access. If a
user opens the source file while PeerSync is transferring it to its targets,
the user will be blocked for write access but may have the option to open
the file in read-only mode.
This new feature provides a solution to the problem of using the "Exclude
all open files until close" option which exclusively locked the source file
during transfer such that parallel transfer of one file to multiple targets
was not allowed.
- Fixed an issue where the following attributes were being set on source files
then transferred to the target: Read-Only (R), Hidden (H), System (S),
Archive (A), and Offline (O). This issue would occasionally occur with
Excel, AutoCAD, or other applications that momentarily delete the original
file as part of the file saving process.
- Fixed an issue where renaming files to a ~pstmp extension during renames
and/or deletes would get processed for incoming *.pstmp files.
- Fixed an issue where files were intermittently being missed during scans and
possibly during real-time.
- Fixed issue where files greater than 4 Gigs got truncated.
- Fixed an issue where Network Logon settings were being ignored.
- PeerSync now accepts the /T (Terminate All Instances of PeerSync) command
line argument either as upper case or lower case.
- Fixed an issue where PeerSync would not be able to delete folders that had
long paths. PeerSync would throw the following error: Cannot delete folder:
C:\... (The system cannot find the path specified)...
- Fixed an issue where PeerSync would fail to write to hidden folder files
during Enhanced Bi-Directional replication. This issue would occur only when
the file paths were too long.
- Resolved an issue where in some cases folder adds/deletes would cause
PeerSync on the target to trigger a folder add or delete event back to the
source (real-time bi-directional setup).
- Resolved an issue where files were replicated to incorrect locations. The
issue occurred when using multiple jobs with enhanced real-time event
processing enabled. In particular When two jobs were configured for
real-time monitoring (enhanced event processing on) with the source path for
the first job being a substring of the source path for the second job:
Example: Job 1 Source Folder = C:\Testsource
Job 2 Source Folder = C:\Testsource123
Files added to the source folder of the second job will be replicated to the
target folders of both jobs.
- Improved Enhanced Real-Time process to work better for file and folder
renames.
- Fixed an issue where PeerSync failed to re-add a file that has been deleted
and is being stored in the deletions folder.
- Resolved an issue where if Enhanced Event Processing was enabled, PeerSync
would process Real-Time events for NON Real-Time configured Jobs. In
particular, if two Jobs were identical except for the Target and Automation
settings (i.e. One configured for Real-Time, the other for Scheduled Scans),
the scheduled Job would also receive the Real-Time events.
PeerLock Compatibility
- Fixed an issue where file deletes and renames caused oscillation in PeerLock
on other machines.
- Fixed an issue where file exclusions configured by PeerSync were stored
under folder exclusions in PeerLock.
Performance
- Improved performance by no longer checking for lock files (*.PSLOCK) when
doing non-bidirectional replication.
- Improved performance when using multiple copy threads.
Enhanced Scanning / Performance
- Dramatically improved scan time when using the Enhanced Scanning option by
loading folder scans or dynamic jobs quicker.
- Fixed an issue where PeerSync incorrectly handled variable target paths when
using Enhanced Scanning. For example, when the target path was based on a
date or time variable that changed in the middle of the scan.
- Fixed an issue where PeerSync would intermittently miss files during a can
when using the Enhanced Scanning option.
- Fixed an issue where TCP pulls would fail when using Enhanced Scanning.
TCP Mode / TCP WAN Connector
- Fixed an issue where PeerSync failed to synchronize files in non real-time
using TCP mode where the source and target paths were equal.
Example
Source: C:\Testing\A
Target: TCP:\\server\C\Testing\A
- Fixed an issue where Variable paths for TCP Jobs were not being properly
converted on load of a Profile causing invalid paths to be created.
- Fixed an issue where during a TCP pull scenario PeerSync would not delete
disjoint files from the target folder when the option to "Delete unmatched
target files" was checked. PeerSync would report deletions but not actually
delete the files.
- Fixed an issue when using TCP source paths with an administrator share (i.e.
TCP:\\1.2.3.4\C$\Folder) would fail and cause the PSListener to go into an
infinite loop.
Exceptions
- Fixed issue where excluding Added or Updated files was not working in
real-time when using Enhanced Event Processing.
- Fixed a bug where file Inclusions based on attributes would not work.
Example: Including files with just the Archive attribute would actually
exclude files with the Archive attribute flag set.
- Fixed issue where PSLock files are reported as being excluded.
- Fixed an issue where exclusions based on file size in real-time were
not working.
ByteReplicator
- Added ability to exclude files using the *.ext format in addition to .ext or
ext.
- Fixed an issue where files containing at least two % characters would fail
during byte-level replication.
- Fixed an issue where during a byte-level pull scenario (remote to local)
PeerSync would use the local PSListener instead of the remote.
- Fixed an issue where byte-level file transfers for files with long paths
failed and 100% of the file would be updated.
FTP
- Fixed folder creation issues where PeerSync would fail to access or create
folders and throw one of the following errors:
Cannot create folder: FTP://.../FLDR
(550 /FLDR: File does not exist. (7))
or
Cannot create/goto target folder: FTP://.../FLDR
(550 /FLDR: File does not exist. (2)) (File does not exist. (2)) [550]
- Added ability to specify file types to transfer as ASCII using the *.ext
format in addition to .ext or ext.
- Fixed an issue When using FTP with Enhanced Event Processing that caused
connection failures. This issue would also cause PeerSync to report folder
adds as updates during Enhanced Real-Time. By default, on load of a Profile,
we now disable Enhanced Event Processing for FTP Target Jobs which have
Enhanced Real-Time enabled. This can be re-enabled from the interface or by
adding the /QYE+ switch to the list of Command Line Arguments.
Reporting
- Fixed issue where reporting of .PSTMP, .PSLOCK and other internal exclusions
would be logged.
- Now storing seconds when writing the modified time of files to the log file.
- Fixed an issue where files being Added on a Retry Cycle were being reported
or logged as Updated.
- Fixed TCP reporting issues where PeerSync would fail to report failures due
to invalid encryption settings (UserName or Password) as well as incorrectly
report copy file progress.
- Fixed an issue where PeerSync incorrectly displayed TCP Connection failure
messages for non-TCP Jobs. It now correctly reports connection failures.
- Improved reporting accuracy of attribute changes during enhanced scanning.
- Fixed an issue where Admin/Email advanced settings do not run when stopping
the Service from the Profiler.
- Resolved an issue where Enhanced Event Processing Caused file Adds to be
reported as Updates.
- Fixed an issue where a "Cannot create folder ..." error message was being
reported for each and every folder encountered if PeerSync lost connection
to the target during a scan.
- Resolved an issue where files that were excluded because they were GREATER
then x bytes was being reported incorrectly. The exception entry showed
the byte criteria for the exclusion to be the value of the "Exclude files
LESS then x bytes" instead.
Profiler/Interface
- Fixed an issue where random Options dialogs would appear when navigating
through the Profiler with multiple Jobs selected.
- Fixed an issue where occasionally the Profiler would display garbage when
PeerSync was running as a Service.
- Changed the Date Exceptions check boxes to radio buttons.
- Fixed an issue where the Profiler would display a modal dialog message after
installing the PeerLock service.
- Profiler changes made to PeerLock configuration options will now be saved
and stored out when hitting the PeerLock Launch or Start button from the
Profiler.
Status Display
- Improved "Added" statistics to show only the count of files that have been
added and no longer increment the count for folders added.
- Improved the Copy Thread Progress display to clean up files that have
completed during TCP and/or ByteReplicator transfers.
- Improved the "Checked" display to no longer increment when a *.PSLock file or
PeerLock stub file is detected and ignored.
- Fixed an issue where extensive flickering would occur when incrementing and
decrementing the Managed File List counter.
- Fixed an issue where status statistics were incorrectly displayed during
Enhanced Scanning.
Blackout Period
- Fixed an issue where during Blackout Periods PeerSync incorrectly reported
that folders were being added.
- Fixed an issue where under certain circumstances PeerSync would try to
process events during a blackout period. In particular, the issue would
occur when using Enhanced Event Processing.
File Compression
- Fixed an issue where real-time deletions with Enhanced Event Processing
would fail during File Compression and Expansion.
Revisioning
- Fixed an issue where the first Revision saved was a copy of the current file.
This would cause the Target file and first Revision to be the same. The first
Revision should be the previous version of the current file. This problem
occurred only if the Revision folder was located in a folder outside of the
Target folder.
EOFM/VSS
- Fixed an issue where VSS and/or EOFM prevent system log off, restart, and/or
shutdown.
- Added Tray Icon pop-up hint message to show and update the status of VSS or
EOFM when running.
Other Miscellaneous Enhancements/Improvements/Changes
- Resolved an issue where the running PeerSync Application would not allow the
computer to Shutdown, Restart, or Log Off. This issue occurred when any of
the following options/features were used:
- The Profiler was hidden using the /GLS command line argument
- The skins were disabled
- EOFM or VSS were enabled and running
This issue would not occur if PeerSync was running as a Service
===============================================================================
7.4.0 PSProfiler Interface and PeerSync Engine - 01/31/2008
===============================================================================
Profiler/Interface
- Customers who are running PeerLock v2.0.1 or higher on the same machine as
PeerSync will now be able to configure PeerLock directly from the PeerSync
Profiler. Configuration options include the ability to link specific
PeerSync Profile Jobs to PeerLock, ability to access/view/edit the PeerLock
Global Settings from the PeerSync Profiler, ability to install/uninstall the
PeerLock Service, as well as launch and view PeerLock directly from the
PeerSync Profiler.
- The Selection Tree can now be categorized into four sections: PeerSync,
PeerLock, Startup/Service, and Run/View. By default these categories will
not be shown unless you have PeerLock v2.0.1 or newer installed on the same
computer as PeerSync. You can manually display these categories by adding
PeerLock windows to the Customized tree mode.
- Changed the default Log file name to %JobName% that will resolve to current
Job name.
- Improved the display/load time of the Selection Tree (left panel) as well as
ensure that all necessary items are displayed within each display mode
(Basic, Intermediate, Advanced, and Customized).
- Improved general communication and connection issues between PeerSync and
the Profiler.
- Fixed an issue with the 'Send status information to PS Observer Utility'
option not being enabled in the interface when using the /GO argument.
- Added the ability to use the %UserProfile% Environmental Variable and other
variables that can be set via the set command from a command prompt.
- Improved ability to load Jobs that use variables (i.e. %HomeShare%) that
cannot be resolved by the machine perhaps due to network issues. The new
/QYV option will always try to resolve dynamic variables and not treat them
as folders. So when the laptop is not connected to the network, PeerSync
will go into a retry cycle and try to resolve the dynamic variable. Once the
variable can be resolved, synchronization will start.
- Improved Job Data Import for accurate display of Job Names.
TCP Mode / TCP WAN Connector
- PeerSync now supports real-time or scheduled bi-directional replication
using our TCP replication mode. To achieve real-time bi-directional
replication across TCP, PeerSync and PSListener would need to be installed
on both the Source and the Target machines. For scheduled bi-directional
replication across TCP, PeerSync would need to be installed on one side,
while the PSListener on the other. This feature is not supported when using
a TCP Source, FTP Source or FTP Target.
Bi-Directional
- Improved Enhanced Bi-directional capabilities so that relaying can occur
once a file has been added/updated to the target.
- Added improved logic for Enhanced Bi-directional synchronization where
PeerSync analyzes files against the TLR file to accurately determine what
actions need to be taken with the files.
- When selecting Bi-Directional replication, the Profiler will auto-select the
recommended "Use intermediate file during copy" option and turn off the
"Include attribute change as synchronization criteria" option.
Managed Files
- Added the "Volume Shadow Copy Service (VSS)" as a new open file manager
option. VSS has been integrated with PeerSync to provide another method for
processing open/locked files. In order to enable this feature you will
require the VSS add-on module. This method works well with applications
that are VSS compliant.
Performance
- Enhanced Scanning
Added the Enhanced Scanning option which provides the ability to build
multiple dynamic Jobs for parallel processing of folders during scans. This
will significantly improve the time PeerSync takes to scan trough directories.
By default PeerSync scans through a Job sequentially, one folder at a time.
With the Enhanced Scan option enabled PeerSync will spawn a Job Thread for
each folder it encounters during a scan. The user will be able to specify a
folder depth level (1-5) where PeerSync can spawn a Job thread for each
folder it encounters. The Enhanced Scanning and the Multi-Threading add-on
options are required for this feature to function.
- Enhanced Event Processing
Added the Enhanced Event Processing option which provides the ability to
parallel process real-time, retry or any other non-scan events. Enabling
this feature will improve the speed of synchronization during real-time or
any other non-scanning scenarios.
Miscellaneous
- Added new event trigger option that can be used in a multi-tier or relay
setup. With the "Trigger additional event after successful copy" option
checked, PeerSync will apply the time stamp of the target file after
successfully completing the file transfer in order to trigger an event on
the target side. This action will cause the PeerSync installed on the Target
to take further action with the file such as transferring it to another
location that is not accessible from the originating machine. This option
can also be used in a Hub and Spoke Bi-directional scenario where you would
enable the option on the spoke machines so that the events sent to the Hub
machine can be sent out to the other spoke machines in this type of a
scenario.
Exceptions
- Refined and expanded the "Include Attributes" Exceptions to now support the
following additional attributes:
Temporary
Offline
Encrypted
Compressed
Not indexed
Reparse point
Sparse
Virtual
- Added new "Exclude Attributes" functionality to identify which file/folder
attributes may be excluded. As with the "Include Attributes" Exceptions, the
same list of attributes are supported.
Reporting
- Added ACL Report File Content option to indicate whether or not any file or
folder ACL updates should be reported in the Log file.
- Improved reporting for ACL and Attribute updates during scans and real-time.
- Enhanced reporting to support accurate Enhanced Scanning statistics.
- Fixed an issue with the reporting of folder deletes during real-time. Folders
and files within them where reporting as a scan activity when
they should be reports as an event activity.
- Improved the creation of the Log file name when using extended Job Names.
- Fixed an issue where file updates using Microsoft Word where ignored when
using multiple copy threads with the "Replicate - Delete unmatched files'
option enabled and the default exclusions.
Status Display
- Accurately displays the total bytes transferred even when using the
ByteReplicator.
FTP
- Fixed a problem when pulling from certain FTP sites where the connection
would intermediately be lost and PeerSync would throw error messages.
- Fixed an issue where FTP source files added to the retry list were not being
processed.
- Fixed an issue where folders could not be created on certain FTP sites.
- Fixed an issue where target files where not cleaned up when a FTP source
file size was changed during a synchronization of the file.
Synchronization
- Fixed an issue where during scans the size of the file was not being checked
as a reason to update the file. If the date-time matched but the size was
different files were not being updated.
- Fixed issue where the "After synchronization subtract/add x minute(s) from
target was not working.
- Added global /GFA command line option that allows PeerSync to backup
Alternate Data Streams.
Recovery
- Improved recovery behavior to correctly identify files that need to be
recovered and properly utilizes existing PeerSync settings if enabled (i.e.
ByteReplicator or Use of temporary files). Recover is now also supported for
TCP Source or Target.
- Fixed issue where the Recovery mode would incompletely recover files and
leave them in a corrupt state.
- Fixed issue where some partial/incomplete files were seen as equal and were
not being recovered.
ByteReplicator
- Added ability for Read-Only .BRTMP files to be cleaned up properly.
- Fixed a ByteReplicator issue where it did not detect and transfer small byte
changes to the beginning of a source file.
|
|
More Technical Information about Peersync Standard Server |
- Set the read-write buffer size allowing for better optimization of network bandwidth
- Embedded Open File Manager
- File attribute transfer from source to target during synchronization operations
- Maximizes copy threads: gives or takes away priorities to certain filters
- International date/time format support
- Bandwidth throttling
- Command line operation and multiple configurations
- Bi-directional synchronization with SmartDelete
- Intelligently manage file deletions
- Scheduled archive folder clean-up
- Enhanced real-time file monitoring incorporates event-driven triggering
- File synchronization across different time zones
- Remote PeerSync Observer
- Multiple filter threads and copy threads for parallel processing of filters
- Variable path/folder naming conventions
- FTP site file synchronization
- Link profiles to external data source
- Additional administrative reporting capabilities
- NT file security descriptions (ACLs) are optionally transferred
- Check source and target files for binary match during folder scan/compare cycle and/or after successful file copy operation
- Daily Timer scheduling allows you to schedule specific filters or an entire Profile at selected days of the week
|
|
PeerSync Capabilities |
|
PeerSync Capabilities PeerSync offers varying levels of synchronization features. You can add functionality as your needs change without disruption to your organization?
|
|
PeerSync is Flexible and Scalable |
- Centrally administer PeerSync Profiles across your network. Run as a Windows NT/2000 service or application. Control of application priority for foreground or background operation.
- Perform synchronization across operating systems. PeerSync synchronizes Mac and PC files.
- With PeerSync installed on Windows machines, files can be synchronized to, from, and between Novell, Linux, or UNIX servers.
|
|
Ports used by PeerSync |
|
PeerSync can utilize up to three protocols during the synchronization process.
The three features that utilize the protocols are standard PeerSync network
operations (SMB), ftp synchroniztion (FTP), and TCP/ByteReplicator activity
(proprietary protocol).
SMB (CIFS Protocol)
When synchronizing between network shares, PeerSync will use the SMB (CIFS)
protocol for communication. In addition PeerSync will rely on the protocols
compression, encryption, and security credential systems as well.
This applies to
Windows to Windows relationships, as well as Windows to Non-Windows shares.
Generally the SMB ports used are in the range 136-139.
FTP Protocol
When synchronizing to and from an FTP location, the ftp protocol will be utilized
to provide authentication, command execution, and data transfer. Generally the
port FTP will utilize is 21 as well as a number of random non-standardized ports.
TCP and ByteReplicator Protocol
When synchronizing between shares, the ByteReplicator protocol can be used in
conjunction with the SMB (CIFS) protocol in order to provide smart data transfer
(Byte-Level transfer). This proprietary TCP protocol is by default operating on
port 7333, but can be modified to use any port.
When synchronizing to or from a TCP location, the TCP protocol will be use to
provide encryption, compression, data transfer, and general communication
between PeerSync and the Listener. This proprietary TCP protocol is by default
operating on port 7333, but can be modified to use any port.
|
|
Replicate Microsoft Cluster |
|
Configuring PeerSync to synchronize between clustered machines or between clustered and non-clustered machines.
Overview: When deploying PeerSync in a clustered environment, it is important to remember that PeerSync by itself is not a cluster-aware solution and will not utilize any clustering features.
Therefore it should be treated as just a normal service that runs on a single server.
PeerSync Real-Time Synchronization: In scenarios where PeerSync in a cluster environment will be synchronizing in real-time, it is recommended that a full licensed copy of PeerSync is running on all servers that will provide files or services similar to the original server hosting PeerSync. Each PeerSync will then be responsible for 2 tasks:
- Synchronizing local data to the intended target.
- Synchronizing local data to the other cluster machines.
These 2 tasks ensures that if another machine takes over, it will have the latest data available.
Please see the tutorial document called "Real-Time Bi-Directional Synchronization" for instructions on configuring this.
PeerSync Scheduled Synchronization: In scenarios where PeerSync in a cluster environment will be synchronizing on a schedule, it is recommended that a full licensed copy of PeerSync is installed on each server in the cluster that will provide files or services similar to the original server hosting PeerSync.
These additional installations do not need to be running, however they should be configured and ready to be started either manually or by scripted action. Each PeerSync will be responsible for 2 tasks:
- Synchronizing on a schedule the local data to the intended target (distribution), remote data to the local folder (backup), or in both directions (bi-directional).
- Synchronizing local data to the other cluster machines. (Optional)
Task 2 is optional because it may not be necessary for the cluster servers data to be
synchronized, in cases such as the source and target does not reside on any cluster machine.
Please see the tutorial documents called "Scheduled Synchronization" for instructions on configuring this.
|
|
|
|
|
Copyright © 2001 - 2010 AMT Software. All rights reserved. All trademarks are property of their respective owners. Information subject to change without notice. Revised 19/3/2010 |
|
|