<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://www.lbackup.org/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://www.lbackup.org/feed.php">
        <title>LBackup developer</title>
        <description></description>
        <link>http://www.lbackup.org/</link>
        <image rdf:resource="http://www.lbackup.org/lib/tpl/mmClean/images/favicon.ico" />
       <dc:date>2026-04-30T15:58:17+0000</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/additional_useful_ssh_options?rev=1204105309&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/advanced_excludes_file_examples?rev=1314746285&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/automated_checking_of_the_backup_volume?rev=1257419587&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/automated_ssh_backup_script?rev=1256978815&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/backup_as_root_without_root_login?rev=1251419324&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/bandwidth_limiting?rev=1252893431&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/basicbackup?rev=1240204041&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/case_insensitivity_on_some_mac_os_x_file_systems?rev=1315269595&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/data_deduplication?rev=1320781724&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/data_verification?rev=1343852941&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/database_backups?rev=1261206189&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/dealing_with_sip?rev=1589361832&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/debian_build_notes?rev=1303693821&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/deployment_of_track?rev=1198571969&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/disk_image_backup?rev=1260156212&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/documentation_and_installation?rev=1227766441&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/email_reporting?rev=1265859178&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/filevault_integration?rev=1317190173&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/freenet_integration?rev=1226833228&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/fusecompress?rev=1293102696&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/hardware_storage_error_data_recovery?rev=1473122070&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/hardware_storage_error_detection?rev=1473122238&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/ignore_vanished_file_warnings?rev=1388966748&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/interesting_backup_projects?rev=1226185196&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/lvm_snap_shoots?rev=1280148168&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/migrating_backup_sets?rev=1331761102&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/mounting_attached_backup_devices?rev=1539907142&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/official_ssh_agent_instructions?rev=1259879409&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/osx_automount?rev=1373408072&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/overview?rev=1589361882&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/performance?rev=1305705473&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/pre_and_post_action_tools?rev=1258087848&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/raspberry_pi?rev=1458453002&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/removing_core_storage_volumes_and_volume_groups?rev=1495675370&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/restore_interfaces?rev=1198655562&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/rsync_blocksize?rev=1226635171&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/rsync_hfs?rev=1594179923&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/rsyncrypto?rev=1224900253&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/sort_term_road_map?rev=1342578218&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/speed_improvements?rev=1233617992&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/version_management?rev=1242178522&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/vmware_fusion_virtual_machine_backup?rev=1424344297&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/vulnerabilities?rev=1271452204&amp;do=diff"/>
                <rdf:li rdf:resource="http://www.lbackup.org/developer/zfs_snap_shoots?rev=1292277364&amp;do=diff"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://www.lbackup.org/lib/tpl/mmClean/images/favicon.ico">
        <title>LBackup</title>
        <link>http://www.lbackup.org/</link>
        <url>http://www.lbackup.org/lib/tpl/mmClean/images/favicon.ico</url>
    </image>
    <item rdf:about="http://www.lbackup.org/developer/additional_useful_ssh_options?rev=1204105309&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-02-27T09:41:49+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:additional_useful_ssh_options</title>
        <link>http://www.lbackup.org/developer/additional_useful_ssh_options?rev=1204105309&amp;do=diff</link>
        <description>Potentially Useful SSH options

	*  'from=“10.1.1.1”' ( This can be specified within the authorized keys file prior to the command=“” option )
	*  'SSH Wrapper' 'Another Link' 'Yet another link' 'and another (quite good tips - some listed below - separate with ',' )' 'and another
	*  '“PermitRootLogin forced-commands-only” in your /etc/ssh/sshd_config'
	*</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/advanced_excludes_file_examples?rev=1314746285&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-08-30T23:18:05+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:advanced_excludes_file_examples</title>
        <link>http://www.lbackup.org/developer/advanced_excludes_file_examples?rev=1314746285&amp;do=diff</link>
        <description>Advanced Exclude File Usage

This example assumes that you have set your backup path to “/” (root directory) on the source system. This example also assumes that you are running Mac OS X. 


