3 ms·
It's the latter. In a large enterprise, the backup configuration can be wildly complicated, a matrix of systems, schedules, slas, etc. Just reconfigure your bac
by thedougd 4y ago
It's the latter. In a large enterprise, the backup configuration can be wildly complicated, a matrix of systems, schedules, slas, etc. Just reconfigure your backup software to use this new virtual tape device and you're on your way.
- logifail 4y ago> Just reconfigure your backup software to use this new virtual tape device and you're on your way Isn't the whole point of tape that it is a physical thing, and may be taken offsite in a truck / stored in a vault, and all that jazz. "Just reconfiguring" your backup software sounds like a business might just bypass all that without necessarily realising the consequences. Then "we got hacked and our local backups are gone" -> "restore from offsite tape" -> "oh, actually there are no tapes, it's all the cloud now" -> ... ??
- orf 4y agoThen "we got hacked and our local backups are gone" -> "restore from offsite tape" -> "oh, actually all the tapes where stored at the wrong temperature or humidity and now they are fucked" -> ... ??
- kube-system 4y agoAWS's hard disks are a physical thing that is offsite
- logifail 4y ago> AWS's hard disks are a physical thing that is offsite Taking tapes to a secure offsite location means they're air-gapped from the source data, so even in a situation where an entire network is compromised, remotely-stored tapes can't be wiped/encrypted. I'm sure AWS has thought about this issue while designing Tape Gateway, but it's not clear to me how it could know whether a request to retrieve and overwrite a virtual tape was legitimate or not.
- thedougd 4y agoTape Gateway is just a gateway to S3. S3 offers WORM (Write Once Read Many) storage with Glacier and Object Lock. The slow retrieval for Glacier hints that AWS isn't using hard disks.