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

• Overview
• Detailed Procedure

Overview

If you do not have the hardware to support the parallel installation approach, you must 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. Also, to continue the metaphor, database is 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. Once we've readied your saddle for the new horse, you'll move the old horse out of the way, put the new horse into position, drop the saddle in place, and be on your way.

You'll need to plan for about 8 hours of system downtime while we perform the final conversion of your database. During that time, you won't be able to use your Bundle-Track system. Usually, we do this overnight, when the downtime is least inconvenient for you. In the meantime, we want you to leave your old Bundle-Track system in place and intact so that in the unlikely event that some problem with your source file or our conversion process prevents us from delivering your converted database on schedule, you can simply start up your old system again. Typically, we will deliver your converted database on schedule, and once you've received it, you can uninstall the old Bundle-Track system and install the new one in its place with the new database.

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

1. Preparation, Anytime: (40 minutes) (no interruption of service)
   • Send us your Reports folder and database.
2. 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.
3. Downtime Part 2, Next Morning: (1.25 hours to uptime)
   • Replace the old Bundle-Track Server with the new one, put the new database in place, and start up the new system
4. Client Configuration: (30 mins. to 2 hours + 35 mins. per Client)
   • Replace any old Bundle-Track Clients with new ones and work out any kinks in Ticket Printing.

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

Detailed Procedure

1. Preparation, Anytime: (70 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. (Here's how.)
     5. Let us know at that you've posted it.  
         

---



2. Downtime Part 1, After Period Close: (1.75 hours + 35 minutes per client)
    
   1. Stop using your old Bundle-Track system.
       
   2. Send us your database. (Time varies with file size and connection speed)
      1. Prepare a backup (.GBK) of your database.
         
      2. Make a .zip file of the new .GBK file.
      3. Deliver the .zip file to us by FTP. (Here's how.)
          
   3. 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.
         
   4. Download a new Bundle-Track Executable.
      • Contact Bundle-Track Support for this file.
      
      
   5. (Wait for us to complete the database conversion overnight.)

---



3. Downtime Part 2, Next Morning:
    
   1. Download the converted database. (Time varies with file size and connection speed)
      If we have provided you with a support page, look for that file there.
       
   2. Replace the old Bundle-Track server with a new one. (35 minutes)
      1. Uninstall the old Bundle-Track Server. (5 minutes)
      2. Install the new Bundle-Track:
         • 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.
                   
   3. Install the converted database. (Time varies)
      1. Unzip the Zip file into your Bundle-Track Database Directory. (5 minutes)
      2. Restore the .GBK file, using this procedure. (Time varies)
          
   4. Start the new Bundle-Track system. (2 minutes)
       

---



4. Client Configuration: (30 mins. to 2 hours + 35 mins. per Client)
    
   1. Replace all old Bundle-Track clients with new ones. (35 minutes each)
      1. Uninstall each old Bundle-Track Client (5 minutes each)
      2. Install the new Bundle-Track Client on each client machine, using this procedure. (30 minutes each)
          
   2. Test ticket printing and work out any kinks. (30 minutes to 2 hours)
      • Using one of the demonstration Cut records provided in the new installation, try printing some tickets. If necessary, troubleshoot.

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.