|
Hi, regarding XX-5479 (ex XCF-3003) - http://track.sipfoundry.org/browse/XX-5479 ensure that 4.0 backups can be used for restore on post 4.0 version. Based on the discussions on this subject (see http://list.sipfoundry.org/archive/sipx-dev/msg14837.html and the mirc logs attached bellow) we have done some analysis regarding what is now backed up. Here are our findings: 1. @SIPX_CONFDIR@/domain-config - this file is generated at first run. We can remove this file from backup list and trigger the generation at restore 2. @SIPX_CONFDIR@/security.policy - I found that this file is obsolete (I cannot find it in sipX). It should be removed from backup list 3. All the cert files/folders should be kept 4. @SIPX_DBDIR@/*.xml there are 6 files here which are replicated from DB during various application operations. We can remove them from backup list and force a replication at restore for each one at a time 5. @SIPX_CONFDIR@/*.in 2 files here: httpd-sipxchange-common.conf.in and sipxdialog-config.in . I don't know about these 2. Some clarification needed. 6. @SIPX_CONFDIR@/sipxacd.xml Some clarification needed for this also. 7. @SIPX_VARDIR@/configserver/phone/acd/audio/*, @SIPX_VARDIR@/parkserver/music/*, @SIPX_VXMLDATADIR@/prompts/* - sound files. They should be kept in backup list 8. @SIPX_VARDIR@/phonebook/* - csv files uploaded. They are not under DB control, The solution is to either keep it in backup list or migrate them to DB. This would mean changing the engine to ensure the generation of the files. 9. @SIPX_PAGEMUSICDIR@/* - there is an error here. I find in sipx-backup from {installation folder}/bin this line is not translated into a path. Any thoughts? Regards, Cristi PS: Bellow are the mirc logs relevant to our discussion: (04:43:58 PM) ciuc: XCF-3003 - ensure that 4.0 backups can be used for restore on post 4.0 version (04:43:58 PM) ciuc: Removed all the configuration files from backup script except for certdb folder. (04:43:58 PM) ciuc: **Question: INSTALL/etc/sipxpbx/ssl/ssl.crt and INSTALL/etc/sipxpbx/ssl/ssl.key must remain? (04:43:58 PM) ciuc: Need to improve the restore script to take into consideration that for versions greater than 4.0 it should not take into account version numbers. (04:44:19 PM) pirxpilot: I think certs should remain, but (04:44:29 PM) pirxpilot: there might be in a different directory (04:44:40 PM) ciuc: yes, they are (04:44:48 PM) pirxpilot: did you find a thread on the list for this issue? (04:44:51 PM) ciuc: yes (04:44:57 PM) pirxpilot: ok (04:45:09 PM) ciuc: http://list.sipfoundry.org/archive/sipx-dev/msg14837.html (04:45:16 PM) pirxpilot: the bottom line is: everything that sipXconfig generates needs to be removed (04:45:37 PM) pirxpilot: everything that sipxecs-setup generates needs to stay.... (04:46:04 PM) ciuc: aha (04:46:12 PM) ciuc: i see (04:46:43 PM) pirxpilot: the dificulty is the sipxecs-setup generates some file that are later generated by sipXconfig.... (04:47:35 PM) pirxpilot: I kind of thing they need to be saved just in case, since they are used to establish initial communication with sipx-supervisor (04:47:55 PM) pirxpilot: so if we do not restore them, and the system is completely bare we will never be able to configure it (04:48:10 PM) ciuc: are they backed up now? (04:48:31 PM) pirxpilot: I suppose that nearly entire /etc/sipxpbx directory is in the backup (04:48:56 PM) xmlscott: that's correct, it is (04:49:25 PM) pirxpilot: paul is probably the last person who had a serious look at this code (04:49:35 PM) pirxpilot: he can probably help if you have any questions (05:22:00 PM) ciuc: Hi Paul (05:22:02 PM) ciuc: got a second? (05:22:27 PM) mossmanp: sure, what's up? (05:22:54 PM) ciuc: we have an issue: XCF-3003 (05:23:01 PM) ciuc: about backup and restore (05:23:30 PM) mossmanp: looking now (05:23:31 PM) ciuc: basically we have to make sure that only some files are backed up (05:24:22 PM) ciuc: Damian said that : (05:24:26 PM) ciuc: 04:46:43 PM) pirxpilot: the dificulty is the sipxecs-setup generates some file that are later generated by sipXconfig.... (05:24:26 PM) ciuc: (04:47:35 PM) pirxpilot: I kind of thing they need to be saved just in case, since they are used to establish initial communication with sipx-supervisor (05:24:26 PM) ciuc: (04:47:55 PM) pirxpilot: so if we do not restore them, and the system is completely bare we will never be able to configure it (05:24:59 PM) ciuc: for now we aggreed that we have to backup only the certs (in certdb folder) (05:25:00 PM) mossmanp: these are the certificates, I think (05:25:15 PM) ciuc: yes (05:25:25 PM) ciuc: any other file that you are aware of? (05:25:47 PM) mossmanp: none I can think of offhand... (05:26:09 PM) mossmanp: but the best plance to look would be the script that creates the backup (05:26:23 PM) mossmanp: also, look at an actual backup file (05:26:29 PM) mossmanp: see what it contains (05:26:47 PM) ciuc: right now files that are backed up are: (05:26:49 PM) ciuc: http://sipxconfig.pastebin.com/d7fa7e26f (05:27:05 PM) ciuc: I removed everything except for the certs (05:29:40 PM) mossmanp: gotta scrum (05:29:43 PM) mossmanp: ping me in 15? (05:30:14 PM) ciuc: roger (05:36:53 PM) mossmanp: domain-config, I think has been removed, or just about (05:37:14 PM) mossmanp: not sure why /var/sipxdata/sipdb/*.xml was ever included (05:37:34 PM) mossmanp: those files should be generated by sipXconfig from DB contents (05:37:55 PM) mossmanp: Ahh (05:38:05 PM) mossmanp: ACD, VM, Park Server audio files.... (05:39:28 PM) mossmanp: this is "data" and it would be good to keep it (05:39:42 PM) mossmanp: well, we need to keep it in the backup (05:39:46 PM) ciuc: there is a mail thread :http://list.sipfoundry.org/archive/sipx-dev/msg14837.html (05:40:26 PM) ciuc: for what I understand, only the db should be kept and those files that Damian is talking about (05:40:37 PM) ciuc: I'm a little bit confused, to be honest (05:41:09 PM) mossmanp: me too, I haven't been in the loop on this one (05:41:37 PM) mossmanp: It looks like a bigger issue than folks are probably expecting though (05:41:46 PM) mossmanp: but I'm not a sipXconfig expert (05:42:24 PM) mossmanp: Can I suggest you post to the list? (05:43:17 PM) ciuc: Yup.. (05:43:31 PM) ciuc: It's a bit late since it's the last day of the sprint.. (05:43:32 PM) mossmanp: OK, I see now that Damian says all non-DB data needs to be either produced by sipXconfig or is upgradable independently.... (05:43:45 PM) ciuc: yes (05:44:06 PM) mossmanp: upgradable independantly, I think means that it is OK as is (05:44:11 PM) ciuc: I will probably post a patch with this modification (05:44:33 PM) mossmanp: "produced by sipXconfing"... I think means it can be removed from the backup file (05:44:58 PM) mossmanp: if it is produced by sipXconfig based on DB contents, then no need to keep it in a backup (05:45:07 PM) mossmanp: confirm that part on the list though (05:45:25 PM) mossmanp: but yes, it might be too late for 4.0 (05:45:31 PM) mossmanp: anyway, good luck (05:45:31 PM) ciuc: it kinda is (05:45:38 PM) ciuc: Thanks a lot (05:45:43 PM) mossmanp: you're welcome |
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
