New answers tagged backup
0
Would be strange of that was possible in OS X but not with Linux. It's exactly the same:
cd /cifs/dir
dd if=/dev/zero of=encbackup.img bs=1M count=100 # 100 MiB size
losetup /dev/loop0 /cifs/dir/encbackup.im # assuming loop0 is free
cryptsetup luksFormat /dev/loop0
cryptsetup luksOpen /dev/loop0 cr_cifs_backup
mke2fs -j /dev/mapper/cr_cifs_backup
mount -t ...
-2
To compress a folder with tar, the answer is:
~]# mkdir /office
~]# ll
~]# tar -cvf office.tar office
~]#
That is it.
2
It depends on whether the disk image is a full disk image, or just a partition.
Washing the partition(s)
If the disk is in good working condition, you will get better compression if you wash the empty space on the disk with zeros. If the disk is failing, skip this step.
If you're imaging an entire disk then you will want to wash each of the partitions on ...
2
First of all you should be aware of slapcat's limitations:
For some backend types, your slapd(8) should not be running
(at least, not in read-write mode) when you do this to ensure
consistency of the database. It is always safe to run slapcat
with the slapd-bdb(5), slapd-hdb(5), and slapd-null(5) backends.
So you better pack that backup in ...
1
I changed from rsnapshot to backintime exactly becuase of this problem. With backintime directories are named by date. They both use hardlinks, but backintime is a little smarter in that if nothing changes it doesn't bother making all the links. One difference is backintime changes the permissions of the files to be read only and save the permissions in a ...
0
There is another (better ?, safer ?) way to achieve what you want to do.
Instead of checking whether your backup drive is mounted, why not leave it plugged, but unmounted when it is not actually used.
This is probably better for the disk (some will just rest), and it
avoids accidental access to it. The cron job can mount it when it
starts and umount it ...
2
There is no “best way”. It all depends on your setup and requirements.
One way that also works if the backup directories contains lots of files would be to use snapshots on a lower level and send them to the remote server. ZFS can do that and probably LVM as well, but I never used that. You didn't state your file system or if you use a volume manager, ...
2
This has to do with the filesystem being used, not rsync itself. Assuming ext[234], look at extundelete. There are similar tools for other filesystems.
There is no guarantee that you will get the files back. The files will remain on disk once deleted, but the act of deleting is really marking the space that they occupy as being available to other files ...
0
Take a look at the official documentation.
Excerpt from that doc
Note that:
After the replication, both source and target directory will still be
completely ordinary directories. You can regard as a snapshot of
or vice versa. However, the most common usage of s3qlcp is to
regularly duplicate the same source directory, say documents, to
...
1
Just use tar to dump the data and getfacl/setfacl for storing/restoring the ACLs. Even if NTFS supported UNIX permissions you'd have to ensure mapping od user/group IDs and names, which tar does for you automatically (be aware that some - usually rather ancient or non-mainstream - versions of the utility don't store user/group names, only the numerical IDs).
...
6
Unfortunately, the NTFS permissions model and the Unix one don't look alike at all. There simply is no way to sanely map between them.
Use tar, but read the documentation carefully so all permissions get faithfully stored (including ACLs and SELinux contexts).
0
I suggest you to use bsdtar.
bsdtar backups extended ACL by default, it uses the same syntax as GNU tar, and the archives it produces are readable by GNU tar.
The package and command name (under Debian based distributions) is bsdtar.
bsdtar cf archive.tar /my/folder/using/extd_acl
bsdtar xf archive.tar
The 2nd (extract) command restores ACLs.
Top 50 recent answers are included
