September 8, 2010
| |||
|
In This Edition:
Make Time To Develop A Disaster Recovery Plan
Human Resources...
| ||
Please forward Non Profit Times Weekly Newsletter to your colleagues so that they can also subscribe. | Make Time To Develop A Disaster Recovery Plan
By Grant Howe You've no doubt heard about the need for a Disaster Recovery Plan (DRP). You've also probably heard sad stories resulting from the lack of a DRP, including the pain of data loss and even complete organizational failure. So, what is a DRP? A disaster recovery plan is a subset of a larger process known as business continuity planning that should include preparations for the resumption of applications, data, hardware, communications (such as networking), and other IT infrastructure. According to Wikipedia, a typical business continuity plan (BCP) includes preparations for non-IT related aspects of a business, such as key personnel, facilities, crisis communication, and reputation protection, and should refer to the DRP for IT-related infrastructure recovery and continuity. You might be asking: "Who has the time for this kind of planning?" And, you might be thinking: "Even if I develop a DRP today, it could be months before it's in place and tested. What if we have a disaster in the meantime?" These are both great questions. To put your mind at ease (at least a little), let's look at four steps you can take now to reduce your risk, even without a fully developed DRP. There is a specific question anyone in the technology field asks someone who has just experienced a disaster: "Where is your latest backup and how old is it?" You always want your backup to be all three of these things: off-site, accessible, and less than one week old. Often they hear the very bad news about the data because they didn't a backup. It's gone forever. Many businesses and organizations that are unable to recover data from a disaster cannot make it through their next year. Hardware and software is easily replaced, but your organization's data is priceless and should be treated as such. During the next seven days: * Find out if your organization is performing backups. If not, start doing backups today. If so, make a list of additional data that might need backing up on a regular basis.* Get a plan in place to weekly backup everything on your list.* Store your backups off-site. When insurance agents ask organizations how many computers are in their building, most have no idea. Knowing how many physical IT assets you own is not only critical for insurance reasons, it is also necessary to help you figure out what computers and applications should be rebuilt first. During the next 30 days: * Make a list of your organization's computers and storage devices (workstations & servers). * Annotate the functions and applications that are used on each one. * Rate each resource as "critical" or "disposable." Critical resources are those that cannot be quickly rebuilt from new hardware and a backup (app servers, databases etc). Disposable resources are those that can be easily recreated from backups and install disks. * Focus your attention on plans to "recover from failure" only the critical resources as your first step The proper "care and feeding" of servers and mission-critical applications is best left to those who can afford specialized IT staff. If you would prefer to spend your IT staff's time on higher value tasks for your organization -- beyond patching the operating system or updating applications -- consider switching to hosted versions of key applications. Many independent software vendors (ISVs) offer their software in a hosted environment that you can pay for on a monthly basis, with no servers or software for you to manage. You should also consider "renting" servers from a reliable and large managed service provider. When looking at these providers, make sure they include service level agreements (SLAs) of at least 99 percent uptime for your critical services, and that they are contractually bound to those SLAs. During the next 45 days: * Review the list of critical servers and applications from the previous exercise.* Ask your software vendors about hosted versions of your software.* Determine and consider total cost of ownership (including maintaining hardware in house), as compared to application hosting and outsourcing your servers.* Pick the provider that works for you, and then implement some manageable and economical changes Chinese philosopher Lao Tzu once said, "A journey of a thousand miles begins with a single step." Along with reducing your short-term disaster recovery risks, you'd be remiss in not starting the process of building a comprehensive DRP. Long term, your organization needs to have one developed and implemented. And, if you don't start, you'll never finish. During the next 90 days: * Discuss the need for a DRP with your executive director and/or board of directors and secure buy-in. * Ask for assignment of a project manager or owner.* Draft a project plan.* Build a budget to present to your board. DRPs are important, but reducing real short-term risk is important, too. In dealing with technology, it's important to make a difference, not a mess. *** Grant Howe is the vice president of research and development for Sage North America's Nonprofit Solutions business unit, based in Austin, Texas. His email is grant.howe@sage.com | ||
| |||
Donors...Finding out what your they think of giving
That store you went into the other day -- where the people who "helped" you, for lack of a better term, treated you rudely or indifferently, talked more to each other than to you, and couldn't explain what they were offering – you're just chomping at the bit to get back there again, right?
| |||
| Marketing...Start measuring relationships with donors
Customer relationship management (CRM) is just technical jargon for keeping your constituents actively engaged with your organization as much as possible.
| |||
Update your email address! Simply click here and let us know your new address Make Sure We Move Too!
| |||


