Please enable JavaScript.

Coggle requires JavaScript to display documents.

Backup Options for AWS (Amazon Glacier (Archives support (Download -…

- - - - Connected to local network
      - Multiple users can access at the same time
      - They are scalable (RAID ing drives)
      - Some devices come with clustering, replication, and data consolidation options.
    - - Can have very fast SSDs or disk drives
      - Dedicated hardware (like fiber connections)
      - Ideal for providing high IOPS access to servers with different storage needs
      - Usually more expensive than using NAS
    - - fewer moving and fragile parts
      - Less susceptible to damage from dust, humidity, and other potential damage
      - Long term backups and archives
      - Not as fast for random access, but fast for sequential access
      - Can be used to complement disk drives as part of the backup strategy
- - - - Existing objects are unchanged
      - Added objects are given unique version IDs. Automatically generated by S3
    - - The delete marker becomes the current version
      - By default, GET requests retrieve the latest version
      - All versions remain in the bucket but S3 inserts a delete marker
      - If the current version has a delete marker, it returns 404 Not Found error
      - You can get previous versions by specifying an ID
      - To permanently delete a version, specify an ID
    - - Lifecycle Management can dictate what happens to versions after a certain amount of time
        
        Send non-current versions to Amazon Glacier after 30 days
        
        Permanently delete objects 180 days after the become noncurrent
        
        Can have separate policies for current and non-current versions
    - - Versioning Enabled
      - Versioning Suspended
      - Unversioned
    - - You can suspend versioning
      - Once version-enabled, a bucket cannot go back to being in an unversioned state