Difference between revisions of "Talk:Synchronization and backup programs"

From ArchWiki
Jump to: navigation, search
(Spideroak)
m (rm closed discussions)
(11 intermediate revisions by 8 users not shown)
Line 1: Line 1:
== Misleading info about rsync? ==
+
== should we mention par2cmdline? ==
"Impossible to restore a full backup before the most recent backup"
+
This sounds incorrect. I can restore full backups before the most recent backup using something similar to [http://blog.interlinked.org/tutorials/rsync_time_machine.html]. --[[User:Markus00000|Markus00000]] 13:07, 11 November 2011 (EST)
+
  
== Spideroak ==
+
 
Spideroak [https://spideroak.com/download/] in the AUR is another cloud-based alternative --[[User:Markus00000|Markus00000]] 13:12, 11 November 2011 (EST)
+
I had used parchive before and was looking for its packagename for it here. Maybe it should be mentioned. Feels backup-related enough to me.
 +
 
 +
Thanks
 +
--[[User:Kristianlm|Kristianlm]] ([[User talk:Kristianlm|talk]]) 13:01, 15 October 2012 (UTC)
 +
 
 +
== Guidelines for adding programs? ==
 +
Should a particular program (assuming it is open source) already have a package created for ArchLinux before adding it to this list?  Also, what if it is relatively new, and doesn't have a lot of users yet, should it go through a minimum amount of other user testing before adding it?  In the interest of full disclosure, I have recently contributed a backup system as open source (currently hosted on github), that I've personally used for a while -- it is similar in concept to the rsync-based backups, but it includes full file level deduplication (even across multiple clients), an SQLite-based catalog, and the client side uses standard GNU tar, find, and a wrapper shell script (no binaries to install on the client side).  So you end up with the simplicity of rsync, with some of the features of the heavy-weight backup programs.
 +
 
 +
Thought I would ask here first before posting a writeup on the main wiki page -- don't want to appear like I'm spamming links or anything.  [[User:Derekp7|Derekp7]] ([[User talk:Derekp7|talk]]) 01:48, 17 February 2013 (UTC)
 +
: You are free to add your tool. But since this is an Arch Wiki, the tool should be easily accessed by Arch user. I think at least a [[AUR]] package is needed. Create a [[AUR]] package is very easy. See the [[AUR]] and [[PKGBUILD]] for how to. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 07:42, 17 February 2013 (UTC)
 +
 
 +
== Cloud backups ==
 +
 
 +
Can I add these tree other options or they are not suitable by any reason?
 +
 
 +
- Drive[https://tools.google.com/dlpage/drive] - AUR[https://aur.archlinux.org/packages/grive/]
 +
- Copy[https://www1.copy.com/home/] - AUR[https://aur.archlinux.org/packages/copy/]
 +
- Bitcasa[http://www.bitcasa.com/] - AUR[https://aur.archlinux.org/packages/bitcasa/]
 +
 
 +
--[[User:Gbc921|Gabriel B. Casella]] ([[User talk:Gbc921|talk]]) 21:37, 13 December 2013 (UTC)
 +
 
 +
:Sure, considering that MEGA is listed in [[Backup_Programs#Cloud_backups]], these three would fit there much better ;) But please keep the structure the same as for other software. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 22:01, 13 December 2013 (UTC)

Revision as of 22:02, 13 December 2013

should we mention par2cmdline?

I had used parchive before and was looking for its packagename for it here. Maybe it should be mentioned. Feels backup-related enough to me.

Thanks --Kristianlm (talk) 13:01, 15 October 2012 (UTC)

Guidelines for adding programs?

Should a particular program (assuming it is open source) already have a package created for ArchLinux before adding it to this list? Also, what if it is relatively new, and doesn't have a lot of users yet, should it go through a minimum amount of other user testing before adding it? In the interest of full disclosure, I have recently contributed a backup system as open source (currently hosted on github), that I've personally used for a while -- it is similar in concept to the rsync-based backups, but it includes full file level deduplication (even across multiple clients), an SQLite-based catalog, and the client side uses standard GNU tar, find, and a wrapper shell script (no binaries to install on the client side). So you end up with the simplicity of rsync, with some of the features of the heavy-weight backup programs.

Thought I would ask here first before posting a writeup on the main wiki page -- don't want to appear like I'm spamming links or anything. Derekp7 (talk) 01:48, 17 February 2013 (UTC)

You are free to add your tool. But since this is an Arch Wiki, the tool should be easily accessed by Arch user. I think at least a AUR package is needed. Create a AUR package is very easy. See the AUR and PKGBUILD for how to. -- Fengchao (talk) 07:42, 17 February 2013 (UTC)

Cloud backups

Can I add these tree other options or they are not suitable by any reason?

- Drive[1] - AUR[2]
- Copy[3] - AUR[4]
- Bitcasa[5] - AUR[6]

--Gabriel B. Casella (talk) 21:37, 13 December 2013 (UTC)

Sure, considering that MEGA is listed in Backup_Programs#Cloud_backups, these three would fit there much better ;) But please keep the structure the same as for other software. -- Lahwaacz (talk) 22:01, 13 December 2013 (UTC)