Comment Re:Few things to consider (Score 1) 600
One thing I'd add is to create a good set of documentation, and if necessary let the powers that be know that you want the time to document the systems operation either as it develops or once it's stable. However, for security purposes I tend to prefer either storing data on a server in-house (with VPN access), or being very careful about the choice of an outside hosting service provider.
Document how to perform all key operations, and leave a paper copy in a company-owned safe (in case of network or system failure). It can also help you when you need to perform a rarely - performed operation - perhaps reloading RAID or other drivers. I'd also save and backup a library of all essential sw and systems images in case they are needed for recovery.
This will help down the road not just in case you "are hit by a bus," in the worst sense of those words, but if you have an outside emergency to tend to, or just need to take a day off. This can provide more flexibility for you and your schedule. Also, if you should leave the company one day, this is the sort of thing that does (my opinion) tend to be appreciated.
Regards,
Sam