In information technology (IT) terminology, a key stakeholder is any individual who participates in fulfilling the requirements of the project. This can range from executives and project leads to any team member who functions as a subject matter expert (SME) — the term “stakeholder” doesn’t necessarily indicate that the individual has specific experience or knowledge. 

The purpose of identifying key stakeholders is simple: In order to keep the project within its timeframe and budget while achieving all of the goal outcomes, you’ll need a well-defined team. Below, we’ll introduce some important considerations to keep in mind during this phase of your project.

Datarecovery.com provides extensive resources for data migration. Whether you’re migrating to a new data tape format or moving mission-critical systems to the cloud, our team can help you accomplish your goals — while reducing the workload for all key stakeholders. 

To learn more, call 1-800-237-4200 to speak with a data migration expert or submit a request online.

Related: Data Migration to the Cloud: Best Practices

Key Stakeholders in Data Migration

Your list of key stakeholders will help you establish roles and responsibilities. When unexpected issues occur — and during a data migration project, issues inevitably occur — you’ll need to track the resolution of those issues. If you haven’t established the responsibilities of each team member, remediation can become a bottleneck. 

Some common key stakeholders for data migration projects include:

Executive Stakeholders

A CTO or other executive typically approves the plan for data migration and provides the necessary resources for a successful outcome. 

Data migration may affect nearly every aspect of an enterprise’s core IT systems, and as such, multiple executive stakeholders may be involved. However, most methodologies recommend assigning the ultimate accountability of the project to a single executive sponsor — otherwise, the scope of the project may grow considerably.

Project Leads and Project Coordinators

The project lead is chiefly accountable for the success of the project. In some cases, the executive stakeholder is also the project lead — but in most enterprises, the project lead will be a manager with defined authorities. The lead is often responsible for monitoring milestones and maintaining control of the scope of the project.

Project leads are often accommodated by project coordinators. Coordinators may use management methodologies to keep the data migration project moving forward. The project coordinator usually has fewer authorities than the project lead, but is responsible for escalating risks and identifying key issues that could affect timelines. 

Technical Leads

Technical leads are accountable for the success of specific technical areas of the database migration. For example, a technical lead may be assigned to ensuring that archives remain accessible and available after the migration occurs. 

Generally, technical leads may assign work to individuals and allocate resources as needed to accomplish their goal objectives. 

Many enterprises assign crucial data migration steps to individual technical leads — which can be a costly mistake. For instance, if a single team member is responsible for ensuring the availability of archived data post-migration, the outcome of the entire project rests on a single person’s shoulders. Working with a data migration partner can help your enterprise allocate workloads effectively, improving outcomes substantially.

Subject Matter Experts (SMEs)

SMEs have established skills in a given area. Web developers, programmers, business analysts, and other staff members may function as SMEs in the course of a data migration project. 

Generally, every department who will be affected by data migration should be represented in your SME group. This may include people from outside your IT department who can identify pain points that occur post-migration (for example, a customer service manager might be able to identify database migration problems that wouldn’t be immediately apparent to a sysadmin).

Data Migration Success Requires Comprehensive Planning

The first step of data migration is the accurate identification of key stakeholders. Of course, this isn’t the only important step: You’ll also need to identify the target data, establish the scope of the project, locate dependencies within datasets, analyze potential bottlenecks, and monitor metrics from the outset of the project.

Needless to say, data migration is an enormous undertaking. Many enterprises put off migration until it’s absolutely necessary — then rush through the process, which can have a disastrous impact on data availability and overall performance.

We strongly recommend working with an experienced data partner from the first stages of data migration. A qualified partner can limit the necessary resources for a successful migration, simplifying the project substantially. 

At Datarecovery.com, we have decades of experience with database migration, tape archive conversion, and media recovery. We leverage this experience to provide our clients with peace of mind, and by working closely with your IT team, we can ensure the integrity of your data throughout the process. 

Our team can help enterprises address the challenges of at-scale migration, which may include:

• Converting data for older datasets
• Mapping archival databases to newer systems
• Recovering data from physically damaged storage media
• Maintaining compliance with relevant security and privacy regulations

Learn more by calling us at 1-800-237-4200 or submit a request with our online case form.

The post Defining Key Stakeholders in a Data Migration Project appeared first on Datarecovery.com.

Even so, cloud systems aren’t ideal for every application or every type of workload. Some organizations may need to maintain internal systems or data tape archives to maintain control over data — or to ensure compliance with privacy and security regulations. 

Some questions to ask when deciding whether to engage a cloud migration project:

Will data migration reduce overall costs?

Generally, the operational expenses of cloud storage are less significant than the capital expenses of onsite equipment. However, it’s important to perform a detailed cost analysis prior to the first phase of the migration project — particularly for enterprises that are considering a hybrid model with both cloud and on-premises solutions.

Will data migration improve data integrity?

While modern cloud services offer extensive resources for assuring data integrity, some businesses may prefer to retain onsite archives to simplify compliance requirements or to maintain consistent access to certain types of data.

Will data migration improve our disaster recovery strategy?

Data loss is still possible after cloud migration (in fact, our laboratories regularly receive cloud data recovery requests from enterprises). Before migration, have a new backup strategy in place. While data backup is usually easier when working with a centralized storage solution (in this case, the public cloud), strategy is still essential.

What data will need to move to the cloud?

Many enterprises maintain archives of data tapes in a variety of mediums (for example, DLT-4 and LTO-8), along with physical servers, network-attached-storage (NAS) devices, and other storage systems. Additionally, data may be in disparate formats, which can lead to issues after migration occurs.

For a successful migration, the data will need to be converted to standard formats. Ideally, all data will be equally accessible at the end of the project — but depending on your goals, you may choose to migrate a subset of data to control costs.

