Cristi Starasciuc wrote:
> 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

It's true that sipXconfig generates this file, but before this file is
generated by sipXconfig it is also generated by sipxecs-setup script.
I am worried that if it's not restored the system just won't start at all
and sipXconfig will not have a chance to generate anything...

Scott - what do you think?

Also please make sure that sipx-restore calls sipxconfig.sh --first-run to
force regenerating of all the configuration files.


> 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

Do not backup.


> 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

Do not backup: sipXconfig will configure ACD and ACD will generate this file.

> 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

Yes.

> 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.

Need to be backed up since DB keeps references to them.
We will migrate them to DB in 4.2


> 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
> 

[...]

_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev

Reply via email to