If you have uploaded wav files with a space in the file name for any of your AAs or ACD queues, they will be left out of the backup too. Sent via BlackBerry from T-Mobile
-----Original Message----- From: "Scott Lawrence" <[email protected]> Date: Sat, 06 Feb 2010 07:19:22 To: Eric Varsanyi<[email protected]> Cc: [email protected] users<[email protected]> Subject: Re: [sipx-users] Device files missing on a restore On Sat, 2010-02-06 at 02:10 -0600, Eric Varsanyi wrote: > On SVN 17748, RPM install, running on FC12: I made a filesystem clone > (same IP) of a working machine to a virtual test machine and upgraded > it to SVN 17896. After adding some device files (polycom firmware, > some unmanaged ringtones and .cfg files) through the UI on the > original box I did a sipxecs backup on it then restored to the test > machine using the UI restore function (right after a --database drop > and sipxecs-setup). When it said it was done I rebooted. > > The UI test machine came up without the device files unpacked into > tftpboot but showing them as active in the UI. When I deactivated them > there was no problem. When I tried to reactivate them the config > server threw pages of stack trace (which I can dredge up if needed) > into its log, the initial exception was a file not found exception > trying to find the archive files to unpack in the sipxdata/upload > directory. > > I tarred up a copy of the /var/sipxdata/upload directory from the > original machine and unpacked it on the test machine, then tried again > to activate the files and everything worked fine. > > I do not expect this is due to version skew between 17748 and 17896 > because the device files just aren't anywhere in the backup tars. > > What I expected: that a sipxecs backup has all state I put into the > system via the config UI and I don't otherwise need to make regular > unix level backups of the server. > > I looked through JIRA and the book and couldn't find anything that > covers this, should I file a bug? Yes, please do. Good catch. No need to attach a snapshot or anything - your procedure sounds easily reproducible. _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
