Upgrading Ahsay with any release is fairly straight-forward and requires near-zero downtime if you're quick (implemented it by script). When upgrading from 5.5.2.X (or earlier) to 5.5.3.X (or higher), you need to schedule some downtime to let the system implement the new indexing that ultimately greatly enhances performance. None of this is official from Ahsay, but here is how Peak Backup upgraded our servers:
1. Schedule a maintenance window with your customers. Your window depends on the size of your user home directory sizes. Make it something equivalent to the time it takes to perform a recursive directory listing.
2. Disable replication. If something goes wrong, you'll still have your data is good working order.
3. Perform an initial file copy to retain your customization and settings per the administrator upgrade guide. Peak Backup uses rsync instead of copy because of logs files involved in step 6.
4. Prevent users from backup. Either plumb down the network interface or suspend all accounts (http://peakbackup.blogspot.com/2009/08/multiple-ahsay-accounts-suspended.html)
5. Shutdown the service.
6. Perform a second copy of the system logs. Copy could take a while if you’re using copy. Hopefully you'll consider a rsync-like protocol (then it’s 5 seconds).
7. Start the service. With this specific upgrade, Ahsay software knows that performance indexing needs to be performed. It will parse over every file in the user home directories. You can watch this in the logs.
8. When indexing is complete, enable your network interface or enable all users (whatever method you chose).
9. Checkout completely, then enable replication.
10. Wait a week before auto-upgrading your clients.
NOTE: Our upgrades are literally as fast as a service restart plus 5 seconds and do not require preventing user backup access as soon as the service is back online. This specific release recommendation suggests extended downtime for indexing. This is the first time in years of using the software where we just had to show patience and let the system run.
Jim Robinson
Peak Backup LLC
http://www.peakbackup.com
Friday, October 2, 2009
Subscribe to:
Posts (Atom)