On Tue, Mar 2, 2010 at 7:03 PM, Picher, Michael <mpic...@cmctechgroup.com>wrote:

> Build a new box from ISO making sure to use the same IP / host name /
> sip domain / etc.  I have best results if I have the network adapter
> linked up but you won't want it on the same network as your existing
> PBX.
>
> Backup the existing box and copy the backup files to a PC.
>
> Shut down the server beast from h___ and take it off line.
>
> Fire up the new box on the lan and do a restore.
>
> After restore, upload/activate your phone firmware files and then send
> all the phone profiles (it does get done automatically after the
> restore, but I still do it anyway with the firmware files on-line and
> active).
>
> If things don't go quite right you haven't destroyed your production box
> yet so no worries.
>
> Once in a while I have had to re-gen my certificates.
>
> Mike
>
> -----Original Message-----
> From: sipx-users-boun...@list.sipfoundry.org
> [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Andreas
> (Around the Clock Information Systems)
> Sent: Tuesday, March 02, 2010 6:45 PM
> To: sipx-users@list.sipfoundry.org
> Subject: [sipx-users] sipXecs Server Hardware Migration
>
> Dear sipXecs Users, Experts and Developers,
>
>        I know at some point that this topic has been covered in the
> past,
> so I apologize in advance for being redundant.  Feel free to reply with
> links to previous answers from the sipx-users mailing list archives.  I
> just
> wasn't sure how to formulate my search query to find the answers that I
> seek. . .
>
>        The situation is this:  We (our company) have a sipXecs server
> (now
> at version 4.0.4-017289) that has been in production for about nine
> months
> and has been working flawlessly (Developers, thanks for building such
> fantastic product!) since we upgraded to the current stable version.
> These
> days, I rarely need to touch it because it "Just Works".  Unfortunately,
> when I put this server platform together last year, I significantly
> over-built.  Even during peak usage times the 'Server CPU Load' and 'CPU
> busy percentage' rarely exceeds 3%.  The Percentage of Disk Usage after
> nine
> months in production is only at 11%.  From my impression, it seems that
> sipXecs appears to be extremely efficient (much more so than I
> originally
> anticipated).  So, the point that I am trying to make is that running
> sipXecs on this hardware platform is a waste of resources and
> electricity.
> I would like to move our current running configuration to more of a
> Workstation Class machine so that the hardware platform that it is
> currently
> running on could be repurposed to a role that is a bit more demanding.
> Ultimately, what I would like to happen would be to turn the original
> server
> beast from h___ off, turn the new Workstation Class Server on and have
> everything work as it does right now, to include customized inbound
> voice
> prompts, user voice mails, etc., etc. . . the whole shootin' match.  Is
> there a simple approach to make this happen?  It literally took me 40 to
> 50
> hours to get this box configured and customized to meet the needs of our
> company; I dread the thought of having to go through all that again.
> Your
> recommendations, PLEASE. . .
>
> Thanks in advance!
>
> Andreas
> Systems Engineer
> Around the Clock Information Systems
>
>
>
>
>
> _______________________________________________
> sipx-users mailing list sipx-users@list.sipfoundry.org
> 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 sipx-users@list.sipfoundry.org
> 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/
>

NTP configurations don't restore, so if you have anything "special" to the
config, make that change also.

IF the system is a DNS master, manually backup your /etc/named.conf and any
zone file(s). You might also consider the same for dhcpd and your leases
file if it is a dhcp server too.

I've noticed I have to go grab AA greeting files from time to time and
sometimes you actually have to pick a different greeting file/apply, then go
back choosing the original and apply again to get the system to pick it up.

One the other hand, leave the beast from h____ alone. If he's happy, don't
screw with him. Ha!

Tony
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
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/

Reply via email to