Feedback on immutability
-
Introduced in XO 5.91, we need people to make their own tests and report. You are welcome here!
See https://xen-orchestra.com/blog/xen-orchestra-5-91/ for details -
-
@olivierlambert Going to follow this post closely, may not have time to test super soon but will try to when I can.
Curious, I know it may be a ways off, but is there plans for immutable S3/Backblaze type remotes?
-
It is already working with any external S3 supporting immutability. It's exactly the same concept, but not on-prem You just setup the retention in your S3 console and that's it.
-
@olivierlambert Awesome, I'll test this as soon as I can and try to post about my experience with it. If all goes well I'll do a writeup/how to.
Thanks!
-
tried to run it.
root@xo-rp:/mnt/test# xo-immutable-remote /usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:311 throw this.error(new TomlError('Unexpected character, expected only whitespace or comments till end of line')) ^ TomlError: Unexpected character, expected only whitespace or comments till end of line at row 4, col 15, pos 122: 3: # some files need to be made mutable 4> liftEvery = 1h ^ 5: at TOMLParser.parseWhitespaceToEOL (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:311:26) at TOMLParser.runOne (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/parser.js:64:30) at TOMLParser.goto (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/parser.js:87:17) at TOMLParser.recordAssignStatement (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:337:19) at TOMLParser.runOne (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/parser.js:64:30) at TOMLParser.returnNow (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/parser.js:107:17) at TOMLParser.recordAssignValue (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:380:19) at TOMLParser.runOne (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/parser.js:64:30) at TOMLParser.returnNow (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/parser.js:107:17) at TOMLParser.parseNumberOrDateTimeOnly (/usr/lib/node_modules/@xen-orchestra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:934:21) { fromTOML: true, wrapped: null, line: 3, col: 14, pos: 122 } Node.js v18.19.0
@olivierlambert said
If everything works well, you can then start it as a service, for example with systemd (we'll provide an example service file).
still nope
-
Ping @florent
-
@Tristis-Oris in the toml , the string should be between quotes
so liftEvery = "1h"
-
We need to correct the blog post then