Jump to content

Search the Community

Showing results for tags 'backup'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • The Highlands
    • Announcements
    • Bruno's All Things Linux
    • All Things Windows
    • All Things Mac
    • Hardware
    • Mobility
    • Security & Networking
    • Social Media
    • The Restaurant at the Edge of the Universe
    • Forum Feedback

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...

Found 6 results

  1. I've always just used rsync and cron to keep backups of my user data, and clonezilla for doing a whole system image manually when big changes are afoot like dist-upgrades. I've been a bit slack about setting it up on my current system so I finally decide to enact a backup plan. I'm using rsnapshot this time as it is primarily for incremental backups and allows you to specify how many iterations of backups to keep and how often to run it. rsnapshot uses rsync to do the actual backup. I won't reinvent the wheel, pretty much just followed the excellent (as usual) guide on Arch wiki. This gives examples of how to run it regularly using systemd timers, rather than cron which most of the other guides use. https://wiki.archlinux.org/index.php/Rsnapshot
  2. https://wiki.archlin...ckup_with_rsync Well after me near disaster I thought it best to do a backup. So I followed the ARCH WIKI made a script called " phew.sh " placed it in a newly made folder called " ~/Scripts " (/home/me/Scripts) and followed the instructions, So I was quite surprised that me terminal tells me there is no " ~/Scripts/phew.sh ". However " # /home/me/Scripts/phew.sh /some/destination " does exist and the backup is now hopefully running. So am I doing something wrong with " # ~/Scripts/phew.sh /some/destination " or is the Arch Wiki wrong ?
  3. abarbarian

    BitTorrent Sync

    http://labs.bittorrent.com/experiments/sync/technology.html This looks like an excellent way to keep several or more pc's in sync as long as the pc's you want to keep synced are switched on at the same time. Looks like a very useful tool and I can see no cons with it. Much more secure than cloud offerings as all the files and folders are stored on your own pc's.
  4. I want to set up a backup system for my school laptop, my main computer, and my home file storage device. Clonezilla, a wonderful tool, is not what I want. I want something more flexible and faster. Here's what I am hoping it will do. 1 - Run a cron job on each computer once a week and make a local backup to external hdd and/or the home file storage device. 2 - Run a cron job once a month and make a backup of the home file storage device to my hosting account. Storage space is not an issue, I have tons, but compression would be nice. Time needed to make the backup is more important. I want to make the original run be a full restorable image of the entire hdd for each computer. Is there anything that will do that and then do incremental backups from there on? I would update it a couple times a year with a new full image to limit the number of incremental bits to add back in, in case of restore. Can I do this with just basic Linux tools? dd? rsync scripts? What else? I am in the early stages of learning all this stuff. What don't I know that I need to read up on?
  5. Mirroring My Slackware Partitions - Using Porteus (thumb drive) Linux > grsync as root (can also be done with rsync as root from terminal) - Porteus automatically mounts all available partitions. However, best to check > gparted to check mounting or > cd mnt to check Note: both source and destination must be mounted for rsync to work. - Open Terminal > su to root > start grsync - Set up session in grsync > check preserve user, permissions, time, groups, etc > check copy symlinks and hardlinks > uncheck verbose > choose source - add trailing / to prevent source directory creation on destination > choose destination > test run, if wanted > start live run - Repeat above for each partition to be mirrored - After mirroring completed, to make the mirror bootable as the original, fstab must be edited to correct for source/destination partition number discrepancies - Also edit GRUB to boot mirrored partition ===== For rsync, just make sure the source and destination are both mounted, then execute (as root): #rsync -a /dev/sd/ /dev/sd *Don't forget trailing / after source. ____________________________________________________________________________ rsync is VERY COOL! I should have been using this years ago to backup. It took about 45 minutes to mirror my 25Gig / and my 50Gig /home partitions. I can do this every Sunday. I'll never lose more than 7 days' worth of work this way. Unless, of course, my drive crashes, since both the original and source are on the same drive. I have two other drives on this system, though. Time permitting, I may set up one with the proper sized partitions to create a true backup. The current method is only to provide me with a usable Slackware if I should booger up my primary one somehow. So, there we go...
  6. Got the following in their April 2012 email newsletter today from SpiderOak: Any thoughts on SpiderOak? It's available for Windows, Mac and Linux; iOS and I believe Android as well. Are they safer than others? Is their encryption safe? Sounds like it's end to end encryption and no one sees your stuff. Think it's a legit claim? Think it can beat out Dropbox?
  • Create New...