Below, we’ll explain some of the best practices for data migration to the cloud. However, it’s important to recognize that every project is different: While we’re providing general tips, we strongly recommend working with an experienced data partner to control costs, shorten project timelines, and limit the overall burden on IT personnel.

To discuss your cloud data migration with expert technicians, contact Datarecovery.com at 1-800-237-4200 or submit a case online.

6 Best Practices for Data Migration to the Cloud

1. Clearly define the scope of the project.

Cloud data migration requires prioritization, and prioritization is not possible if you haven’t properly defined the scope of the project. Start by describing the characteristics of the data: 

• Data Storage Medium and Location
• Data Type and Format
• Size (Amount) of Data
• Dependencies Within Datasets

When reviewing these characteristics, you’ll need to plan for how the data will function within the cloud system. Eliminating redundancies and addressing inaccuracies will ensure a smoother transition (and in many cases, reduce the overall cost of the project).

2. Establish the goals of cloud data migration.

Your business may need to move to the cloud to enable future growth — but if your IT systems are relatively fixed, migration may be an unnecessary expense. Likewise, some enterprises can dramatically lower their expenses by eliminating physical servers, but for other organizations, this isn’t a significant reason to make the switch. 

Identify why your business should migrate data, then build a migration strategy that reflects your goals. Your goal is to undergo migration once — even if you choose a phase-based approach — and if you’ve properly defined the scope of the project, you can categorize and prioritize data in accordance with your objectives.

3. Identify a timeline for data migration, but be prepared to make adjustments

Many enterprises attempt to perform data migration to the cloud in a single operation (the “Big Bang” approach). In most cases, a phase-based approach is simpler and less expensive, but the nature of your IT systems will determine the timeline. 

Avoid rolling data migration into another project. To meet established timelines, you’ll need to keep your teams coordinated, and attaching migration to other IT priorities can lead to confusion. 

4. Analyze potential bottlenecks.

When planning the timeline, consider unexpected circumstances that could prompt an adjustment. For example:

• Physical Damage to Storage Media
• Data Conversion for Older Datasets
• Mapping Issues with Archival Databases
• Security Compliance Requirements During Migration

Working with an experienced migration partner can help to offset many of these challenges. Datarecovery.com can perform recovery on damaged tapes, manage conversion, and correct inaccuracies before the migration occurs, reducing the burden on IT personnel — and ensuring data integrity during the most crucial phases of the project.

5. Identify metrics (and begin tracking performance). 

Decision makers will expect to see results following migration. After all, migrating data to the cloud requires enormous resources, and without clear metrics, demonstrating the benefits can be difficult.

Some potential metrics for data migration include:

• Reductions in Capital Expenses
• A Smaller Physical Footprint for Key IT Systems
• Faster Data Access Times
• Less Downtime
• Improved Customer Satisfaction (CSAT) Metrics

Depending on the data, you may need to track memory usage, disk/hardware performance metrics, application latency, and error rates. Start tracking metrics early; otherwise, establishing a point-of-comparison may be impractical, even if you operate the new system alongside the old system. 

6. Leverage external resources.

Public cloud providers offer useful tools for transferring databases, and some service providers provide hands-on support and training for IT staff. 

However, enterprises should always work with experienced data migration technicians — while cloud service providers can make the process simpler, few providers offer custom support for complex challenges such as managing dependencies of in-house applications. 

Start Creating Your Cloud Data Migration Strategy

Datarecovery.com is a leader in enterprise data migration. Our team can help you establish KPIs and data governance policies — and test your data migration strategy to identify areas for improvement. 

With fully equipped laboratories at each of our physical locations, we can also address media issues (such as damaged tape archives or failed RAID arrays), convert data to cloud-ready formats, and protect user data with best-in-class security controls.

Learn more by calling us at 1-800-237-4200 or submit a request with our online case form.

The post Data Migration to the Cloud: Best Practices appeared first on Datarecovery.com.

Apple’s Xserve utilizes a wide variety of RAID levels, and Datarecovery.com offers services for every configuration.

The most common configuration is a standard stripe set with parity ( RAID 5). The default RAID stripe size is 64k (128 sectors), and data is striped across all of the disks with a parity block that rotates between the drives; this parity block uses the XOR algorithm.

If one disk fails in a standard RAID 5, the RAID controller card can default to degraded mode and the server can continue to operate without interruption. Data recovery may be necessary if there is corruption within essential parity blocks or if a second drive fails while the array is operating in a degraded state. Additional data loss issues include failed firmware upgrades, RAID controller card failures, and natural disasters.

Xserve also supports hardware RAID levels 0, 1, 3, and 0+1. RAID levels 10, 30, and 50 are available, but these levels must be supported supported using host-based software RAID. Our engineers have experience with every configuration, including options not supported by Xserve hardware, and each of our laboratories is completely outfitted for Xserve data recovery.

If you have an Apple Xserve and you need to recover key files after a failure, contact us right away at 1.800.237.4200 to discuss options.

Real Laboratories for Xserve RAID Data Recovery

To keep your downtime to a minimum, we will work closely with your IT staff to create a case-appropriate recovery and reintegration plan. In some circumstances, this can include on-site recovery at your location or remote data recovery. We recognize that Xserve systems play a critical role in your business’s operation, and our experience with various Xserve models allows for a RAID recovery success rate of 95 percent (dependent on scenario, RAID level, and other factors).

Datarecovery.com operates fully outfitted laboratories – unlike our competitors, we do not receive your media and immediately outsource it to another facility.  With locations throughout the United States and Canada, we can quickly gain access to your RAID media and begin working on your case. We create full clones of every drive in the array before performing data recovery, and our Apple specialists can create software on-the-fly to address your server’s specific needs.