/private/etc/ssh_config/
+ private     
+ private/etc/***
+ private/var/***
+ home/***
- *</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/automated_checking_of_the_backup_volume?rev=1257419587&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-05T11:13:07+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:automated_checking_of_the_backup_volume</title>
        <link>http://www.lbackup.org/developer/automated_checking_of_the_backup_volume?rev=1257419587&amp;do=diff</link>
        <description>Automatic Backup Volume Checking

Initial Steps

The first step to this is to create a script which checks the following properties of a backup volume. In addition, there should be checks in place for available free disk space (check elsewhere in the developer pages for details).</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/automated_ssh_backup_script?rev=1256978815&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-10-31T08:46:55+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:automated_ssh_backup_script</title>
        <link>http://www.lbackup.org/developer/automated_ssh_backup_script?rev=1256978815&amp;do=diff</link>
        <description>Automated SSH Backup Script Developer Page

This page is where links and ideas for the development of an SSH backup assist page are located.



Currently this aspect is on the drawing board but no work has started yet. If you have a working script then please submit this to the project.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/backup_as_root_without_root_login?rev=1251419324&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-08-28T00:28:44+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:backup_as_root_without_root_login</title>
        <link>http://www.lbackup.org/developer/backup_as_root_without_root_login?rev=1251419324&amp;do=diff</link>
        <description>Backup as Root

sudo approach

Q : How do I enable a full backup of the remote server without allowing root top log in to ssh? Can I somehow get rsync to login as a normal user and then do some kind of “sudo” command?

A : --rsync-path=“sudo rsync</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/bandwidth_limiting?rev=1252893431&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-09-14T01:57:11+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:bandwidth_limiting</title>
        <link>http://www.lbackup.org/developer/bandwidth_limiting?rev=1252893431&amp;do=diff</link>
        <description>Bandwidth Limiting

Trickle

RSync Bandwidth Limiting Example


rsync -auvPe &quot;trickle -d 80 ssh&quot; user@host:/src/ /dst/






	*  Details on trickle : &lt;http://monkey.org/~marius/pages/?page=trickle&gt;
	*  reference</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/basicbackup?rev=1240204041&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-04-20T05:07:21+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:basicbackup</title>
        <link>http://www.lbackup.org/developer/basicbackup?rev=1240204041&amp;do=diff</link>
        <description>Basic Backup Script

This is a very basic and rough script. 

It uses diskutil on Mac OS X to generate a disk image and then copy this disk image to a location. Improvements are welcome.


#!/bin/bash

##
## Very Basic backup script. V.00003
##

# Copyright 2006 Henri Shustak GNU GPU v3

## Settings

# Log File
logfile=&quot;&quot;

backup_name=&quot;Backup1&quot;

# Volume with Data
backup_src_volume=&quot;/Volumes/SoruceVolume&quot;

# This is messy - should be fixed
if [ &quot;${backup_src_volume}&quot; == &quot;/&quot; ] ; then
        # On…</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/case_insensitivity_on_some_mac_os_x_file_systems?rev=1315269595&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-06T00:39:55+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:case_insensitivity_on_some_mac_os_x_file_systems</title>
        <link>http://www.lbackup.org/developer/case_insensitivity_on_some_mac_os_x_file_systems?rev=1315269595&amp;do=diff</link>
        <description>Case Sensitivity OS X

On Mac OS X systems, if a file system is not specified as case sensitive then some matches will fail to detect issues. Perhaps a function will need to be implemented to resolve this situation. A test could be performed to check if a directory exists by changing directory into the directory and checking for an error exit code.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/data_deduplication?rev=1320781724&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-11-08T19:48:44+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:data_deduplication</title>
        <link>http://www.lbackup.org/developer/data_deduplication?rev=1320781724&amp;do=diff</link>
        <description>Data De-Duplication

	*  lessfs (high performance inline data deduplicating filesystem)
	*  HAMMER (distributed)
		*  FUSE details (LINUX/Mac OSX)
		*  HAMMER also has various other features which would be great for geographic redundancy.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/data_verification?rev=1343852941&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-08-01T20:29:01+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:data_verification</title>
        <link>http://www.lbackup.org/developer/data_verification?rev=1343852941&amp;do=diff</link>
        <description>Notes Regarding Data Verification






fingerprint

Using the fingerprint tool it should be possible to add some basic verification to LBackup.





rsync checksum Option

Adding the --checksum option is a possibility. Even if this only happens every x rotations. Currently it is possible to enable the</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/database_backups?rev=1261206189&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-19T07:03:09+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:database_backups</title>
        <link>http://www.lbackup.org/developer/database_backups?rev=1261206189&amp;do=diff</link>
        <description>Database Backups





MySQL

One option for MySQL database backups is to have a replica and then dump from the replica. This allows you to leave the primary database active and accessible during the dump.




Mac OS X Server

Below is a link to a script which you may use to create an archive of the Open Directory on a Mac</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/dealing_with_sip?rev=1589361832&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-05-13T09:23:52+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:dealing_with_sip</title>
        <link>http://www.lbackup.org/developer/dealing_with_sip?rev=1589361832&amp;do=diff</link>
        <description>SIP macOS

SIP (system integrity protection) is a feature of many recent versions of macOS. In 10.14.x Apple introduced privacy protection which means that programs are not able to access certain areas of any users home directory. The idea is to prevent malicious attacks (including data theft). This feature means that any program on MacOS 10.14.x or later needs to be granted full disk access in order to access various areas of the home (such as iPhoto Library / Mobile backups and much more).</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/debian_build_notes?rev=1303693821&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-04-25T01:10:21+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:debian_build_notes</title>
        <link>http://www.lbackup.org/developer/debian_build_notes?rev=1303693821&amp;do=diff</link>
        <description>LBackup Debian Build Notes

About this page

This page provides notes for building LBackup .deb packages. The process is currently quite manual. As the process becomes more automated then this page should be updated to reflect the process for building the lbackup .deb package.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/deployment_of_track?rev=1198571969&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-25T08:39:29+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:deployment_of_track</title>
        <link>http://www.lbackup.org/developer/deployment_of_track?rev=1198571969&amp;do=diff</link>
        <description>Track Deployment

Deploying track is one possibility for LBackup, currently we are consider a move to  Track for LBackup the LBackup development pages.



Will we or Wont We

We will wait and see....for now the doku wiki is doing just fine, but with more developers and more issues to manage, the move to an actual bug tracking system may be a good idea.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/disk_image_backup?rev=1260156212&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-07T03:23:32+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:disk_image_backup</title>
        <link>http://www.lbackup.org/developer/disk_image_backup?rev=1260156212&amp;do=diff</link>
        <description>Disk Image Backup

This topic relates backup scripts which rely upon the diskutil command which is available on Mac OS X. 
These scripts may be used to enhance the way LBackup works. There are similar utilities available on other operating systems. These notes should be expanded to cover other popular tools.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/documentation_and_installation?rev=1227766441&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-27T06:14:01+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:documentation_and_installation</title>
        <link>http://www.lbackup.org/developer/documentation_and_installation?rev=1227766441&amp;do=diff</link>
        <description>Basic Ideas

Below is a list of some basic ideas which should be implemented. If you are not working within Lucid then and are able to assist with the any of the following, then please submit patches directly to Lucid.




	*  Some better install scripts for *NIX operating systems (when downloading the source code)</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/email_reporting?rev=1265859178&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-11T03:32:58+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:email_reporting</title>
        <link>http://www.lbackup.org/developer/email_reporting?rev=1265859178&amp;do=diff</link>
        <description>Developer Page : Email Reporting

When are Emails Sent

Currently there a variety of situations when emails are not sent. With the default LBackup example configuration emails are only sent out if the backup has actually started. If a machine is not available for backup then this will not generate an email report. For automated notifications regarding these situations you should schedule the lmail program at a specific interval to report the status of the backups. Another possibility is to enabl…</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/filevault_integration?rev=1317190173&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-09-28T06:09:33+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:filevault_integration</title>
        <link>http://www.lbackup.org/developer/filevault_integration?rev=1317190173&amp;do=diff</link>
        <description>Improvements to LBackup FileVault Integration

About

This page contains information for LBackup developers regarding the simplification of Backup of Mac OS X FileVault users. Please note that the information on this page reefers to FileVault version one which is found in Mac</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/freenet_integration?rev=1226833228&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-16T11:00:28+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:freenet_integration</title>
        <link>http://www.lbackup.org/developer/freenet_integration?rev=1226833228&amp;do=diff</link>
        <description>Overview

FreeNet is a distributed encrypted storage system. This page is related to using LBackup FreenetFS for backups.

Approach

The best approach at present is to use FUSE to mount a storage area. Then backups can either be written to this area by a backup server or by the client directly. However, it is recommended that backups are sent via a backup server. This approach will avoid the deletion of files due to a rouge process or accident. Any time you are using a client to access a backup,…</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/fusecompress?rev=1293102696&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-12-23T11:11:36+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:fusecompress</title>
        <link>http://www.lbackup.org/developer/fusecompress?rev=1293102696&amp;do=diff</link>
        <description>FUSECompress

FUSEcompress is a possible way to reduce the storage space required for a backup set.




Related Links

	*  FUSEcompress
	*  Data de-duplication
	*  LBackup developer overview</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/hardware_storage_error_data_recovery?rev=1473122070&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-09-06T00:34:30+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:hardware_storage_error_data_recovery</title>
        <link>http://www.lbackup.org/developer/hardware_storage_error_data_recovery?rev=1473122070&amp;do=diff</link>
        <description>HDD Hardware Error Data Recovery

If the data on your drive is important and you have not yet backed up the data, then the best thing to do is to send your drive to a data recovery professional. DriveSavers based in the USA is our recommendation ; they offer you the best chance of recovering data from your system and when your data is important working with a professional service from the start is important. Attempting to recover data yourself or letting someone less experienced may work. Howeve…</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/hardware_storage_error_detection?rev=1473122238&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-09-06T00:37:18+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:hardware_storage_error_detection</title>
        <link>http://www.lbackup.org/developer/hardware_storage_error_detection?rev=1473122238&amp;do=diff</link>
        <description>Drive Hardware Error Detection

There are many ways of detecting hardware errors with your storage media including SMART status from a device. This page specifically focuses on using a tool to check a device for bad blocks. 




Tools to detect bad blocks</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/ignore_vanished_file_warnings?rev=1388966748&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2014-01-06T00:05:48+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:ignore_vanished_file_warnings</title>
        <link>http://www.lbackup.org/developer/ignore_vanished_file_warnings?rev=1388966748&amp;do=diff</link>
        <description>No Error on Vanished Files

During a backup rsync may issue the following warning : 
  rsync warning: some files vanished before they could be transferred (code 24)
Depending upon what you are backing up, your backup policy and requirements, this may be a serious issue. By default LBackup marks such backups as unsuccessful. In event that you wish to have such errors ignored and the backup to be marked as successful, then there are two approaches mentioned below to achieve this result.  Prior to …</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/interesting_backup_projects?rev=1226185196&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-08T22:59:56+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:interesting_backup_projects</title>
        <link>http://www.lbackup.org/developer/interesting_backup_projects?rev=1226185196&amp;do=diff</link>
        <description>Interesting Backup Projects

	*  LBackup
	*  Duplicity (Tutorial - Encrypted Backups)
	*  Link-Backup (intelligently handles renames, moves, and duplicates) 
	*  Distributed Internet Backup System
	*  rlbackup (similar to both rsnapshot and LBackup, support hard-linked snapshot file system backups) 

Interesting Related Projects</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/lvm_snap_shoots?rev=1280148168&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-07-26T12:42:48+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:lvm_snap_shoots</title>
        <link>http://www.lbackup.org/developer/lvm_snap_shoots?rev=1280148168&amp;do=diff</link>
        <description>LVM Snapshots

LVM snapshots offer a way to backups directories / partitions which are constantly changing, while reducing the downtime of any services which use these directories / partitions.

LVM Related Tools

	*  dsnapshot (high level tool for using LVM)</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/migrating_backup_sets?rev=1331761102&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-03-14T21:38:22+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:migrating_backup_sets</title>
        <link>http://www.lbackup.org/developer/migrating_backup_sets?rev=1331761102&amp;do=diff</link>
        <description>Migrating Backup Sets (Mac OS X)

This page is part of the developer section. As such there may be problems with this information. This page is intended to be the basis for yet to be developed backupset a migration tool, which will assist with migrating / moving backups between volumes. This tool would then be included with LBackup.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/mounting_attached_backup_devices?rev=1539907142&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2018-10-18T23:59:02+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:mounting_attached_backup_devices</title>
        <link>http://www.lbackup.org/developer/mounting_attached_backup_devices?rev=1539907142&amp;do=diff</link>
        <description>Mounting Attached Devices

This page is dedicated to the development of systems to mount attached devices. The hope is that this page will result in a variety of tools which will be able to assist pre and post action scripts.

Related Links

	*  Pre and Post Actions (information related to the pre and post action script system of LBackup)</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/official_ssh_agent_instructions?rev=1259879409&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-12-03T22:30:09+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:official_ssh_agent_instructions</title>
        <link>http://www.lbackup.org/developer/official_ssh_agent_instructions?rev=1259879409&amp;do=diff</link>
        <description>Developer : Instructions for Using an SSH Agent

This page is somewhere to gather good instructions or to write up setup instructions for using an SSH agent on various operating systems. 

This document is probably going to require construction by the LBackup team. However, the following links contain tutorials or other helpful information currently available on then internet.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/osx_automount?rev=1373408072&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2013-07-09T22:14:32+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:osx_automount</title>
        <link>http://www.lbackup.org/developer/osx_automount?rev=1373408072&amp;do=diff</link>
        <description>OS X Automount Notes

Below is one approach to configuring an AFP auto mount. You should carry out the following commands as root. Note that storing passwords like this is not advised due to security implications.




First create a directory for the auto mount(s).</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/overview?rev=1589361882&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-05-13T09:24:42+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:overview</title>
        <link>http://www.lbackup.org/developer/overview?rev=1589361882&amp;do=diff</link>
        <description>LBackup Developers Home Page




Welcome

The LBackup development process is completely open. Whether you are a developer or just interested in what is going on, you are welcome, contribute or have a look around or download the source code.



Developer Topics</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/performance?rev=1305705473&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2011-05-18T07:57:53+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:performance</title>
        <link>http://www.lbackup.org/developer/performance?rev=1305705473&amp;do=diff</link>
        <description>LBackup Performance

This page is related to performance issues relating to LBackup running on various platforms.




Tuning Rsync

 The '--whole-file' option may speed up transfers. However, in certain circumstances it could also slow down the transfer particularly on slow WAN links. Consider as an option for a future release.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/pre_and_post_action_tools?rev=1258087848&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-11-13T04:50:48+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:pre_and_post_action_tools</title>
        <link>http://www.lbackup.org/developer/pre_and_post_action_tools?rev=1258087848&amp;do=diff</link>
        <description>Pre and Post Action Tools

There are plans to implement a system either within LBackup or as a separate project which will offer a variety of tools which will simplify pre and post action scripts.

Essentially the goal is make the too offer a variety of cross platform tools which will allow the pre and post action scripts to also become more cross platform. If this is not possible initially. The hope is to at least offer support for common operations on some operating systems.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/raspberry_pi?rev=1458453002&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2016-03-20T05:50:02+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:raspberry_pi</title>
        <link>http://www.lbackup.org/developer/raspberry_pi?rev=1458453002&amp;do=diff</link>
        <description>Raspberry Pi as a backup server

It is possible to use a Rasberry Pi as a backup server. They may be used to pull or push backs. Please see the appropriate page(s) relating to the advantages of pull backups. Given the price points and low power requirements and small form factors, there are many reasons for using a Rasberry Pi as a backup server particularly for geo redundancy.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/removing_core_storage_volumes_and_volume_groups?rev=1495675370&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2017-05-25T01:22:50+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:removing_core_storage_volumes_and_volume_groups</title>
        <link>http://www.lbackup.org/developer/removing_core_storage_volumes_and_volume_groups?rev=1495675370&amp;do=diff</link>
        <description>Removing Core Storage Volumes and Volume Groups

If repartitioning a disk with DiskUtility is not possible using the command line and you see an error like the following : 
  # diskutil eraseDisk jhfs+ Macintosh\ HD  /dev/disk2
  Unable to begin erase operation: Placing a partition map on a 
  Core Storage logical volume is not supported (-69671)</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/restore_interfaces?rev=1198655562&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2007-12-26T07:52:42+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:restore_interfaces</title>
        <link>http://www.lbackup.org/developer/restore_interfaces?rev=1198655562&amp;do=diff</link>
        <description>Restore Interfaces

	*  This page has a link to a video about the Tardis restore system.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/rsync_blocksize?rev=1226635171&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-11-14T03:59:31+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:rsync_blocksize</title>
        <link>http://www.lbackup.org/developer/rsync_blocksize?rev=1226635171&amp;do=diff</link>
        <description>&gt; ... is there a flag in rsync which can change the
&gt; default block size?


man rsync says (in part):
        -B, --block-size=BLOCKSIZE This forces the block size used in  
the rsync algorithm to a fixed value. It is normally selected based on  
the size of each file being updated. See the technical report for  
details.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/rsync_hfs?rev=1594179923&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2020-07-08T03:45:23+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:rsync_hfs</title>
        <link>http://www.lbackup.org/developer/rsync_hfs?rev=1594179923&amp;do=diff</link>
        <description>Compiling Rsync with Resource Fork Support

This page contains resource links and information for compiling rsync to support resource forks on Mac OS X systems. If you have instructions on building an rsync binary which includes HFS+ suport then please submit a link to your instructions on this page. If you do not have somewhere to host your instructions then either</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/rsyncrypto?rev=1224900253&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2008-10-25T02:04:13+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:rsyncrypto</title>
        <link>http://www.lbackup.org/developer/rsyncrypto?rev=1224900253&amp;do=diff</link>
        <description>rsyncrypto

Below is information relating to how rsynccrypto support may be able to be added to LBackup. The purpose of this page is to allow LBackup developers to make moves to integrate support for rsyncrypto into the LBackup project.

Related Links</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/sort_term_road_map?rev=1342578218&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2012-07-18T02:23:38+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:sort_term_road_map</title>
        <link>http://www.lbackup.org/developer/sort_term_road_map?rev=1342578218&amp;do=diff</link>
        <description>Short Term LBackup Project Road Map

0.9.8r1

Released Monday 14th September 2009

	*  Improve the defaults so that a basic configuration file will be simpler to setup 
	*  Look at a locking system for when the backup is taking place
	*  Bundle a post hook script which will generate accurate date and time symbolic links to backup sections.</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/speed_improvements?rev=1233617992&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-02T23:39:52+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:speed_improvements</title>
        <link>http://www.lbackup.org/developer/speed_improvements?rev=1233617992&amp;do=diff</link>
        <description>Reducing Backup Times

	*  Recompile SSH (Needs further investigation)
	*  rsync blocksize
	*  rsync documentation regarding the re-coping of files modification times and file system file name storage (eg Mac OS X UTF-8 character sets)</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/version_management?rev=1242178522&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-13T01:35:22+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:version_management</title>
        <link>http://www.lbackup.org/developer/version_management?rev=1242178522&amp;do=diff</link>
        <description>LBackup Source Code Version Management

This page is dedicated to looking at moving the source code into a git repository. Hopefully, this page will soon be updated with details so you can clone the latest Lucid build.

If you are willing to deal with the minor issues relating to AppleScript and git then please</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/vmware_fusion_virtual_machine_backup?rev=1424344297&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2015-02-19T11:11:37+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:vmware_fusion_virtual_machine_backup</title>
        <link>http://www.lbackup.org/developer/vmware_fusion_virtual_machine_backup?rev=1424344297&amp;do=diff</link>
        <description>Backup of VMWare Fusion Virtual Machines

If you are backing up a VMWare Fusion virtual machine, you should snapshot, suspend or best of all shutdown (shutdown is recommended by VMWARE) the machine, before running the backup. Then once the backup has finished if you have shutdown or suspended the virtual machine you may start the virtual machine. Below are some helpful commands (as well as some links) for doing this on Mac</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/vulnerabilities?rev=1271452204&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-04-16T21:10:04+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:vulnerabilities</title>
        <link>http://www.lbackup.org/developer/vulnerabilities?rev=1271452204&amp;do=diff</link>
        <description>Vulnerabilities

rsync mailing list


&gt; Could attacker X on remoteserver alter the rsync binary in such a way
&gt; so it can traverse and change or read arbitrary files on localserver? 
&gt; Does running above command execute remote code or give remoteserver 
&gt; any kind of system access to localserver  (does the ssh tunnel work both ways???)
&gt; or is it &quot;pumping&quot; data through a dumb pipe just like for example rsync
&gt; over a samba share would and leaving all control to local?

You are wise to ask this q…</description>
    </item>
    <item rdf:about="http://www.lbackup.org/developer/zfs_snap_shoots?rev=1292277364&amp;do=diff">
        <dc:format>text/html</dc:format>
        <dc:date>2010-12-13T21:56:04+0000</dc:date>
        <dc:creator>Anonymous (anonymous@undisclosed.example.com)</dc:creator>
        <title>developer:zfs_snap_shoots</title>
        <link>http://www.lbackup.org/developer/zfs_snap_shoots?rev=1292277364&amp;do=diff</link>
        <description>ZFS Snapshots

Helpful Links

	*  Latest ZFS download for Mac OS X : &lt;http://code.google.com/p/maczfs/downloads/list&gt;</description>
    </item>
</rdf:RDF>
