Konsep Backup Offsite yang berbeda : “ExaGrid vs Tape Library”

ExaGrid vs Tape Library

For many years, backing up to a tape library has been the dominant method for performing backups to protect your organization’s data. Many IT organizations, however, have grown dissatisfied with tape-based backups and are looking for alternatives that offer fast backups and restores, scalability with no forklift upgrades, fast disk-based offsite disaster recovery, and a low IT maintenance burden . Disk backup with data deduplication is one such alternative, and it’s now available at a price comparable to a new tape library.

Why the move from a tape library? The problems with tape are well known: slow backups and restores, backups fail, restores fail, labels fall off, tape is mislabeled, and tape can be lost, stolen, or damaged. Tape backups must be monitored. Equipment needs to be maintained and heads cleaned for backups to be run properly. And tapes must be loaded and changed, labeled correctly, and physically transported off-site (and then back on-site) for disaster recovery.

According to Gartner and Storage magazine, 34% of companies backup their data to tape and do not test their backups. And an amazing 77% of those companies who do test their tape backups found backup failures (Boston Computing Network Data Loss statistics). Furthermore, a 2009 Symantec Disaster Recovery survey found that 65% of companies do not have adequate backup protection for virtual server environments. Many of these virtualized environments still rely on tape.

Disk, on the other hand, is fast and reliable for both backup and restores. The table below compares tape vs disk for selected attributes:

Tape Disk
Backups are slow

Tape libraries have a physical number of drives and therefore have a fixed number of concurrent streams. Also, tape libraries roll forward and backward (“shoe shining effect”) wasting performance time.

Disk is fast

Disk is faster than tape as it is random access versus sequential access. In addition, with disk, you can set up dozens of NAS shares for concurrent streams.

Backups are unreliable

Tape libraries are mechanical devices subject to failure over time. In addition, tapes get worn, dirty and damaged by heat and humidity.

Disk is reliable

Disk does not wear, get dirty or get damaged by heat and humidity as disk is in a hermetically sealed case and lives in a heat and humidity controlled data center.

Restores are slow

Restores are slow from tape because the tape has to be streamed to the point where data is stored—and the tape with the data may not be in the drive, not in the tape library, or could even be offsite. Even worse is the situation where the backup failed, and you won’t know it failed until you go to restore.

Restores are fast

Disk is fast since it is random read versus sequential read, and with disk the data that is online is also on the disk. The chance of the data being on disk is 99.9999% because it is disk in a hermetically sealed case in a climate-controlled data center.

Tapes are lost or stolen

Tapes move around onsite and are transported to an offsite location. Tapes are easily stolen or lost, thereby creating security issues.

Disk is Secure

Disk sits in the data center rack secured by network and physical security. For an offsite disk backup system, the second system is also in a secured data center. All data is replicated in an encrypted form by the VPN.

Tape Labeling is Error-Prone

Tapes are mislabeled or labels fall off.

Disk Labeling is Automatic

No manual labor is required. Thus, no issues arise with human error or labels falling off.

ExaGrid’s disk backup with deduplication not only overcomes the challenge of tape, but it offers the following benefits:

  • Fast backups: typically 40-90% faster than tape, utilizing post-process deduplication which lands the data to disk and then deduplicates after the data is already protected
  • Fast restores: by keeping a full copy of the data on disk in non-deduplicated form
  • Scalability: GRID architecture allows seamless scalability from 3.5TB to 320TB raw capacity, allowing full backups from 1TB to 130TB with no forklift upgrades or degradation in backup performance as data grows
  • Offsite DR: an optional second-site configuration allows for WAN-efficient replication of data to an offsite disaster recovery location
  • Low IT management burden: Customers using a plug-and-play disk backup with deduplication system typically spend only a small amount of time each week managing backups. Many report saving 10-20 hours/week or more vs tape, thus freeing time for more important IT priorities

In summary, ExaGrid’s disk backup with data deduplication eliminates the problems and management burden of tape with a solution that offers the fastest backups and restores, the only scalable architecture, and the only solution priced comparable to the cost of a new tape library.

Project Management Documentation – Project Management Body of Knowledge (PMBOK)

Berikut ini adalah tahapan-tahapan yang dilakukan saat memulai sebuah project baru. Baik itu project Information Technology atau project lainnya. Based on PMBOK (Project Management Body of Knowledge).

Initiation

  • Business Case: To justify the financial investment in your project, you need to write a Business Case. It lists the costs and benefits, so everyone knows what the return on investment will be.
  • Feasibility Study: Before you kick-off your project, you need to determine whether your project is feasible, using a Feasibility Study.
  • Project Charter: You then need to document the objectives, scope, team, timeframes and deliverables in a Project Charter.

Planning

  • Project Plan: You need to create a Project Plan listing all of the tasks required to undertake your project from start to finish. Every task must be scheduled, so you know what needs to be done and when.
  • Resource Plan: Next, you need to plan your resources by documenting the money, equipment and materials needed for your project.
  • Quality Plan: You then need to set quality targets, so that the project deliverables meet the expectations of your customer.
  • Risk Plan: All of the risks need to be documented and their likelihoodand impact on the project identified.
  • Communication Plan: You need to plan your communications, so that you send the right messages to the right people, at the right time.

Execution

  • Time Management: You need to use Timesheets to track time spent on your project. Then update your Project Plan with your Timesheet data to see whether your project is still within schedule.
  • Cost Management: Track your costs using Expense Forms. Every expense is formally logged and approved, so that you can confirm at any time that you are currently under budget.
  • Change Management: Document each change to the project scope, using Change Forms. You can then control change to ensure your project is always on track.
  • Risk Management: Use Risk Forms to document each risk to the project. You can then manage project risk carefully to ensure that nothing happens that will affect the project schedule or budget.
  • Issue Management: As each issue occurs on the project, you need to investigate its impact on the project and then write it up on an Issue Form. You can then kick off the tasks needed to resolve it quickly.

Closure

  • Project Closure Report: When your project is complete, document all of the actions needed to close the project properly. This includes releasing teams and suppliers, equipment and materials.
  • Post Project Review: And after your project has been closed, you can review its success and document the results for your sponsor. That way, you can show that all of the objectives were met and that the project was delivered on time and within budget.

—–

PMBOK version :

The PMBOK Guide is process-based, meaning it describes work as being accomplished by processes. This approach is consistent with other management standards such as ISO 9000 and the Software Engineering Institute‘s CMMI. Processes overlap and interact throughout a project or its various phases. Processes are described in terms of:

  • Inputs (documents, plans, designs, etc.)
  • Tools and Techniques (mechanisms applied to inputs)
  • Outputs (documents, products, etc.)

The Guide recognizes 42 processes that fall into five basic process groups and nine knowledge areas that are typical of almost all projects.

  • The five process groups are:
  1. Initiating
  2. Planning
  3. Executing
  4. Monitoring and Controlling
  5. Closing
  • The nine knowledge areas are:
  1. Project Integration Management
  2. Project Scope Management
  3. Project Time Management
  4. Project Cost Management
  5. Project Quality Management
  6. Project Human Resource Management
  7. Project Communications Management
  8. Project Risk Management
  9. Project Procurement Management

Each of the nine knowledge areas contains the processes that need to be accomplished within its discipline in order to achieve an effective project management program. Each of these processes also falls into one of the five basic process groups, creating a matrix structure such that every process can be related to one knowledge area and one process group.

The PMBOK Guide is meant to offer a general guide to manage most projects most of the time. There are currently two extensions to the PMBOK Guide: the Construction Extension to the PMBOK Guide applies to construction projects, while the Government Extension to the PMBOK Guide applies to government projects.