Datarecovery.com’s Xserve technology is unparalleled, and we’re always available to provide a free consultation. Call us now at 1.800.237.4200 and ask to speak with an Xserve expert.

Apple Xserve RAID
*Xserve is a registered trademark of Apple Computer, Inc. Datarecovery.com, Inc. is not affiliated with Apple Computer, Inc. All images herein are property of Apple Computer, Inc.

The post Apple Xserve RAID Data Recovery appeared first on Datarecovery.com.

The Dell PowerEdge series features enterprise-level capabilities with remarkably affordable pricing, and the servers are extremely popular with small businesses. Because of their popularity, Datarecovery.com has developed specialized technologies to treat data loss on various PowerEdge devices, and we offer service options to help businesses control their overall expenses.

PowerEdge servers use a variety of RAID configurations, but RAID 5 (a striped set with a parity) is by far the most common. PowerEdge uses a default RAID stripe of 64k, equivalent to 128 sectors, and the user’s data is striped across all disks. A parity block rotates between the member drives, ensuring redundancy.

If a single hard drive fails, the PowerEdge will not lose data – the RAID card will default to degraded mode and continue to operate without any interruption. However, if there is corruption within essential parity blocks or if more than one hard drive fails, the RAID volume will fail. These are the most common scenarios for data loss.

Creating a Plan for Dell PowerEdge Data Recovery

Datarecovery.com staffs certified engineers who are familiar with the PERC controller family, and with multiple laboratories with Class 5 clean rooms, we offer the most efficient PowerEdge recovery options nationwide. Our process begins with a thorough evaluation, which results in a price quote and a specialized recovery plan for your case.

Our engineers then create disk images of all functional RAID hard drives while repairing any damaged drives that are necessary to the set. We draw from substantial experience – many of our engineers have worked with PowerEdge servers for decades, and whether you have a tower, blade, or rack system, we can develop an optimal strategy to return all essential files on your schedule.

We provide recovery services for all PowerEdge configurations including (but not limited to):

• RAID 1 (Mirrored Set)
• RAID 0 (Striped Set)
• RAID 5
• RAID 6
• All Types of Nested RAID

Provided that your RAID has not been rebuilt in an incorrect configuration, the chances of a successful recovery are usually very high. We encourage you to contact our engineers before attempting to rebuild or repair your RAID, particularly if the cause of the failure isn’t immediately apparent. Datarecovery.com provides free consultations and RAID evaluations, and our secure laboratories give you excellent options following any server failure.

Call 1.800.237.4200 and ask to speak with our Dell PowerEdge RAID recovery experts.

The post Dell PowerEdge Data Recovery appeared first on Datarecovery.com.

The RAID arrays and NAS & SAN devices sold by Sun and Oracle are built with a high degree of redundancy and superior hardware, but as is the case with all servers, data loss is possible.

Our data recovery engineers are specially trained to work with Sun and Oracle servers, and have specific experience with the Solaris operating system as well as the other operating systems that the servers use to operate. Datarecovery.com engineers are able to obtain full data sets from the vast majority of Sun server cases.

Our Detailed Data Recovery Process for Sun Servers

Every Sun server is different, and our data recovery process is substantially different in every case.  When you call 1.800.237.4200, an engineer will speak with you to determine the best course of action for your server.

Remote recovery is often the fastest option. This allows your system to be re-mounted and used normally after recovery is complete, and your hardware remains at your physical location. An engineer connects to your server through remote software with bit-level access. We correct errors and use logical procedures to return the server to its original condition, and downtime is minimal.

Some Sun NAS devices and RAID arrays have issues that must be addressed in-lab. This is most common in instances where a power surge or misconfiguration led to the failure or corruption of several drives. In these cases, we recover the damaged media in a Class 5 clean room using advanced data recovery techniques. Clones are made of the failed drives to ensure the best possible results, and data corruption is addressed with specialized software.

Speak to an engineer at 1.800.237.4200 to discuss recovery options for your case.

Sun Server Error Messages And Symptoms

There are numerous symptoms that could indicate data loss on a Sun server. Primary indicators are LEDs and Solaris GUI alerts that show failure of more than one hard drive (enough drives where built-in redundancy doesn’t prevent data loss). If LEDs on your Sun server indicate power failure or a poor operating environment despite contrary conditions, you should contact Sun customer support or speak to a recovery engineer as soon as possible.

Configuration issues can also make data inaccessible, and these can be a major concern. “Error executing server” is one example, but this can have a simple or complex solution; it simply indicates that the server is unable to operate. These types of “Unknown” errors on Sun servers generally indicate some type of hardware failure which prevents the server from starting up properly.

You should take enormous care when addressing configuration issues, as it’s possible to complicate even simple problems on high-end servers with minor missteps. Engineers at Datarecovery.com can determine whether your Sun server’s error messages indicate a need for data recovery.

Supported Sun and Oracle Servers

We currently support data recovery services for all Sun Microsystems servers, RAID arrays, SANs, and NAS devices. A partial list of supported servers is below.

