Are there any problems involved in 'backing out' of file virtualization?

Are there any problems involved in 'backing out' of file virtualization?

Removing virtualization can be highly disruptive to file servers and NAS platforms, but it really depends on what you're using virtualization for.

    Requires Free Membership to View

    When you register for SearchVirtualStorage.com, you’ll also receive targeted emails from my team of award-winning editorial writers. Every flavor of virtualization project – server, storage, desktop, file – offers challenges and rewards to the storage manager, and it’s our goal to ensure you’re up-to-date on the latest tips, trends and technologies that can help you overcome these roadblocks.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchVirtualStorage.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchVirtualStorage.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

As an example, file aggregation can change the way that data is organized, so you may need to unload all of the data, remove the file virtualization layer and then reformat and reload all of your data from scratch. By comparison, data migration is one of the most transparent file virtualization functions. You can install the virtualization and move the data to a new location or storage system. Afterwards, you can remove the virtualization layer or turn virtualization off until it's needed again.

Replication falls somewhere in between these two extremes. If the virtualization layer is required to successfully access the replicated data, removing the file virtualization layer can prove very disruptive unless the replicated data is in a format that applications can work with. It's important to test "back-out" procedures to weigh the disruption involved and determine whether key data will be left stranded.

Go to the beginning of the File Virtualization FAQ Guide.


This was first published in June 2007

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.