[05:21:19] --- SecureEndpoints has left: Replaced by new connection [05:25:49] --- dev-zero@jabber.org has become available [05:49:10] --- dev-zero@jabber.org has left [06:08:09] --- kula has left [06:19:13] --- kula has become available [07:40:53] --- dev-zero@jabber.org has become available [07:40:59] --- dev-zero@jabber.org has left: offline [07:52:49] --- SecureEndpoints has become available [10:51:42] --- dragos.tatulea has become available [10:59:07] --- dlc has become available [11:36:14] --- dev-zero@jabber.org has become available [11:36:14] --- dev-zero@jabber.org has left: offline [12:46:10] --- dragos.tatulea has left [13:24:01] --- Russ has become available [13:27:18] --- SecureEndpoints has left: Disconnected [13:27:57] --- SecureEndpoints has become available [16:04:56] --- manfred has become available [16:08:51] I have some small question, on vos release, can you help me ? [16:16:48] possibly [16:17:06] simon: you can .. [16:17:18] the vos release is incremental ? [16:17:31] simon: welcome back .. [16:18:22] vos release is incremental by default unless you pass -f. [16:18:39] and also if you have more ro volume is a parallel process or serialized [16:18:42] Or unless there's nothing to be incremental to (a new release to a newly created site). [16:19:00] In some situations, it's parallel. I don't know off-hand how it decides whether it can be parallel. [16:19:14] vos release -v will tell you if it's doing it in parallel, I believe. [16:19:58] I thought that it released to the local RO first, and then did the remote ROs in parallel [16:20:00] the diff is made by a change log on the server or on a diff on the content on the two or more volumes ? [16:20:31] Oh, yeah, good point, the local RO is always separate. [16:20:49] If the remote ROs aren't all the same, it won't do them in parallel. [16:20:57] If they're all the same, I think it can always do them in parallel, but I'm not sure. [16:21:06] I seem to recall seeing it not do it in parallel when I thought it should be able to. [16:21:08] that means you have some like a snapshot when you run the command ? [16:21:13] Yes. [16:21:26] It creates a local clone and then pushes that clone to the remote servers. [16:21:46] And I think the incremental is done via the same mechanism as incremental vos dumps, but now you're at the edge of my understanding. [16:22:22] The reason for having a local clone is that the RW volume has to be locked whilst that clone is being made. If you did all of the remote pushes without the local clone, you'd lock the RW volume for much longer. [16:23:01] It makes a local clone even if you don't have a local RO, but I believe it uses the local RO as the local clone if there is one. [16:23:21] the ro way it is good way .. [16:24:25] can you decide compression level (if it is possible )? [16:24:45] I don't believe replication is compressed. [16:24:46] on the data trasmission for replication [16:24:52] I don't think anything that vos does is compressed right now. [16:24:55] I could have missed something, though. [16:25:29] do you think the ro volume could be a solution for disaster recovery site ? [16:25:35] Yes. [16:25:52] It has some limitations, but if your DR requirements fit those limitations, it's not a bad one. [16:25:59] Yes. We use it for that. [16:26:01] The main limitation is that you only get one copy. [16:26:16] Yes, unless you're Michigan. But that's hairy. [16:26:46] i can solve the problem of the afs db ? if a lose a site probably a lose the "majority" in the election [16:27:22] why one copy ? [16:27:47] Well, you can have more than one copy. But only one generation. [16:28:17] Each time you release, the new data gets copied everywhere. So you can't do yesterday, last week, last month, etc. [16:28:35] ok [16:29:12] --- dev-zero@jabber.org has become available [16:29:16] --- dev-zero@jabber.org has left: offline [16:29:26] --- manfred has left [16:29:35] Anyway, must sleep. [16:29:38] --- Simon Wilkinson has left [16:31:40] --- manfred has become available [16:32:38] the backup for me is a separate problem [16:33:04] thx for now [16:33:57] --- manfred has left [18:14:37] --- kula has left [19:46:03] --- kula has become available