• Sun SPARC Enterprise Servers
• Sun Blade Servers
• Older Legacy Sun Systems
• Sun Fire X4540 Server
• Sun Fire X4240 Server
• Sun Fire X4150 Server
• Sun Fire X4140 Server
• Sun Microsystems
• Sun SPARC Enterprise M3000 Server
• Sun SPARC Enterprise T5120 Server
• Sun SPARC Enterprise T5140 Server
• Sun SPARC Enterprise T5220 Server
• Sun SPARC Enterprise T5240 Server
• Sun SPARC Enterprise M4000 Server
• Sun SPARC Enterprise M5000 Server
• Sun SPARC Enterprise T5440 Server
• Sun SPARC Enterprise M8000 Server
• Sun SPARC Enterprise M9000 Server
• Sun Netra UltraSPARC Rackmount Servers
• Sun Netra T5440 Server
• Sun Netra T5220 Server
• Sun Netra T2000 Server
• Sun Netra x64 Rackmount Servers
• Sun Netra X4250 Server
• Sun Microsystems Server
• Sun Netra X4200 Server
• Sun Netra ATCA Blade Servers
• Sun Netra CT900 Server
• Sun Netra UltraSPARC ATCA Blade Servers
• Sun Netra CP3260 ATCA Blade Server
• Sun Netra CP3060 ATCA Blade Server
• Sun Netra x64 ATCA Blade Servers
• Sun Netra CP3250 ATCA Blade Server
• Sun Netra CP3220 ATCA Blade Server
• Sun Netra CP3020 ATCA Blade Server
• Sun Storage F5100 Flash Array
• Sun Storage 7110 System
• Sun Storage 7210 System
• Sun Storage 7310 System
• Sun Storage 7410 System
• Sun Storage J4200 Array
• Sun Storage J4400 Array
• Sun Storage J4500 Array
• Sun Fire X4540 Storage Server
• Sun Fire X4240 Storage Server
• Sun Fire X4170 Storage Server
• Sun Fire X4140 Storage Server
• Sun Fire X4140
• Sun Fire X4240
• Sun Fire X4440
• Sun Fire X4540
• Sun Microsystems Sparc Server
• Sun Fire X4640
• Sun Netra X4200 M2
• Sun Netra CP3020 Blade
• Sun Ultra 27 Workstation
• x64 Intel Xeon Rackmount
• Sun Fire X2270 Server
• Sun Fire X4170 Server
• Sun Fire X4270 Server
• Sun Fire X4275 Server
• Sun Fire X4450 Server
• Sun Netra X4250 Server
• Sun Netra X4450 Server
• x64 Intel Xeon Blade
• Sun Netra CP3250 ATCA Blade Server
• Sun Blade X6270
• Sun Blade X6275
• Sun Blade X6450

Sun Sparc Server Data Recovery Tips

When you speak to a data recovery engineer, be sure to have as much information as possible regarding the symptoms that led to data loss. You should also try to collect information about the operating system, file system, the number of drives in the NAS, RAID, or SAN, and any other information that might be relevant to the process.

Do not attempt to run your server after data loss occurs. Never reinitialize a server with multiple failed drives without contacting Sun Microsystems or a trained data recovery engineer.

Most Sun server cases result in a full 100% recovery of requested data. By acting quickly, the chances of recovery are improved and cost and turnaround time are reduced dramatically.

To contact us, please contact us by phone or email for more information or set up a case online.

*Sun Microsystems and its product names are registered trademarks of Oracle Corporation.Oracle.com. Oracle Corporation is not affiliated with Datarecovery.com, Inc. in any way. All product names, registered trademarks, and trademarks are the property of their respective owners.

The post Sun Microsystems Data Recovery appeared first on Datarecovery.com.

Due to the precautions built into NetApp devices, complete data loss is very rare. However, data recovery services are sometimes necessary when data is being read incorrectly, when files suddenly appear missing, and when configuration issues or hard drive failures prevent the servers from acting normally.

We’ve worked with hundreds of NetApp devices, and recovery rates are very high, in part due to their high levels of redundancy and professional features that prevent user errors.

NetApp Server/NAS Data Recovery Procedures

Many NetApp servers can be recovered remotely through a secure Internet connection.  When possible, remote recovery is preferable to both our clients and our data recovery engineers.

By connecting through the Internet to the server at a bit level, engineers are able to fix many types of corruption, resolve configuration issues, and even resolve some hard drive failures (though the failed devices will need to be replaced at the end of the data recovery process). In most situations, NetApp NAS devices simply need to be remounted after recovery procedures are complete, and the entire process can take less than a day. Typically, a NAS or SAN device’s full functionality can be restored using remote recovery.

In rare cases, in-lab recovery is necessary for servers. Our engineers assess each situation to make sure that in-lab procedures are only used when it’s absolutely critical for the data recovery process, as we understand that downtime is a major issue in all server recovery cases. Onsite NetApp recovery is possible in some instances, and we will discuss all available options to limit expenses.

In these situations, the drives from the NAS, SAN, or RAID must be shipped to one of our laboratories, where we combine standard data recovery techniques with advanced virtualization to simulate the original operating environment of the server.

We create clones of all hard drives to ensure that the process is completely non-destructive. All in-lab server cases are expedited, and 24/7 recovery work is available for extreme situations. All data is handled securely, and every step is taken to ensure efficient processing. In-lab recovery work also has a very high success rate.

NetApp Error Messages

Many error messages can indicate data loss on NetApp devices, and the exact messages displayed will differ depending on your operating environment.

For example, “The system cannot find the device specified” is sometimes displayed in Windows when a NetApp NAS cannot locate its media. However, this can also be displayed for a variety of other reasons–it’s best to contact NetApp support if this error message arises, particularly if it only seems to pop up when certain programs are in use.

“Failure of controller” indicates that the controller is functioning improperly and is unable to boot normally. This is different from “Failback of controller,” which indicates that the controller failed, but restored to older settings or fell back to another controller; the device should be functioning properly (although maintenance may be necessary) when “Failback of controller” is displayed.

Several hard drives can fail simultaneously on any server, and although this is exceptionally rare, it is a possible scenario. If multiple hard drives have failed, it’s vital to keep your NetApp device powered off until contacting a data recovery engineer for further instructions.

