Joined: 06 Jun 2007
There are many interrelated aspects to an Axia system and backing up a system can be a bit complicated however it is all very logical once you understand the blocks.
Ethernet Switches – It is essential that you know how to program your switches and that you have the necessary documents plus your existing configurations to use as a reference. Our web site has several Cisco application notes posted here http://www.axiaaudio.com/manuals/default.htm .
Nodes – If you have Axia iProbe software, backing up all of your node configurations is a simple one-click process. If you do not have iProbe, it is highly recommended that you use a spreadsheet to document all of your node sources and destinations as well as the node name, clock priority settings and software version. Remember that some node destinations may be controlled by software so be sure to note this in your documents. Since Pathfinder can be used to directly make route changes plus control VMIX functions, it is important to document your system design in this respect. This will also make any changes and troubleshooting much less complicated.
Element and Mix Engine – Again, there is nothing like some good documentation however both the Engine and the Element include a backup function so be sure to make backups of these files whenever you make changes. Keep a record of VMIX functions and Element profile changes that are controlled by Pathfinder. Again, iProbe can be used to centralize your backups and make restoration a simple process.
Compact Flash (CF) cards - Both the Element and the Studio Engine have their Linux Operating System plus Axia application software stored on CF cards (compact flash). These Axia devices boot from these flash disks so it is a good idea to have a couple of spare CF cards with current Element and Engine images stored on these cards. An application note on “How to create new compact flash cards” plus our windows CF image utility (awrite.exe) can be found here. http://www.axiaaudio.com/manuals/default.htm Axia recommends the SimpleTech CF cards since they are a high-quality card that has been fully tested. Other brands have been also used successfully in the field. As of Q3, 2008, the Element needs a 256MB card and the Engine requires 512MB. Larger cards have also been used successfully. Be sure to use the correct image when creating an image on your CF card. Over time, different motherboards will be used for the Element and Mix Engine and each different type of motherboard will require its own image. Contact our tech support group if you have questions - firstname.lastname@example.org
Pathfinder – Most Axia systems include Pathfinder installations and this software can play a very important role in the functionality of your system. It is true that an Axia system can deliver audio without Pathfinder however there is a lot of power provide by Pathfinder and all complex systems will make extensive use of this software. Be sure to have an off-line copy of the entire PathfinderServer folder which is, by default, located at C:\Program Files\PathFinderServer. All mini panels, stack events, logs, etc. are included in subfolders at this location.
When creating Stack Events, make full use of the fields available for describing your events, qualifiers and actions. Simply using these fields effectively goes a long way to documenting what you have done. If you can't tell exactly what the qualifiers and actions are doing by simply looking at the descriptions, expand on those descriptions! There is lots of space available for very complete info to be displayed there.
- Be sure to record the IP addresses and Axia Livewire source/destination channel numbers used by all other devices including the IP drivers and Livewire-enabled devices(Omnia.8x, Omnia ONE, Telos Xstream, InternationalDataCasting, Radio Systems, 25/7 Systems)
- If you are using the iProfiler, document your archive sources and storage locations plus any settings unique to GPIO.
- Be sure to backup the Windows installation on your Pathfinder Server. Archiving a disk image is a good way to do this.
Some of our users have experimented with web-scraping tools such as HTTrack (www.httrack.com) These can be quite effective but there is some risk. Be careful capturing web pages of devices such as our Element that include a “delete” function. Tools such as HTTrack will attempt to open every page and will delete your profiles unless you have specified exceptions.
To simplify Cisco configuration, you can backup and restore your switch configurations by using free TFTP server software such as Solar Winds TFTP found here http://www.solarwinds.com/downloads/index.aspx?CMP=ILC-GNav-Downloads . This is a very convenient and quick way to manipulate Cisco configuration files.
Forgot what address you have assigned to a device? AngryIP Scanner will probe a network and let you know what addresses are in use. Find it here http://www.angryziber.com/w/Home