About Bundle-Track
  Home Solutions About Us About Us
Free Support: Online Knowledge Base
  Accessing Support
Self Help
  • Online Knowledge Base
  • User Documents
    •  

    Free Support
  • support@bundle-track.com
  • Fax 617-556-4005
    •  

    Contract and Billable
  • phone 617-556-4003 x261
    		•

    System Maintenance: Upgrading Bundle-Track from series 3.4 and 3.5;
    the parallel installation approach

    Overview

    We have designed a process that will enable you to transition from your old Bundle-Track system to the new one with minimal system downtime. We call it the parallel installation approach. It requires that you have, in addition to the computer currently running Bundle-Track, another computer on which you can install the new Bundle-Track system, at least temporarily. (If you don't, then you need to take the serial installation approach.)

    Metaphorically, the process is a bit like jumping from a tired horse to a fresh one. The tired horse is the old Bundle-Track system, and the fresh one is the new Bundle-Track system. You'll get ready by getting your new Bundle-Track system running along side of the old one, on an alternate server computer. Then, when you're ready, you'll jump off the old system and onto the new one.

    You'll need to plan for about 8 hours of system downtime during that transitional period where you're in the air, having left the old system and not yet landed on the new one. During that time, we'll be performing the final conversion of your database. To continue the metaphor, if you'll think of your database as your saddle, we need to retool your saddle to fit your new horse, and we need you to be off of it while we do that. Meanwhile, you can get the new system ready by replacing all the old Bundle-Track Clients with new Bundle-Track Clients. Once your converted database is loaded into your new Bundle-Track system, you can get back in the saddle again.

    Finally, if you want to move Bundle-Track back to the original server, you would uninstall the old Bundle-Track system from the original server machine, install the new Bundle-Track server on the original server machine, and then stop using Bundle-Track long enough to move the database from the alternate server to the original server and redirect each client's database connection to the original server.

    To sum up, here are the basic steps of the process:

    1. Preparation Part 1, Anytime: (40 minutes) (no interruption of service)
      • Send us your Reports folder and database.
    2. Preparation Part 2, Anytime: (1.5+ hours) (no interruption of service)
      • Install the new Bundle-Track System on alternate servers and work out any kinks in ticket printing.
    3. Downtime Part 1, After Period Close: (2.5+ hours)
      • Shut down Bundle-Track, send us your database, and get your new Clients ready while you wait for us to complete the database conversion overnight.
    4. Downtime Part 2, Next Morning: (1.25 hours to uptime)
      • Put the new database in place and start up the new system.
    5. Optional Relocation of Server, Anytime: (1+ hours) (some downtime)
      • Replace the old Bundle-Track Server on the original server with a new one, relocate the database, and update the clients.

    We can be hired to perform any part of this process.

    Detailed Procedure

    1. Preparation Part 1, Anytime: (40 minutes) (no interruption of service)
       
      • Send us a copy of your Reports folder. (10 minutes)
        1. Make a .zip file of your entire Reports directory.
        2. Email that file to support@bundle-track.com.
           
      • Send us a Zip file of a recent database backup (.gbk) file. (30 minutes)
        1. Locate a recent .gbk (database backup) file created shortly before a period close.
        2. Make a .zip of that .gbk file.
        3. Rename the .zip file to start with your company's initials.
        4. Deliver the .zip file to us by FTP. [FTP procedure]
        5. Let us know at that you've posted it.  
           
      • (We will use these source files to update your reports and to tune our conversion process for your database.)

    2. Preparation Part 2, Anytime: (no interruption of service)
       
      1. If you don't currently have a Setup Package for your system, contact Bundle-Track Support for this file.
        • See contact info at top right on this page.
           
      2. Download a new Bundle-Track Executable
        • Contact Bundle-Track Support for this file.
           
      3. Install Bundle-Track on the alternate server machine:
        • Desktop Edition: Just run the Setup Package and accept all defaults.
        • Network Edition:
          • If installing Server and Client on one machine, use this procedure.
          • If installing Server and Client on separate machines, then ...
            1. install the Server by this procedure and then
            2. install the Client by this procedure.
               
      4. Test ticket printing and work out any kinks.
        • Using one of the demonstration Cut records provided in the new installation, try printing some tickets. If necessary, troubleshoot. [online help]
           
      5. Register the Server in IB Console:
        1. Start IB Console: >> Programs >> InterBase 6 (the name may be longer) >> IBConsole.
        2. Register a Server:
          1. Use the menu to select Server >> Register.
          2. Set the radio button to choose Local Server or Remote Server.
            • If you are working on the computer that holds the Bundle-Track database, choose Local Server.
            • Otherwise, choose Remote Server, then specify the Server Name (as the network sees it).
          3. Specify your Network Protocol.
            • If you aren't sure which to choose, try TCP/IP.
          4. At the bottom of the panel, input the Administrator Login:
            • Username: sysdba
            • Password: masterkey
          5. Click OK.
          6. Close IB Console.

    3. Downtime Part 1, After Period Close:
       
      1. Stop using your old Bundle-Track system.
         
      2. Send us your database.
        1. Prepare a backup (.gbk) of your database.
        2. Make a .zip file of your backup (.gbk) file.
        3. Deliver the .zip file to us by FTP. [FTP procedure]
           
      3. Replace all old Bundle-Track clients with new ones.
        1. Uninstall each old Bundle-Track Client. [procedure]
        2. Install the new Bundle-Track Client on each client machine. [procedure]
           
      4. (Wait for us to complete the database conversion overnight.)

    4. Downtime Part 2, Next Morning:
       
      1. In the morning, install the converted database.
        1. Download the converted database.
        2. Unzip the .zip file.
        3. Restore from the .gbk file. [procedure]
           
      2. Start the new Bundle-Track system.

    5. Optional Relocation of Bundle-Track Server, Anytime: (some downtime)
       
      1. Replace the old Bundle-Track server with a new one.
        1. Uninstall the old Bundle-Track Server from the original server. [procedure]
        2. Install the new Bundle-Track Server on the original server. [procedure]
           
      2. Take Bundle-Track offline and move the database. [procedure]
         
      3. Start the Bundle-Track system on the original server.
         
      4. Remove Temporary Installations, Anytime:
        1. Uninstall the new Bundle-Track Server from the alternate server machine. [procedure]
        2. Uninstall any temporary Bundle-Track Clients. [procedure]

    We welcome your comments at support@bundle-track.com.

    If you would like our live assistance, you may hire us at our professional services rate.
     

    top