To diagnose a specific NetApp error message, call us at 1.800.237.4200 and ask to speak with a NAS specialist.

Supported Devices for NetApp Data Recovery

We support data recovery on every NetApp device, regardless of configuration, operating system, or file system. A partial list of supported products is below. If your device is not listed, please contact an engineer at 1.800.237.4200 to discuss options.

• FAS8000 Series
• FAS2500 Series
• FAS6000 Series
• FAS3100 Series
• FAS2000 Series
• Data ONTAP GX Systems
• NearStore on FAS
• NetApp VTL
• V6000 Series
• V3100 Series
• Information Server – IS1200
• E5500 and All SAN Devices Including Flash-Based Systems

Preparing for NetApp Data Recovery

Do not attempt to initialize or rebuild a NetApp server without contacting a data recovery engineer, as this can compromise data integrity. Collect as much information about the failure as possible, and also some information about the server itself, specifically its configuration, the number of drives (and their capacities), operating system, file system, and any error messages that were logged leading up to the data loss.

The data recovery process is usually very fast, but providing as much information as possible will decrease turnaround time and help to keep costs low. Once you have this information, call us at 1.800.237.4200 and ask to speak directly with a NetApp RAID Engineer.

Visit this page for more contact options or to set up a case online.

*NetApp and its product names are registered trademarks of NetApp Corporation located in Sunnyvale, California netapp.com. NetApp is not affiliated with Datarecovery.com, Inc. in any way. All product names, registered trademarks, and trademarks are the property of their respective owners.

The post NetApp Data Recovery appeared first on Datarecovery.com.

As Isilon servers are designed to avoid any data loss, and as their exceptional OneFS operating system (in its fifth revision when this web page was written) detects hardware errors and corruption very accurately, many of the cases that we receive are due to a user error, failed rebuild, or other issue not intrinsic to an Isilon system’s original setup. These cases are usually easily recoverable.

It should be noted that data loss and server failure is always possible, regardless of built-in redundancies and error correction. In order to overcome technological difficulties associated with this complex technology, Datarecovery.com laboratories employ custom technology that is not found anywhere else in the world, allowing us to recover the data efficiently and successfully.

The Data Recovery Process

Each case must be carefully evaluated to determine the extent of failure. We try to gather as much information as possible about server cases, especially Isilon cases, as their proprietary OneFS operating system can certainly affect our recovery procedures.

In general, we require that hard drives from a server to be shipped to one of our locations, where damaged hard drives from the NAS appliance are rebuilt in a class 5 clean room, at which point a special clone drive of each damaged and working hard drive is created. As some Isilon servers contain solid state hard drives (such as the 5000S-SSD), and due to the variety of possible failure scenarios with high-end servers, some cases may not require clean room work. However, physical procedures are necessary on a majority of cases, and all cases will begin with all drives being cloned, as this prevents the possibility of damage to the original media at any point in our process.

Data corruption is addressed in each case, and any overwritten data is recovered using proprietary methods. Once a full copy of data is accessible, we are able to copy the data you need (or the entire server) to return media, such as another server or additional drives for the original server. An engineer will discuss return media options on a case by case basis. An encrypted, secure copy of your data is kept at our laboratories until your data has been verified as accessible and working. This prevents permanent loss due to shipping errors, which occur in far less than 1% of cases. When data has been verified, the copy of your data is securely destroyed. We realize that cases involving NAS devices and Isilon servers in particular are often of critical importance. Every possible step is taken to minimize your downtime and return your data as quickly and safely as possible. Many server cases are completed within a day or two, and 24/7 emergency services are available when necessary for all Isilon NAS cases.

Recognizing Isilon Error Indicators

Isilon devices have no single point of failure and boast a “self-healing” cluster, which makes data loss due to disk or node failure exceedingly unlikely. The system will notify its users via onscreen alerts and email alerts when a hard drive fails, and rebuilds are handled in-system to minimize possible user-error. Nevertheless, it’s possible for multiple hard drive failures to incapacitate any large server. The number of hard drives that would have to fail to cause data loss varies among Isilon models, but if data has become inaccessible and several hard drive failures have been reported, this is a potential possibility. Failed hard drives in any server should always be replaced as quickly as possible for this reason. Improperly handled rebuilds are unlikely to cause damage to an Isilon system, but again, there is some potential for user error to overwrite data in some specific circumstances. A system administrator should always follow the detailed procedure outlined in Isilon NAS manuals when performing any hardware changes, especially when replacing failed hard drives.

If you’ve noticed data loss after a hardware change on an Isilon NAS device, power the system down and contact a DataRecovery.com engineer as quickly as possible.

Supported Isilon NAS Devices

We support data recovery on all Isilon data storage devices, including the following NAS devices:

Isilon IQ S-Series: IQ 5400SIQ 5000S-SSD Isilon IQ X-Series: IQ 1920XIQ 3000XIQ 6000XIQ 9000XIQ 12000XIQ 36000XIQ 72000XIQ 10000X-SSDIQ 32000X-SSD Isilon IQ NL-Series: IQ 36NLIQ 72NL If your device isn’t listed above, contact us at 1.800.237.4200.

Data Recovery Tips For Isilon Servers

As noted earlier, Isilon servers are designed to avoid failure, and any symptoms of data loss can be serious. If possible, shut down your server and contact either Isilon support or an engineer at DataRecovery.com. Collect as much information about the server as possible, including model number, the number and size of the attached drives, the amount of data that was stored on the system, and any error symptoms. This will help our engineers to minimize your turnaround time, and may help to lower the cost of recovery.

