Syncrify » Knowledge base

Document information

Document ID:1524
Subject:Repository path exceptions in Syncrify
Creation date:9/28/10 4:09 PM
Last modified on:6/5/13 10:12 AM



Repository path exceptions


When a user is created in Syncrify server, you have to specify a path where files are stored. This is called the repository path. Consider the following scenario where you create a user with the following values:

User's Name: John Doe
Login ID: john@acme.com
Repository path: C:\Backup

John, who has an account on Syncrify Server, wants to backup C:\IIS\wwwroot . Assume the profile name is WebServer.

By default, the files will be stored in the following folder on the target machine (where Syncrify server is running)

C:\Backup\john@acme.com\WebServer\wwwroot

Alternative approach
Consider using Junction Points on Windows or symbolic links on Linux to accomplish this goal.

Problem statement

Often you need to copy files on the server to the same location where they reside on the client. For example, if you are backing up C:\IIS\wwwroot on the client machine, you want the backed up files to go in the same location on the server.

Steps - version 3.0 and above

  • Login as admin to the web interface of Syncrify server.
  • Click Manager Users and then Repository Exceptions on the upper right hand side
  • To add a new exception, specify
    • Login Email - email address that identifies the user. For example john@acme.com
    • Profile Name - refers to the particular profile you want to change. For example WebServer
    • Absolute Path - Path on the server machine where files should be stored. For example: C:\IIS\wwwroot
  • Click Add


Steps - prior to version 3.0

In order to accomplish this task, you need to create a repository exception. Following steps demonstrate this task.
  • Locate the installation folder for Syncrify server. This usually C:\Syncrify on Windows and /opt/Syncrify on Linux /Unix and BSD. Let's call this $INSTALL_DIR
  • Create a new text file in $INSTALL_DIR\config\RepositoryExceptions.txt
  • Modify this file in any text editor. Each line of this file contains one repository exception in the following format

    john@acme.com|WebServer=C:/IIS

    This line contains 3 parts. First is the email address of the user followed by a pipe ( | ) symbol. The second part contains profile name followed by an equal ( = ) sign. Finally, specify the path where you want to files to appear.

    IMPORTANT: Use forward slash ( / ) instead of back-slash for directory separator, even on Windows machine.

  • Save the file
  • Restart Syncrify server


Once this RepositoryExceptions.txt file is found at runtime, Syncrify server will read the path from this file instead of actual path specified through the web interface.


User comments

Posted by Jason Parker on 6/4/13 8:49 PM

The problem statement is a bit unclear. It appears that the "problem" is when you want to redirect the backup path to something other than what is set up in the user profile. If this is the case, a statement to that effect would be very helpful. Also, the problem statement says "replicate" as if the exception creates a duplicate copy. One would be very wise to know--before setting up an exception--if this really replicates or simply redirects so that there is only one backup location. The "instead of" statement in the "steps prior to 3.0" section makes me think that the backup will only occur in one location on teh server and there is no "replication" of the files that wold otherwise be stored in the default location specified in the user profile. I am currently using an xcopy batch file and a Windows Scheduled Task to achieve what I believe this function does. It would be nice to know exactly what it does because it seems to be a cleaner way to have a backup location and a "working" location on the server.

Posted by Synametrics Support on 6/5/13 10:22 AM

Jason, we modified the language in the Problem statement section. I tried sending you an email but it bounced back due to quota limits on your account.

Posted by lemon on 2/10/11 8:21 PM

This is a really important note for some usage scenarios. May I suggest that this note is rewritten and expanded for clarity and provide more or better examples. I would also suggest that the software is updated in the next version to include this option rather than having to do a manual hack. The problem with the hack is how can I see that it is working correctly, before I potentially screw up something major? (By your own example, a pretty important directory c:/IIS...)

Posted by lemon on 2/10/11 8:51 PM

Let me add to the comment by saying that an "Analyse" button/tool would be useful. So rather than actually doing the backup, it would create a log of the differences it has found and therefore what WOULD be done through the backup. This TEST before EXECUTE is important, esp. in this server-server replication scenario.

Posted by md on 3/12/17 8:43 AM

I messed around with the steps described for almost and hour and still could not get backups to go where I was aiming. Just let us browse to the target folder and be done with it (See qnap's rsync system for an example). Qnap also has a test button as suggested above, I had to delete files and restart the server for each test as it is now. I like the logging and many other features of Syncrify, that's what brought me here after running into connection troubles with Qnap.


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.
Your name:
Your email:
Hide my email address
Verification code:
Enter the verification code you see above more submitting your tip
Tip:Please limit tips to 1000 characters

Navigation

Social Media

Powered by 10MinutesWeb.com