WORM storage compatibility
Problem to solve
Storing backups on WORM (Write One, Read Many) storage is important to protect backups against manipulation and corruption after they are taken. Our backups need to be compliant with this storage. This means that the backup service should not depend on being able to modify the content of a backup once written to disk. An example of where this may be necessary is when backups are chained together such as incremental backups. The backups need a way to reference the next backup in the chain.
Proposal
Guarantee that the backup service does not depend on the need to manipulate the backup contents after it has been written to disk.
Intended users
Feature Usage Metrics
TBD
Does this feature require an audit event?
TBD
Edited by Sampath Ranasinghe