Call us now at 1.800.237.4200 for a free consultation. 

*Isilon and IQ are trademarks or registered trademarks of Isilon Systems, Inc. Isilon Technology (USA), Inc. is not affiliated with Datarecovery.com, Inc. in any way. All product names, registered trademarks, and trademarks are the property of its respective owners.

The post Isilon RAID Data Recovery appeared first on Datarecovery.com.

One of the major draws of Snap Servers is their low-maintenance, dependable design. However, data recovery is still sometimes necessary when a redundant array fails due to several damaged drives, misconfiguration, or any of a number of other issues. We have provided data recovery on Snap Servers and appliances since 1998, and our engineers have worked with hundreds of the devices. Our recovery techniques on Snap Servers have revolutionized the data recovery industry, and most cases end in a full recovery of all missing or inaccessible data.

Read more about our NAS recovery service here.

Snap & REO Server Data Recovery Procedures

The recovery process will vary depending on the model number of your Snap Server and its unique issues. When possible, our engineers use remote recovery techniques. This ensures minimal downtime, and no hard drives or hardware devices need to be shipped. In remote recovery cases, our engineers access your NAS, SAN, or RAID device on a bit level to clear data corruption and configuration issues that prevent normal operation. In most cases, the entire data recovery process is complete within a few hours, and you’ll simply need to remount the device to use it. Some instances require a data transfer and reinitialization of the server; in these cases, we will require an additional server or device to transfer the recovered data before initialization. Some cases cannot be recovered remotely, as a class 5 clean room is necessary when any hard drive recovery techniques are necessary. These are treated as priorities and emergencies to minimize downtime and get your server and data operating as quickly as possible. Drives (usually not supporting hardware) will need to be shipped to one of our laboratories, where the damaged drives are repaired and cloned. The NAS or SAN is then rebuilt, and recovered data is backed up. By cloning the drives, we ensure that every method that we use for recovery is completely nondestructive and secure.

Error Messages on Snap Servers

The most common problematic error message on a Snap Server lists the date and time in the system log, followed by:

ERROR Disk Driver : Cannot Read Device 80070000 Block 2081904.

This error indicates a fatal flaw in one or more of the hard drives of the NAS. It does not, however, necessarily indicate that a hard drive has failed; corruption or electronic issues may be preventing the system from booting normally. Most NAS devices have built in redundancy, which means that failure of one hard drive is not in itself a serious issue as long as the drive is replaced quickly. However, if multiple hard drives fail or if other issues are preventing your data from being accessible, it’s very important to avoid any attempt to replace failed drives. Reinitializing a failed device, whether it’s a NAS, SAN, or RAID, can potentially overwrite data. Overwritten data is much more difficult to fully recover. You should immediately call a data recovery professional or Overland Storage customer service if you’ve seen a “Cannot Read Device” error message. Review your entire system log, and note anything unusual. The more information you’re able to gather about the failure, the better the chances of a fast, inexpensive, and full recovery. Our server engineers can discuss data recovery options and provide some guidance to help you get your Snap Server running in its normal operating condition. Contact an engineer at 1.800.237.4200.

Supported Overland Storage Snap SAN, NAS, and RAID Devices

Data recovery is supported on the following servers, as well as all older servers (including Adaptec Snap Servers). If your device is not listed, it is still supported. Call us for more information.

• Snap Server SAN
• Snap Server NAS 650
• Snap Server NAS 620
• Snap Server NAS 410
• Snap Server NAS 210
• Snap Server NAS 110
• Snap Server NAS 650 with iSCSI
• Snap Server NAS 620 with iSCSI
• Snap Server NAS 410 with iSCSI
• Snap Server NAS 210 with iSCSI
• Snap Server NAS 110 with iSCSI
• REO 9100
• REO 4600
• REO 1550

(Note: REO devices are virtual tape libraries. We use the latest tape recovery techniques for these servers.)

Data Recovery Tips for Snap Servers

Regardless of whether you’ve got a SAN, NAS, or VTL RAID, it’s important to avoid overwriting any of the data on the device. As such, when multiple hard drives fail, you should avoid attempts to rebuild the server. Gather as much information as possible about symptoms leading up to the failure, as well as information about the server itself. Our engineers will need to know the file system and operating system of the device, its configuration, and a brief explanation of the failure. If you’re unable to gather any of this information, a trained server engineer can help you find out more before the data recovery process begins.

To contact us, please contact us by phone or email for more information or set up a case online.

*Overland Storage and its product names are registered trademarks of Overland Storage Corporation. Overland Storage is not affiliated with Datarecovery.com, Inc. in any way. All product names, registered trademarks, and trademarks are the property of their respective owners.

The post Snap Server Data Recovery appeared first on Datarecovery.com.

Most Proware® products (including NAS devices) use one of six possible RAID configurations to minimize the possibility of data loss and offer fast performance. Unfortunately, while Proware® servers extremely dependable, data loss is always possible.

Recovery Procedures for Proware® Technology Corp. Servers and NAS Devices

Our recovery process will vary depending on the level of RAID that your Proware® server uses, its exact failure scenario, and many other variables. Most cases start with an in-house evaluation, after which an accurate price can be quoted for the recovery. Evaluations require the hard drives from your Proware® Technology server (both working and non-working) but not the hardware from the server itself.

If the estimation is accepted, any physically failed hard drives are treated as quickly as possible in a class 5 clean room by trained data recovery engineers. Clones are made of both failed and good hard drives, which ensures that every further procedure is nondestructive and stands no chance of damaging your data.

Different levels of RAID require different data recovery techniques, but for common RAID types such as RAID 0 and RAID 5, the array is then reconstructed. This is handled through virtualization software and on-site arrays. Corruption and other issues are then treated before data can be accessed.

