Remote office and branch office storage solutions architecture

There are three strategies VARs and systems integrators should take into account when setting up remote office, branch office storage. By planning the remote storage model ahead of time, VARs can eliminate data mix-ups for customers.

Decentralized model

The most decentralized model uses storage directly attached to individual servers (DAS). The decentralized model is probably the most common for branch offices since it is the simplest and cheapest to implement and puts the fewest demands on support personnel. It is also the hardest to manage, the most inefficient in using available storage space and requires provisions for backup, such as backup over the LAN. VARs and systems integrators need to take into account when setting up remote office, branch office (ROBO) storage.

Centralized model

    Requires Free Membership to View

More on ROBO storage solutions:
Remote backup trends and technologies

Remote office backups bring new life to the SSP

A centralized model with the storage at the local site, such as a SAN, offers high scalability and faster data access while still giving good manageability. However, it is often the most expensive of the approaches because of the need to establish a separate, fairly sophisticated storage facility in the branch office. It can also pose support problems because of a lack of technically knowledgeable personnel on site. Often, companies choose this model when the branch office is likely to expand significantly in the near future.

Hybrid model

The hybrid model is in some ways the most difficult to design because, to get the maximum benefit, it needs to be carefully matched to the present and future needs of the local office. For example, in a hybrid storage architecture, deciding what kinds of data will be kept locally and what will be kept centrally is very important. Properly done, the hybrid model provides a good mix of scalability, data access and ease of support.

One complicating factor in designing storage for a branch model is the potential support cost of getting it wrong. By their nature, branch offices don't have the kind of resources for troubleshooting and support that a data center does, which means additional support, especially on-site support, can be disproportionately expensive.

This article orginally appeared on SearchWinComputing.com.

Rick Cook has been writing about mass storage since the days when the term meant an 80 K floppy disk. The computers he learned on used ferrite cores and magnetic drums. For the last 20 years he has been a freelance writer specializing in storage and other computer issues.

This was first published in April 2007

There are Comments. Add yours.

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.