Differences between revisions 1 and 4 (spanning 3 versions)
Revision 1 as of 2016-03-19 08:44:17
Size: 160
Editor: PieterSmit
Comment:
Revision 4 as of 2016-03-23 18:14:23
Size: 783
Editor: PieterSmit
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
   * $ 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.
 * Then set AWS policy on s3 bucket to move older files to Glacier, and even delete very old files, e.g. after 700days.
Line 8: Line 15:
CategoryStorage 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.
  • Then set AWS policy on s3 bucket to move older files to Glacier, and even delete very old files, e.g. after 700days.

...


CategoryStorage CategoryDevelopement CategorySecurity

AWS (last edited 2022-05-05 00:26:05 by PieterSmit)