Backup Exec: The challenge of updating RAWS with push wizard
Many users of Backup Exec are annoyed by the recommendation to apply all hotfixes made to the server also to the remote agent. I think this is quite understandable, because in daily business it is in most cases simply not easy to do it because of other, higher priority topics.
With this short piece of text I would like to change your point of view.
Please consider the following facts:
1. Many problems of backups with BE result out of a mismatch of server and RAWS.
2. Hotfixes are hotfixes, because they fix important issues.
3. If you have to call tech support, they will definitely check the version of server and RAWS and in case they do not match advise you to update.
4. This is really important: If you are waiting too long, the number of updates that have to be applied increase that much that a push update will no longer be possible.
The last point is really important. My investigations showed that somewhere between 8 (result of tech support) and 10 (my result) updates the installer simply crashes. It cannot handle more updates and therefore updating the RAWS through push wizard will fail. This has been confirmed by tech support, too.
Some recommendations for this scenario:
1. Remove all updates before service pack 2 from directory .../backup exec/agents/rawsXX/updates (simply sort by date)
2. If you have to apply more than 8 updates, and want or have to use push wizard do the following
a) Split all existing updates in .../backup exec/agents/rawsXX/updates into groups of max. 8 items (of course, take care of the order)
b) only keep one group in directory .../backup exec/agents/rawsXX/updates and move the other groups to a temporary location
c) start the push wizard
Do this with every group of updates. The wizard only uses the updates located in the directory .../backup exec/agents/rawsXX/updates. With this workaround you can manage to update the RAWS centralized from your BE server.
Hope you think a bit different about updating the RAWS and perhaps know the reason now, why updating with the push wizard failed with no clear reason the last time. ;)