Once data is accessible, it is transfered to a return media and shipped back to our clients. A copy of each drive from the Proware® server is kept in our drive database for a period of 3-5 days or until data is confirmed, at which point each drive is permanently erased.

At datarecovery.com, we know the potential costs of a failed server, and we do everything possible to reduce these costs by offering the fastest, most reliable data recovery services in the world.

Proware® Server LED Notifications and Error Messages

Proware® servers use LEDs to notify a user when an error requires attention. These LEDs (and often, an onboard LCD) will notify you of any hard drive failures. On most Proware® Technology systems, the LED for each drive will be blue (operating) or green (working) during standard operation. A failed hard drive’s LCD will appear orange. Read the onscreen prompt or LCD to see whether a drive has failed, or if a configuration or installation problem is preventing it from functioning normally.

Note that Proware® systems will often display error messages, either in user logs, onscreen prompts, or on-device LCDs, when a serious data issue has been detected.

The event logs are usually the best place to look for error messages that might help you diagnose the data loss issues that your server is experiencing. Event logs can be accessed through proRAID management software (included with many Proware® servers) or other RAID management software, or even through the LCD panel.

The following events may indicate a possible cause of failure or inaccessibility for Proware® servers. If you find evidence of any of these events, contact a data recovery engineer.

• Over temperature warning
• Over voltage warning
• Low voltage warning
• PSU not present warning
• Fan not present warning
• Fail to setup network configuration warning
• Array initialization failed warning
• Array rebuild failed warning
• Array expansion failed warning
• Array parity checking failed warning
• Disk clone failed warning
• Mirror disk clone failed warning
• System restart warning
• Parity error detected warning*

In particular, error messages relating to array rebuild failures should be especially noted, and no further attempt should be made to restart your array. If user or hardware errors caused a failed rebuild, failed clone, or parity issues, recovery is extremely likely, but there’s some potential for an accidental overwrite. Exercise extreme caution when working with a Proware® server or NAS device after a failed rebuild.

*: Note that Proware® RAID arrays avoid potential parity issues by monitoring parity information as it is input to the drives in an array, regardless of RAID configuration; if a drive incorrectly reports the parity information back to the system, the system will retry the command. Disks that are unable to successfully log parity info are shut down. Therefore, arrays reporting a parity error are usually very simple recovery cases. Contact an engineer at 1.800.237.4200 for more information.

Supported Proware® Technology Storage Systems

Our laboratories can perform data recovery services on all Proware® systems, including the following storage devices.

• SB-2123-F4S3
• EP-2123S/D-F4S3
• EP-2129-F4S3
• SB-2803-F4A3
• SB-2123-F4A3
• SB-3163S-F4S3
• EP-3163S/D-F4S3
• EP-3169S/D-F4S3
• SB-3163E-F4A3
• EP-4423S/D-F4S3
• EP-4429S/D-F4A3
• DP-503-F4A3
• EP-T803-F4A3
• SB-2123-S3S3
• EP-2123S/D-S3S3
• SB-2123-S3A3
• SB-2803-S3A3
• SB-3163S-S3S3
• EP-3163S/D-S3S3
• SB-3163-S3A3
• EP-4423S/D-S3S3
• EP-T803-S3A3
• SB-1404-G1A3
• SB-2124-G1S3
• SB-2804-G1A3
• SB-2124-G1A3
• SB-3164E-G1S3
• EP-3164D-G1S3
• Proware® System
• SB-3164E-G1A3
• DP-504-G1A3
• B-1403E-SA3
• EP-2126-SS
• SB-2803-SA
• EP-2806-SA3
• SB-2123SA
• EP-2126-SA3
• EP-3166-SS
• SB-3163SA
• EP-3166-SA3
• DP-403E-SA3
• EP-T803-SA3
• SB-1413-UA
• EP-2803-UA
• EP-2803-WA
• DP-403-UA
• EP-D501-AA
• EP-m501-AA
• EP-D501-CA
• EP-m501-CA
• SN-1403 SATA NAS
• EN-2126 SAS NAS
• SN-3163 SAS NAS
• DN-503 SATA NAS
• EN-2126 SATA NAS
• EN-3166 SAS NAS
• EN-2800 SAS NAS
• DN-500 SATA NAS
• SN-1400 SATA NAS
• EN-T800 SATA NAS

Because Proware® manufactures a vast line of storage products, only recent, popular products are listed. If your Proware® Technology server or storage system isn’t on this page, we still offer data recovery services for it; contact us at 1.800.237.4200 for more information.

Proware® Technology Server Data Recovery Tips

In order to maximize the chances of a successful data recovery, it’s important to avoid any action that could exacerbate the situation, particularly if one or more of the hard drives in your server have failed. Consult your Proware® device’s event logs and note anything unusual, then shut down the server.

Contact a data recovery engineer at 1.800.237.4200 with as much information about the server as possible. Describe any symptoms that might be useful from a diagnostic viewpoint. In most situations, an engineer will be able to estimate a probable chance of recovery and turnaround time over the phone, and although a more in-depth, physical evaluation is necessary to determine cost, we may be able to provide a rough approximation.

Call us now at 1.800.237.4200 for a free consultation.
*Proware® and all mentioned model names are trademarks or registered trademarks of Proware® Technology Corp. Proware® Technology Corp is not affiliated with Datarecovery.com, Inc. in any way. All product names, registered trademarks, photos and trademarks are the property of their respective owners.

The post Proware® RAID Data Recovery appeared first on Datarecovery.com.

This page contains a basic overview of our HP server recovery services.  For more information or to speak with a specialist, call 1.800.237.4200.

