After 40 years, I think I probably have an opinion now. I would say there are three things.

The first thing is, don't be locked in into traditional thinking. That's number one. Don't get put into that box where you're thinking about the old backup robots or local disk drives with Symantec, or whatever your products are. Don't be stuck with the concept of, "Well, we have to co-locate our data outside of our facility in order to keep it ours and protect it." So, number one, don't get locked into traditional solutions.

Number two, don't be afraid to negotiate for guarantees of performance, with penalties if the company doesn't perform. You can walk away from any solution. You don't have to marry it. But this is the time that you build in your guarantees if you have doubts and concerns. You do it up front.

The third thing - probably the most important thing - is, make sure that your infrastructure team is involved in the process from the start. Don't cherry pick one or two people and have them review products and then go based on their recommendation. Engage as many of the people who are actually going to live with the product or the solution as possible, from the start, for evaluating and considering what you're doing, because they're the ones who have to live with the outcome.

I have absolutely no complaints about it, and it performed exactly as advertised, and has continued to do so in an extremely reliable manner. My comment to you or to anybody reading this is: We don't think about our backups anymore. They're that reliable. We aren't worried about them. We are checking them first thing in the morning when we come in. We get reports and we get indicators and we do check it occasionally, but it's not the first thing on the agenda when the first person comes in the morning, "Did the backups go off last night?"