# 
# AUTHOR <EMAIL@ADDRESS>, YEAR.
#
msgid ""
msgstr ""
"Project-Id-Version: 0\n"
"POT-Creation-Date: 2010-12-19T10:13:17\n"
"PO-Revision-Date: 2010-12-19T10:13:17\n"
"Last-Translator: Automatically generated\n"
"Language-Team: None\n"
"MIME-Version: 1.0\n"
"Content-Type: application/x-publican; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Tag: title
#, no-c-format
msgid "Technical Information"
msgstr ""

#. Tag: title
#, no-c-format
msgid "Backup formats"
msgstr ""

#. Tag: para
#, no-c-format
msgid "This section details how fwbackups create backups and each type of backup's storage requirements."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Archive/tar backups"
msgstr ""

#. Tag: para
#, no-c-format
msgid "<guilabel>Archive</guilabel> backups use one of two methods to create the backup archive depending on the operating system. On Unix-like operating systems such as Linux, Unix and OS X, the <command>tar</command> executable is called upon directly to create a standard GNU tar archive, optionally with gzip or bzip2 compression. On Windows, Python's <ulink url=\"http://docs.python.org/library/tarfile.html\">tarfile</ulink> module is used to create a standard GNU compliant tar archive. In either case, backup compression is applied on-the-fly without the need for the tar archive to be created first."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Because the backup is in the format of a standard tar archive, should fwbackups ever fail to restore a backup any utility supporting the tar format such as GNOME's integrated <ulink url=\"http://library.gnome.org/users/file-roller/stable/\">file-roller</ulink> utility or <ulink url=\"http://www.7-zip.org/\">7-zip</ulink> on Windows may be used to extract files from the backup. For those confortable with the command line, a simple <command>tar xfz &lt;backup file&gt;</command> will extract all files from the backup."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Direct Copy/rsync backups"
msgstr ""

#. Tag: para
#, no-c-format
msgid "As with <guilabel>Archive</guilabel> backups, <guilabel>Direct copy</guilabel> backups will use one of two methods to copy files depending on the operatng system. On Windows, fwbackups uses a slightly modified version of the Python <ulink url=\"http://docs.python.org/library/shutil.html\">shutil</ulink> library to copy files and folders. On Unix-like operating systems (Linux, Unix and OS X) fwbackups determines the appropriate parameters and then makes a call to <command>rsync</command> to copy the files (rsync is faster than shutil and therefore is used when the OS supports it). Thus, in either case the result is a direct copy of the files and folder structure."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Because files have been copied directly, if fwbackups fails to restore your files simply copying them from the backup destination to their desired location via drag-and-drop in your file browser will suffice."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Minimum storage requirements"
msgstr ""

#. Tag: para
#, no-c-format
msgid "Depending on your backup format and destination, the minimum storage requirements to complete a backup may change."
msgstr ""

#. Tag: para
#, no-c-format
msgid "For local backups, both the <guilabel>Archive</guilabel> and <guilabel>Direct copy</guilabel> backup engines will copy files from the disk source to the destination without the need for temporary storage, even if compression is enabled. Therefore, you should have no problems backing up a full disk so long as your destination is on another volume such as USB or removable storage."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Backups to remote destinations have different storage requirements. <guilabel>Archive</guilabel> backups with a remote destination create the archive locally and then upload it via SFTP to the remote host. Therefore, you must have free space equal to the size of the files being backed up (unless compression is enabled, in which case slightly less would be required). In a <guilabel>Direct copy</guilabel> backup with a remote destination, files are uploaded directly to the remote machine and therefore it is possible to backup a full drive. However, be warned that a remote direct copy is significantly slower than a archive backup."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Preservation of file ownership and other attributes"
msgstr ""

#. Tag: para
#, no-c-format
msgid "fwbackups uses the internal Python <ulink url=\"http://docs.python.org/library/tarfile.html\">tarfile</ulink> and <ulink url=\"http://docs.python.org/library/shutil.html\">shutil</ulink> modules to restore files (and <ulink url=\"http://www.lag.net/paramiko/\">paramiko</ulink> for interfacing with remote hosts via SFTP). File permissions, modification time and access time are always preserved, as are symbolic links."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Local backups should preserve ownership on Unix-like operating systems, however OSs commonly do not allow regular users to change the ownership of files and thus the backup would need to be extracted manually as root in order to preserve ownership. Remote backups will not preserve ownership, as any files uploaded over SFTP assume the owner of the user used to connect to the remote machine. Please note that in the case of an archive backup to a remote host, this only applies to the actual archive file. The archive itself may contain file ownership information and once it has been retrieved from the remote host, it can be extracted manually similarly to a local archive backup if the user wishes to preserve file ownership."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Other file attributes, xattrs or ACLs may be stored in the backup (depending on the backup format, the OS the backup was created on and filesystem) however fwbackups will not attempt to restore them."
msgstr ""

#. Tag: title
#, no-c-format
msgid "Expected levels of reliability"
msgstr ""

#. Tag: para
#, no-c-format
msgid "fwbackups is a user backup program and accordingly, should be able to backup your user data without issues. Although it is possible to use fwbackups to backup an entire operating system, this was not its intended purpose and this scenario is as of yet untested. Users should expect fwbackups to successfully backup and restore their data, however (as described above) extra metadata such as file ownership, ACLs and extended attributes that an OS may require to function properly are not guarunteed to be restored along with the actual file data."
msgstr ""

#. Tag: para
#, no-c-format
msgid "Prior to each release of fwbackups, the code is put through a test suite which automates each possible type of backup and restore operation and verifies that each of those operations completed successfully. Nonetheless, unexpected bugs in software do happen and migitate the risk of unintentional data loss, users are recommended to check the fwbackups log regularly to ensure no errors are occuring, as well as periodically verify backups to ensure that no files are missing."
msgstr ""

