how to split all flash datastore which is 190 TB

Muhammad Imran Lv2Posted 03 Nov 2023 15:57

Anyone knows how to split datastore which is 190 TB all flash.
Remember 160 TB space is occupied already.

jerome_itable has solved this question and earned 20 coins.

Posting a reply earns you 2 coins. An accepted reply earns you 20 coins and another 10 coins for replying within 10 minutes. (Expired) What is Coin?

Enter your mobile phone number and company name for better service. Go

Splitting a 190 TB Sangfor datastore with 160 TB occupied space can be a complex task, but it is possible with careful planning and execution. Here's a step-by-step guide on how to split the datastore:

    Preparation:
        Backup: Make sure you have a complete backup of your existing datastore before proceeding. This will ensure that you can restore your data in case of any issues during the splitting process.
        Free Space: Ensure that you have at least 30 TB of free space available on your storage system. This space will be required to temporarily hold the data while you split the datastore.
        Network Bandwidth: Ensure that you have sufficient network bandwidth to handle the data transfer during the splitting process. This can be a bottleneck, so make sure you have adequate bandwidth to avoid slow transfer speeds.

    Data Migration:
        Identify Split Point: Determine the point at which you want to split the datastore. This could be based on file size, file type, or any other criteria that makes sense for your data organization.
        Create New Datastore: Create a new datastore to hold the data that will be split from the existing datastore. This datastore should have sufficient capacity to accommodate the data being moved.
        Migrate Data: Use Sangfor's built-in data migration tools to migrate the data from the existing datastore to the new datastore. This process will copy the data from the source datastore to the destination datastore without affecting the data itself.

    Datastore Splitting:
        Stop Services: Stop all services that are using the existing datastore to prevent any data inconsistencies during the splitting process.
        Unlink Datastore: Unlink the existing datastore from the Sangfor cluster. This will remove the datastore from the cluster's management and allow you to modify it directly.
        Shrink Datastore: Use Sangfor's datastore management tools to shrink the existing datastore to the desired size. This will free up space on the storage system for the new datastore.
        Expand New Datastore: Use Sangfor's datastore management tools to expand the new datastore to the desired size. This will make it ready to receive the data that was migrated in the previous step.
        Link Datastores: Link the new datastore to the Sangfor cluster. This will make it available to the cluster and allow applications to access it.
        Start Services: Start all services that were stopped in step 3. This will allow applications to resume normal operation using the split datastores.

    Verification:
        Data Integrity: Verify the data integrity of both the existing datastore and the new datastore. This ensures that the data was copied correctly during the migration process.
        Application Functionality: Test the functionality of your applications to ensure that they are working correctly after the datastore split. This includes data access, performance, and any other relevant aspects.

Remember that splitting a large datastore can be a time-consuming and resource-intensive process. It is important to plan carefully and execute each step meticulously to minimize downtime and ensure data integrity. If you are not comfortable performing the splitting process yourself, it is recommended to engage a qualified Sangfor administrator or consultant to assist you.
Is this answer helpful?
mdamores Lv3Posted 08 Nov 2023 10:14
  
this will be a very complex operation, and the steps will vary depending on the infrastructure and requirements. you may try the below:

1. back up your data before making any changes. backup should be separate from the existing data store to prevent data loss during the split
2. choose splitting method and create new datastore with the desired capacity and migrate data from the existing datastore to the new one.
3. you might be able to create new one within the existing datastore and move data in between if you are using LUNs
4. testing after the migration and monitoring
5. decommissioning of old datastore once you are confident that all data has been migrated successfully
Farina Ahmed Lv5Posted 08 Nov 2023 16:39
  
Splitting a 190 TB all-flash datastore with 160 TB occupied involves a careful approach to ensure data integrity and minimal disruption. First, identify the virtual machines (VMs) and their storage requirements within the datastore. Prioritize critical VMs and plan for downtime if necessary. If you have vCenter Server, use Storage vMotion to migrate VMs to another datastore with available space. Alternatively, you can add additional storage resources such as new disks or storage arrays to your existing infrastructure. Ensure your backup solution is up-to-date before making any changes. If you don't have extra physical storage, consider utilizing storage features like Storage DRS (Distributed Resource Scheduler) or Storage I/O Control (SIOC) to balance the existing load across multiple datastores within a storage cluster.
Brooker Lv3Posted 08 Nov 2023 16:50
  
Before you do anything, make a backup of your data. To avoid losing any data during the split, the backup should be kept apart from the primary data storage.
Carrot Lv3Posted 08 Nov 2023 16:51
  
Select the method of splitting, build a new datastore with the required capacity, and transfer data from the old datastore to the new one.
Fisher Lv2Posted 08 Nov 2023 16:51
  
If you are utilizing LUNs, you might be able to establish a new one inside the current datastore and migrate data across
Racoon Lv2Posted 08 Nov 2023 16:52
  
decommissioning the previous datastore if you're satisfied that everything was correctly transferred
Robin Lv3Posted 08 Nov 2023 16:53
  
Ensure that your Cisco switch supports EtherChannel (or Link Aggregation Group). It's a common feature on Cisco switches, but it's essential to confirm.
sanjigerma Lv3Posted 08 Nov 2023 16:54
  
Before making any changes, ensure that you have a complete and verified backup of all the data on the 190 TB datastore. This is essential in case something goes wrong during the split.
Snipe Lv2Posted 08 Nov 2023 16:54
  
Analyze the existing data on the datastore and categorize it. Determine if there are specific data types or virtual machines that you want to move to a new datastore. This can help in planning the split.

I Can Help:

Change

Moderator on This Board

2
20
0

Started Topics

Followers

Follow

Board Leaders