| |
|
| |
 IBackup for Linux/Unix |
| |
|
| |
|
| |
|
| |
|
| |
Sample script to backup a mysql database securely to an IBackup account: |
| |
The following example assumes root or administrator privileges to run stunnel and that the script is readable only by the root or owner as it contains the account password information.
mysqldump
sample_database > /usr/local/mysql_sample_database
stunnel
-c -d localhost:45873 -r too:5000
export
RSYNC_PASSWORD=ibackup_account_password
rsync -r -v -z -t/usr/local/mysql_sample_database
ibackup_account_username@localhost::ibackup
--port=45873
killall
stunnel
|
| |
 |
| |
|
| |
Can IBackup Professional Services create custom scripts based on my needs? |
| |
Yes. IBackup Professional Services has expertise in various Unix platforms including Linux and Solaris and can create customized scripts based on your needs. We have developed many custom scripts for our enterprise customers including data center users (to execute online backup of Oracle databases including clustered environments), mysql and other setups.
|
| |
|
| |
|
| |
Is there a way to specify the base directory to be used on IBackup? |
| |
If you wish to specify a base directory on your IBackup account, for example, my_ibackup_root/server1/home/backup/,
you can do so by creating a folder
/server1/home/backup in your IBackup account, using the browser interface.
Next, backup your data using rsync as follows
rsync -r -v -z -t/home/backup
<ibackup username>@too::ibackup/server1/home/backup. |
| |
|
| |
|
| |
How do I use the Snapshots feature to restore from a previously stored data file using rsync on Linux? |
| |
To view previously stored data with 'Enable Snapshot view' feature for rsync on Linux and other platforms, follow the steps listed below:
1. Login via the browser and click 'Preferences' under the 'Account Maintenance' section. Select the 'Enable Snapshots view'.
2. Keep your browser session open. Make a note of the directories from which you want to restore data. Then, using rsync and the directories that you have noted, apply the requisite rsync commands to restore data from Snapshots.
Close the Web-Manager session when you are done with the restore.
|
| |
|
| |
|
| |
When I restore data, the permissions and owner/group information is different from source. Why? |
| |
IBackup's rsync server stores your data with a fixed owner/group and set of permissions that may be different from original set of owner/group and permissions. After you restore the data, ensure that the permissions and ownership information is modified appropriately.
For this, create and store a separate document locally that has information on the ownership and permissions information of your data.
|
| |
|
| |
|
| |
Is
there a work around to the owner/permissions issue with rsync for Linux/Unix ? |
| |
Yes. Use the 'tar' command to compress all the 'files to be backed up' on the server into one file and then transfer it to IBackup for backup. The single file that tar generates (called a 'tar ball') preserves all the files with their permissions. Just un-tar it again to restore.
1. To backup, go to the directory containing the files and
tar cvpf <tarball-filename.tar>
*
(this also takes in all sub directories as well)
2.
To see what is inside the tarball
tar tvf <tarball-filename.tar>
3.
To extract the tarball
tar xvpf <tarball-filename.tar> |
| |
|
| |
|
| |
Does backing up compressed files created using gzip method negate the rsync patching effect and result in full transfers each time? |
| |
Yes. However, if you are technically inclined, then apply the rsyncable patch to gzip that allows rsync to do efficient patching. The link to the patch is mentioned below. It is easy to recompile gzip with the patch.
http://rsync.samba.org/ftp/unpacked/rsync/patches/gzip-rsyncable.diff
for the patch
http://www.gzip.org for gzip source
It is possible that the newer gzip on most installations includes this rsyncable patch. You may only need to provide an option '--rsyncable' to your standard compression command using gzip. Check by typing 'gzip -h' before applying the patch. |
| |
|
| |
|
| |
What
are the supported rsync options? Are there any limitations? |
| |
IBackup's
rsync server side application has been recently changed to error out if clients
send out requests that involve 'links' in the options.
IBackup's
rsync compatibility does not include certain options that are explicitly related
to symbolic links and hard links such as '-l' , '-L' , '-H' , and options such
as '-a' that implicitly use links. Most other standard rsync options are supported.
|
| |
|
| |
|
| |
How do I restore directories from my IBackup account to the local machine? |
| |
Use the syntax below to restore directories from your IBackup account to the local machine:
$ rsync -r -v -z -t <ibackup username>@too::ibackup/<your
directory in IBackup Account> <destination directory on local machine>.
|
| |
|
| |
|
| |
Is it advisable to backup the .htaccess file? |
| |
Backing up the ".htaccess" files from your local computer to the IBackup
server will create problems when you try to access your account. Hence, we
recommend that you to skip these files.
Instead, create a copy of the ".htaccess" files as "htaccess_copy" and back them up. The rsync command to skip the ".htaccess" files would include "--exclude" option and would be similar to
"rsync -r -v -z -t --exclude=.htaccess /home/backup < ibackup username > @too::ibackup."
|
| |
|
| |
|
| |
|
