<rdf:RDF
    xmlns:rdf='http://www.w3.org/1999/02/22-rdf-syntax-ns#'
    xmlns:s='http://snipsnap.org/rdf/snip-schema#'
    xml:base='http://thinkberg.com/rdf'>
    <s:Snip rdf:about='http://thinkberg.com/rdf#start/2009-04-25/1'
         s:name='start/2009-04-25/1'
         s:cUser='arte'
         s:oUser=''
         s:mUser='arte'>
        <s:content>1 The next Backup iteration {anchor:The next Backup iteration}&#xD;&#xA;&#xD;&#xA;Finally I have a backup strategy for my server too. Not actually perfect, but it works for me. I even added backup of some data from my home RAID system and vice versa to it. The data is backed up to two different locations ({link:rsync.net|http://resync.net} and {link:Amazon S3|http://aws.amazon.com/s3}) and additionally to the RAID. Some data, like photos is transferred from the RAID to the Server and from there to Amazon S3. All Laptops backup to the RAID. That is too much data to be stored at either offsite location price-wise.&#xD;&#xA;&#xD;&#xA;All data transfer is encrypted. The data files are encrypted at either offsite backup but not on the RAID for easy access.&#xD;&#xA;&#xD;&#xA;{image:img=backup.png|align=middle} </s:content>
        <s:mTime>2009-04-25 21:23:54.859</s:mTime>
        <s:cTime>2009-04-25 21:17:12.736</s:cTime>
        <s:comments
             rdf:type='http://www.w3.org/1999/02/22-rdf-syntax-ns#Bag'/>
        <s:snipLinks>
            <rdf:Bag>
                <rdf:li rdf:resource='#snipsnap-search'/>
            </rdf:Bag>
        </s:snipLinks>
        <s:attachments>
            <rdf:Bag>
                <rdf:li>
                    <s:Attachment rdf:about='http://thinkberg.com/space/start/2009-04-25/1/backup.png'
                         s:fileName='backup.png'
                         s:contentType='image/png'
                         s:size='35003'>
                        <s:date>Sat Apr 25 23:23:54 CEST 2009</s:date>
                    </s:Attachment>
                </rdf:li>
            </rdf:Bag>
        </s:attachments>
    </s:Snip>
</rdf:RDF>