HP Proliant Data Recovery Options

We offer both remote recovery and in-lab services for all types and models of HP servers, including RAID arrays, SAN, and NAS devices. An engineer will need to speak with you to evaluate whether remote recovery is possible.

Remote recovery allows our engineers to log into your server on a block level, and they can fix any corruption that’s preventing the server from loading properly. This allows you to simply remount your server and continue to operate it normally.

Depending on the situation, you may have to perform some minor steps (such as switching out a hard drive), but most of the process is handled directly by a recovery engineer. In advanced cases, we may need to copy the data from your server to another device in order to insure data integrity. Each case is different, but our engineers will be able to explain the entire process to you once the situation has been properly assessed.

In-lab recovery services are necessary when multiple drives have failed, past the point where your HP server’s redundancy would have prevented data loss. In these cases, our engineers work on the failed drives in a safe, class 5 clean room. Clones are created of failed drives, and the server is rebuilt at our location, where we can work through any additional corruption and provide you with 100% of the lost data.

In either case, extreme measures are taken to insure data integrity and security. All server cases are handled as priorities, because downtime is a major concern for our clients. Servers often contain millions of critical files that businesses depend on to operate, and we keep that in mind from the moment that a case is opened.

HP Proliant Error Messages

Depending on your system, various error messages can indicate data issues on an HP or Compaq server. Some common error messages which can have quick resolutions are listed below.

STOP 0x0000001E (0xc0000005,…) KMODE_EXCEPTION_NOT_HANDLED
HP Proliant Data Recovery Server

This error is usually present when the operating system cannot boot, and it occurs on ProLiant systems with Windows installed. In many cases, it is possible to get the system operational by simply installing Service Pack 6, which contains a fix.  However, if the operating system cannot boot to the point where the service pack can be installed, data can be completely inaccessible.

Drive Fault LED is lit on ProLiant or Integrity server

When an LED on your HP or Compaq server indicates a drive fault, you can often install a new drive, as HP servers are typically built with relatively high fault tolerance. Multiple LEDs may indicate simultaneous failure of several drives. This can be due to configuration issues, power surges, and other problems. Although it is unusual for more than a single hard drive to fail at one time, we receive hundreds of cases each year with this exact scenario.

In these cases, in lab data recovery may be necessary. Do not attempt to reinitialize any server, whether it’s a NAS, RAID, or other type of device, without contacting a trained data recovery engineer or HP customer service.  Call us at 1.800.237.4200 to discuss options.

Unknown Error on HP or Compaq Server (any model)

If your server presents an unknown error, the most common cause is improperly installed or failing hardware.

As with drive failures, some caution is necessary. In many cases, there’s a very simple solution; by running a minimal configuration and gradually adding hardware devices one at a time, it’s possible to locate the cause of the problem and replace or repair the offending hardware. Again, it’s important not to reinitialize the array, as this can result in data loss. Our data recovery engineers can talk you through the process to fix unknown errors on HP servers, and can evaluate whether data recovery services are necessary. In most cases, unknown errors and LED errors can be easily fixed through our remote services.

These are only a few examples of HP server error messages that can cause data to be lost or inaccessible. Many error messages may be displayed on HP devices, and it’s impossible to give a full list. However, our engineers are able to quickly evaluate any issue that your server is experiencing. Be sure to write down error codes, as these can be a vital key to determining a quick, efficient, and cost-effective data recovery method.

Supported HP Proliant Devices

We support data recovery on hundreds of HP servers and devices. If your device isn’t listed below, it is still supported; this is not a comprehensive list of our capabilities.  Call our offices and ask to speak to a dedicated server engineer.

• HP ProLiant ML100
• HP ProLiant ML300
• HP Proliant Data Recovery Hard Drive
• HP ProLiant ML110 G5
• HP ProLiant ML350 G5
• HP ProLiant DL100
• HP ProLiant DL300
• HP ProLiant DL500
• HP ProLiant DL700
• HP ProLiant DL1000
• HP Blade BL Systems
• HP ProLiant SL2x170z G6 Server series
• HP ProLiant SL170z G6 Server series
• HP ProLiant SL165z G6 Server series
• HP ProLiant SL160z G6 Server series
• HP Integrity servers (all types and grades, including Blade and NonStop systems)
• HP ProLiant Carrier-Grade Servers
• HP ProLiant MicroServer
• Older HP RAID, NAS, and SAN devices

HP Proliant Data Recovery Options

While the operating system of your HP server does not significantly affect the chances of a full data recovery, it can affect our data recovery process, especially for remote recovery cases. For instance, Integrity servers running Linux or OpenVMS will usually require an engineer who has been specifically trained in those systems, and who has experience in fixing data corruption issues on said systems.

For this reason, it can be very helpful to have as much information about your system as is possible from the first stage of our data recovery process. Try to gather as much information as you can before contacting an engineer, including operating system, file system, the number of disks in the server, and symptoms that preceded the failure. This will help to minimize downtime. If you do not have access to some of this information, our engineers will be able to ask several questions and guide you through several steps that can give us the information that we need.

Do not try to operate your HP server after data becomes inaccessible. Various issues can cause data loss, and depending on the scenario, operating your server can result in further corruption and overwritten data which can complicate the recovery process.

To contact us, please contact us by phone at 1.800.237.4200 or email for more information or set up a case online.

*HP, Proliant and other names are registered trademarks of Hewlett-Packard Development Company, L.P. Hewlett-Packard Development Company, L.P. is not affiliated with Datarecovery.com, Inc. in any way. All product names, registered trademarks, and trademarks are the property of their respective owners.

The post HP Proliant Data Recovery appeared first on Datarecovery.com.