Differences
This shows you the differences between the selected revision and the current version of the page.
| howto:backup_-_pc 2008/07/01 22:22 | howto:backup_-_pc 2017/09/06 18:38 current | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== DNS323 RSync Time Machine for Windows ====== | ====== DNS323 RSync Time Machine for Windows ====== | ||
| - | An interesting article titled "DNS323 RSync Time Machine!" was posted [[http://forum.dsmg600.info/t2125-DNS-323-Rsync-Time-Machine%21.html|here]] on the DNS323 forum. The author, raid123, brought to light some very interesting information regarding use of RSync's hard links. Following implementation of such on my NAS I couldn't help but wonder if a similar approach could be used to backup data from three Windows based PC's located throughout the household. Following a brief search of the Internet I was pleased to see tools capable of assisting in this regard were available. | + | An interesting article titled "DNS323 RSync Time Machine!" was posted [[http://dns323.kood.org/forum/t2125-DNS-323-Rsync-Time-Machine%21.html|here]] on the DNS323 forum. The author, raid123, brought to light some very interesting information regarding use of RSync's hard links. Following implementation of such on my NAS I couldn't help but wonder if a similar approach could be used to backup data from three Windows based PC's located throughout the household. Following a brief search of the Internet I was pleased to see tools capable of assisting in this regard were available. |
| \\ | \\ | ||
| + | |||
| ===== Assumptions ===== | ===== Assumptions ===== | ||
| Before getting started lets declare a few assumptions; | Before getting started lets declare a few assumptions; | ||
| Line 8: | Line 9: | ||
| - Volume_1 of the DNS323 contains user data | - Volume_1 of the DNS323 contains user data | ||
| - Volume_2 of the DNS323 contains backup data | - Volume_2 of the DNS323 contains backup data | ||
| - | - Your capable of adding folders to the DNS323 and setting user access rights | + | - You are capable of adding folders to the DNS323 and setting user access rights |
| - ffp version 0.5 is installed, configured and running without error. Check the fun_plug.log to be sure! | - ffp version 0.5 is installed, configured and running without error. Check the fun_plug.log to be sure! | ||
| - You have telnet or SSH access to the /ffp/* folders on your DNS323 | - You have telnet or SSH access to the /ffp/* folders on your DNS323 | ||
| Line 19: | Line 20: | ||
| \\ | \\ | ||
| + | |||
| ===== Basics Steps ===== | ===== Basics Steps ===== | ||
| Establishing a DNS323 RSync Time Machine for Windows requires; | Establishing a DNS323 RSync Time Machine for Windows requires; | ||
| Line 45: | Line 47: | ||
| Information in the table shows that User1 has access to all three folders while User2 has access to only the folder named Backup_PC2. | Information in the table shows that User1 has access to all three folders while User2 has access to only the folder named Backup_PC2. | ||
| \\ | \\ | ||
| + | |||
| ==== Add Cygwin and RSync for Windows ==== | ==== Add Cygwin and RSync for Windows ==== | ||
| - | Installation of a package known as Cygwin on all three Windows PC's is necessary. Cygwin provides an RSync client and allows creation of a symbolic link at the end of the backup process. As with raid123's approach for the "DNS323 RSync Time Machine!", a symbolic link named Current will take you to the latest backup directory. | + | Installation of a package known as Cygwin on all three Windows PC's is necessary. Cygwin provides an RSync client and allows creation of a symbolic link at the end of the backup process. As with raid123's approach for the "DNS323 RSync Time Machine!", a symbolic link named Current will take you to the latest backup directory. |
| \\ | \\ | ||
| \\ | \\ | ||
| Following instruction found at [[http://www.gaztronics.net/rsync.php|Gaztronics.net]], install "RSync for Windows". Although the instruction indicates three key Cygwin modules are required, I found that by installing the Cygwin GNU core utilities module (coreutils/coreutils-6.10-1) symlinks could be built thus allowing creation of a link to the latest backup. | Following instruction found at [[http://www.gaztronics.net/rsync.php|Gaztronics.net]], install "RSync for Windows". Although the instruction indicates three key Cygwin modules are required, I found that by installing the Cygwin GNU core utilities module (coreutils/coreutils-6.10-1) symlinks could be built thus allowing creation of a link to the latest backup. | ||
| \\ | \\ | ||
| + | \\ | ||
| + | There are transfer speed issues between the rsync 3.0.4 versions when using protocol 30. If encountered low transfer speeds (100KB/sec) downgrade the Cygwin rsync package to 2.6.9 to use protocol version 29. | ||
| ==== Create rsyncd.conf File ==== | ==== Create rsyncd.conf File ==== | ||
| Line 60: | Line 65: | ||
| max connections = 2 | max connections = 2 | ||
| secrets file = /ffp/etc/rsyncd.secrets | secrets file = /ffp/etc/rsyncd.secrets | ||
| - | + | ||
| use chroot = false | use chroot = false | ||
| read only = yes | read only = yes | ||
| Line 66: | Line 71: | ||
| strict modes = false | strict modes = false | ||
| # Deny access to all hosts just to be on the safe side | # Deny access to all hosts just to be on the safe side | ||
| - | hosts deny = * | + | hosts deny = * |
| timeout = 600 | timeout = 600 | ||
| dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz | dont compress = *.gz *.tgz *.zip *.z *.rpm *.deb *.iso *.bz2 *.tbz | ||
| Line 72: | Line 77: | ||
| [PC1Backup] | [PC1Backup] | ||
| - | comment = Primary Backup Location for PC1 | + | comment = Primary Backup Location for PC1 |
| - | # Allow access to local hosts | + | # Allow access to local hosts |
| - | hosts allow = 192.168.1.0/24 | + | hosts allow = 192.168.1.0/24 |
| - | read only = false | + | read only = false |
| - | gid = users | + | gid = users |
| - | uid = User1 | + | uid = User1 |
| - | auth users = User1 | + | auth users = User1 |
| - | path = /mnt/HD_b2/Backup_PC1 | + | path = /mnt/HD_b2/Backup_PC1 |
| [PC2Backup] | [PC2Backup] | ||
| - | comment = Primary Backup Location for PC2 | + | comment = Primary Backup Location for PC2 |
| - | # Allow access to local hosts | + | # Allow access to local hosts |
| - | hosts allow = 192.168.1.0/24 | + | hosts allow = 192.168.1.0/24 |
| - | read only = false | + | read only = false |
| - | gid = users | + | gid = users |
| - | uid = User1 | + | uid = User1 |
| - | auth users = User1, User2 | + | auth users = User1, User2 |
| - | path = /mnt/HD_b2/Backup_PC2 | + | path = /mnt/HD_b2/Backup_PC2 |
| [PC3Backup] | [PC3Backup] | ||
| - | comment = Primary Backup location for PC3 | + | comment = Primary Backup location for PC3 |
| - | # Allow access to local hosts | + | # Allow access to local hosts |
| - | hosts allow = 192.168.1.0/24 | + | hosts allow = 192.168.1.0/24 |
| - | read only = false | + | read only = false |
| - | gid = users | + | gid = users |
| - | uid = User1 | + | uid = User1 |
| - | auth users = User1 | + | auth users = User1 |
| - | path = /mnt/HD_b2/Backup_PC3 | + | path = /mnt/HD_b2/Backup_PC3 |
| </code> | </code> | ||
| Line 135: | Line 140: | ||
| In order for the RSync client on each PC to communicate with the DNS323, an RSync daemon needs to be running on the DNS323. Using Telnet or Putty access the DNS323 and set the execution bit of the rsyncd.sh file; chmod a+x /ffp/start/rsyncd.sh. Start the daemon by issuing an "/ffp/start/rsyncd.sh start" command. If all is well with your rsyncd.conf file the script should start with an indication of success. | In order for the RSync client on each PC to communicate with the DNS323, an RSync daemon needs to be running on the DNS323. Using Telnet or Putty access the DNS323 and set the execution bit of the rsyncd.sh file; chmod a+x /ffp/start/rsyncd.sh. Start the daemon by issuing an "/ffp/start/rsyncd.sh start" command. If all is well with your rsyncd.conf file the script should start with an indication of success. | ||
| \\ | \\ | ||
| + | |||
| Line 198: | Line 204: | ||
| Rem Save name of current backup directory; information is required next time batchfile runs | Rem Save name of current backup directory; information is required next time batchfile runs | ||
| echo %BkpDir% > %DOSBackUpPath%\LastBkpDate.dat | echo %BkpDir% > %DOSBackUpPath%\LastBkpDate.dat | ||
| + | |||
| Rem Delete shortcut to Previous Backup Directory | Rem Delete shortcut to Previous Backup Directory | ||
| - | if exist %DOSBackUpPath%\Current.lnk del %DOSBackUpPath%\Current.lnk | + | if exist %DOSBackUpPath%\Current.lnk C:\cygwin\bin\rm %CygwinBackUpPath%/current.lnk |
| Rem Change drive/directory and create shortcut to Current Backup Directory | Rem Change drive/directory and create shortcut to Current Backup Directory | ||
| Line 272: | Line 279: | ||
| ==== Schedule The Backup ==== | ==== Schedule The Backup ==== | ||
| Using the Windows Task Scheduler add a task to run the Backup.bat batch file on a regular schedule basis. I've set mine to run daily at 7:00PM. | Using the Windows Task Scheduler add a task to run the Backup.bat batch file on a regular schedule basis. I've set mine to run daily at 7:00PM. | ||
| + | |||
| ===== End Results ===== | ===== End Results ===== | ||
| - | Upon initial run of the Backup.bat batch file a directory (Named with the current date and time) along with two files and a link named current will be created. | + | Upon initial run of the Backup.bat batch file a directory (Named with the current date and time) along with two files and a link named Current will be created. |
| \\ | \\ | ||
| \\ | \\ | ||
| - | The file named LastBkpDate.dat contains the name of folder that was created during the last backup. The batch file uses this information to determine the location of the last backup. This information is in-turn passed to RSync so it may establish appropriate hardlinks. Do not modify this file or RSync will not create the hardlinks correctly. | + | The file named LastBkpDate.dat contains the name of folder that was created during the last backup. The batch file uses this information to determine the location of the last backup. This information is in-turn passed to RSync so it may establish appropriate hardlinks when performing the next backup. Do not modify this file or RSync will not create the hardlinks correctly. |
| \\ | \\ | ||
| \\ | \\ | ||
| The file named snapshot.log contains detail pertaining to the backup. Depending on the number of files being stored the initial entry may be large. Subsequent entries will reflect only those files changed since the last backup was performed. | The file named snapshot.log contains detail pertaining to the backup. Depending on the number of files being stored the initial entry may be large. Subsequent entries will reflect only those files changed since the last backup was performed. | ||
| + | \\ | ||
| + | \\ | ||
| + | The link named Current will take you to the last backup directory. | ||
| + | \\ | ||
| \\ | \\ | ||
| {{howto:backup:backup_-_pc:backedupfiles.png|}} | {{howto:backup:backup_-_pc:backedupfiles.png|}} | ||
