Feedback on immutability

Tristis Oris

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

olivierlambert

Ping @florent

florent

@Tristis-Oris in the toml , the string should be between quotes

so liftEvery = "1h"

olivierlambert

We need to correct the blog post then

rtjdamen

@olivierlambert we are using synology nas as backup repositories, do u have any experience with them on this subject?

olivierlambert

Not specifically with them, but if we can run a program inside this, we could have immutability (maybe you can even configure it at Syno level?)

john.c

@olivierlambert said in Feedback on immutability:

Not specifically with them, but if we can run a program inside this, we could have immutability (maybe you can even configure it at Syno level?)

Synology has a developers program, which people can join, through this it's possible for a version of the immutability service developed for Xen Orchestra, to be deployed as a packaged program on one of their NAS products.

https://www.synology.com/en-us/support/developer

Check out the above link for more information.

rtjdamen

@john-c @olivierlambert i have installed nodejs on the synology box, i installed the application

i am not shure if it actually is installing, i tried to go to /etc/xo-immutable-remote/ but the directory is not there, do i need to create it or should this have been installed?

rtjdamen

I created the directory and config file and tried to start the application but it get the follwoing error

xo-immutable-remote
/usr/local/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 whit                                              espace or comments till end of line'))
                        ^

TomlError: Unexpected character, expected only whitespace or comments till end o                                              f line at row 4, col 15, pos 122:
3: # some files need to be made mutable
4> liftEvery =  1h
                ^
5:


   at TOMLParser.parseWhitespaceToEOL (/usr/local/lib/node_modules/@xen-orchest                                              ra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:311:26)
   at TOMLParser.runOne (/usr/local/lib/node_modules/@xen-orchestra/immutable-b                                              ackups/node_modules/@iarna/toml/lib/parser.js:64:30)
   at TOMLParser.goto (/usr/local/lib/node_modules/@xen-orchestra/immutable-bac                                              kups/node_modules/@iarna/toml/lib/parser.js:87:17)
   at TOMLParser.recordAssignStatement (/usr/local/lib/node_modules/@xen-orches                                              tra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:337:19)
   at TOMLParser.runOne (/usr/local/lib/node_modules/@xen-orchestra/immutable-b                                              ackups/node_modules/@iarna/toml/lib/parser.js:64:30)
   at TOMLParser.returnNow (/usr/local/lib/node_modules/@xen-orchestra/immutabl                                              e-backups/node_modules/@iarna/toml/lib/parser.js:107:17)
   at TOMLParser.recordAssignValue (/usr/local/lib/node_modules/@xen-orchestra/                                              immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:380:19)
   at TOMLParser.runOne (/usr/local/lib/node_modules/@xen-orchestra/immutable-b                                              ackups/node_modules/@iarna/toml/lib/parser.js:64:30)
   at TOMLParser.returnNow (/usr/local/lib/node_modules/@xen-orchestra/immutabl                                              e-backups/node_modules/@iarna/toml/lib/parser.js:107:17)
   at TOMLParser.parseNumberOrDateTimeOnly (/usr/local/lib/node_modules/@xen-or                                              chestra/immutable-backups/node_modules/@iarna/toml/lib/toml-parser.js:934:21) {
 fromTOML: true,
 wrapped: null,
 line: 3,
 col: 14,
 pos: 122
}

john.c

@rtjdamen said in Feedback on immutability:

@john-c @olivierlambert i have installed nodejs on the synology box, i installed the application

i am not shure if it actually is installing, i tried to go to /etc/xo-immutable-remote/ but the directory is not there, do i need to create it or should this have been installed?

Things on a NAS especially Synology NAS is different, as its not a normal Linux. It's been customised and developed by Synology so the structure is different, also packages may be missing that are expected as well as different versions.

So may be worth working with Vates on a Synology developer account and then having a GitHub repository with a port for the Synology.

rtjdamen

@john-c ok, @olivierlambert any chance we can get someone to look into this?

rtjdamen

@john-c @olivierlambert i will check out with our own developers what we can do on this subject, maybe we can help develop a draft application/package here. keep u posted on the results.

olivierlambert

We are pretty busy right now (release week), but we'll try to take a look later (@marcungeschikts will try to find someone available later on)

rtjdamen

@olivierlambert i understand, i will let u know the results on our end as well.

john.c

When working on this later on it maybe worth checking out lru-cache to see if inflight can be replaced. Due to inflight not being supported and leaks memory.

rtjdamen

@olivierlambert any update on this item?

rtjdamen

@olivierlambert Hi Olivier, it is pretty quite on this subject for a while now, any news or updates to expect?

olivierlambert

Hi,

Immutability is still possible via your S3 provider or via the Linux script we provided. It's still in the backlog to see how to get it integrated with 3rd party providers.

rtjdamen

@olivierlambert is this something we can help develop? what language is it currenlty being written? maybe i can ask our developer to have a look an contribute.

olivierlambert

The question is: what's the exact target to get immutability on?