0000416: Backup using ssh - Openbravo Issue Tracking System

Notes
(0008887) pjuvara (reporter) 2008-09-04 20:03	Email exchange with client: > From: Morten Minke > Date: September 4, 2008 2:47:12 PM GMT+02:00 > To: Josep Mitjà > Subject: Re: Business Momentum request for the Openbravo Network 2.4 > > Hello Josep, > > I hope everything is very well in Spain. I just returned from a visit to Bonware in Finland (another Openbravo Partner as you might now). Although it was only two (intensive) days, the results were very promising. We have worked both on a development issue, as well as on a better cooperation between Openbravo partners. We all are very enthousiastic about this direction. > > Regarding your question. > > The issue is about the current backup options for openbravo network. Currently you can use NFS shares and Windows shares (SMB shares) or a local disc to transfer the backup to. > These options are well enough if the server is hosted at the clients location well separated from the internet. However, our servers are hosted in a datacenter and the backups are stored offsite in our office. Currently we use the SMB protocol for this, but this protocol is highly inappropriate for communication over a public network. > > Our suggestion therefor is to also create the option to use SSH for file transfers to another location. SSH can also use public key encryption where the public keys are stored on the openbravo server. This enables password less logins. If this is not desirable, a normal username/password option should also be present. > With SSH all data is encrypted, so all mission critical data can be send over unsecure lines. We think this is very important. > > Another issue with the current backup procedure is that the backup is directly created on the share. This creates a lot of network traffic during backup creation. It would be nice if the backup could be created locally on the openbravo server and after the backup is completed, the checksum can then also be generated on the openbravo server (this increases the backup speed a lot, because currently this also goes backup over the network). Once all files are generated, a simple file copy would be enough. If necessary, a roundtrip copy could be done to check if the filetransfer was succesfull (use the checksum again). > > I hope this makes it a bit more clear. If not, maybe Juan-Pablo can contact me through skype to discuss this in more detail. > > > Kind regards > > Morten Minke > Implementation Manager > > > www.businessmomentum.nl > > > ----- Original Message ----- > From: "Josep Mitjà" > To: "Jurgen Sant" > Cc: "Morten Minke" "Juan Pablo Aroztegui" > Sent: Wednesday, 3 September, 2008 5:58:37 PM GMT +01:00 Amsterdam / Berlin / Bern / Rome / Stockholm / Vienna > Subject: Business Momentum request for the Openbravo Network 2.4 > > Jurgen, > > The team is now preparing the Openbravo Network for 2.40, which is > going to include some improvements in the administration console. The > reason why I am writing is because you requested a new feature, which > we need understand better, before we can decide what is the best > design to solve the underlying problem. > > The feature request 0000446 is called Backup using SSH, and the > description of the request is: > > > Feature request filed by Business Momentum: > > Currently it is possible to select a NFS share, a local volume or a > > Windows share to store the backups. > > It would be very useful and much more secure over the internet if > > also a SSH target location could be selected. If the key of the > > target can be added, no username and password would even be necessary. > > Can you provide me with a description of the user story of how this > would be used? Also it would be good to understand why NFS or Samba > share is not enough for the use you need. > > Any inputs / insights / descriptions that you can provide to us at > this stage will he very beneficial. > > Best regards, > > Josep > Openbravo

(0074465) shuehner (administrator) 2015-02-13 20:11	This issue only applies to the old rPath Appliance which is not longer supported for a long time already.

Issue History
Date Modified	Username	Field	Change
2008-05-23 10:51	jpabloae	New Issue
2008-05-23 11:09	jpabloae	Issue cloned	0000417
2008-06-02 15:30	jpabloae	Assigned To	=> jpabloae
2008-07-04 10:50	pjuvara	Status	new => scheduled
2008-07-04 10:50	pjuvara	fix_in_branch	=> trunk
2008-07-04 10:52	pjuvara	Target Version	=> 2.40
2008-08-29 13:44	pjuvara	Tag Attached: Sprint-2
2008-09-04 20:03	pjuvara	Note Added: 0008887
2009-01-28 10:44	jpabloae	Category	=> SMB Network One
2011-08-24 12:58	jpabloae	Assigned To	jpabloae => gorka_gil
2012-07-19 13:11	gorka_gil	Category	Appliance stack => Appliance rPath
2015-02-13 20:11	shuehner	Note Added: 0074465
2015-02-13 20:11	shuehner	Status	scheduled => closed
2015-02-13 20:11	shuehner	Resolution	open => out of date

Relationships [ Relation Graph ] [ Dependency Graph ]