|
Size: 295
Comment:
|
Size: 1297
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| * [[https://live.awsevents.com/?sc_channel=em&sc_campaign=chicagosummit2016&sc_publisher=aws&sc_medium=em_13869&sc_content=launch_t1launch_tier1&sc_country=global&sc_geo=global&sc_category=mult&sc_outcome=launch&trk=ema_13869&mkt_tok=eyJpIjoiTWpZMk1XTmtPVGRrTmpnMSIsInQiOiJVb3VIVURraVRGNTRKNEtWNzNjNTlJWmlPUmRwSDRyWFhzaG1PSHY1YXJcL0swRnpKd1BhUEFMdzNGMU53UTd4Mkd6WlJyM1htWGladlNBNHpZMk1sUTIxR3NzTlB4RDdOYnVvaDlZRHErXC9RPSJ9|2016-aws-live]] * [[https://aws.amazon.com/partners/success/infor/|AWS-Partner-infor]] |
|
| Line 7: | Line 9: |
| * s3cmd mb s3://backupVigor {{{ Bucket 's3://backupVigor/' created }}} * Use tar with incremental option to backup files, pipe through xz to compress, pgp to encrypt if needed and then pipe straight to s3cmd, into backup file. * 20160322 - This works great, and no need for a local copy of the file while creating the backup. * Then set AWS policy on s3 bucket to move older files to Glacier, and even delete very old files, e.g. after 700days. |
|
| Line 10: | Line 17: |
| CategoryStorage CategoryDevelopement | CategoryStorage CategoryDevelopement CategorySecurity |
Amazon Web Services - Cloud provider
- on linux can use $s3cmd to backup to S3 storage in AWS.
- $ s3cmd --configure
get keys from http://aws.amazon.com/ User Name,Access Key Id,Secret Access Key
- s3cmd mb s3://backupVigor
Bucket 's3://backupVigor/' created
- Use tar with incremental option to backup files, pipe through xz to compress, pgp to encrypt if needed and then pipe straight to s3cmd, into backup file.
- 20160322 - This works great, and no need for a local copy of the file while creating the backup.
- $ s3cmd --configure
- Then set AWS policy on s3 bucket to move older files to Glacier, and even delete very old files, e.g. after 700days.
...