|Subject:||Specifying a mapped drive for backup repository|
|Creation date:||7/14/10 11:26 AM|
|Last modified on:||9/10/10 11:46 AM|
Mapped drives for user repository
When a user is created in Syncrify, you have to specify a repository path where backup files are stored. Often users want to specify a remote folder or a mapped drive for user repository. In such case 3 machines get involved in the backup process:
Before you configure Syncrify to run in such configuration, following important information should be kept in mind
- Client machine
- Server machine - where Syncrify server is running
- Storage disk -this is where the actual backed file will reside
- Syncrify runs as a service on Windows. Mapped drives are usually NOT available to a service. Therefore, rather than using mapped drives use UNC path.
- The user account that is used to run Syncrify service must have permission to access the remote machine. By default, Syncrify service runs under Local System Account. Consider changing this to a local user who also has permission on the remote machine.
Log in to Syncrify web interface using the admin account
- Create a new user. If the user already exists you will have to delete the account and recreate it. This is because the account is also pinned to the folder where backup files are stored.
- Please a UNC path for the repository. For example:
Disadvantages of using a third machine
Although, using a third machine is possible, its use is discouraged. Syncrify's backup algorithm tries to minimize network traffic at the cost of local disk I/O. When you use a remote repository, you are increasing unnecessary network traffic between the machine where Syncrify server is running and the actual disk is stored. Refer to the image below.
When a network storage is used, three machines get involved:
The most important design goal in Syncrify is to reduce network traffic. This goal is achieved by using the rsync algorithm, which is used between machine 1 and 2. When a third machine is involved, this goal gets skewed and therefore, is discouraged.
- Syncrify client - this is where the original file stored
- Syncrify server - this is where the Syncrify server assumes the target file resides
- Storage disk - this is where the actual file is located. This could be a Windows machine or a NAS device
As a solution, consider installing Syncrify on the machine where the disk is local. You can even use a USB drive for the repository.
Add a comment to this document
Do you have a helpful tip related to this document that you'd like to share
with other users? Please add it below. Your name and tip will appear at the
end of the document text.