So this time, i was little occupied with some issue related to file services where i was running out of space on a SAN volume. After troubleshoot a lot, i found some useful info about DeDuplication problems. So i am going to explain each and every stuff about his issue. Might be it can help you in your environment if in case you run in to the same problem.
Information about Servers and Folder :
I have two server FS01 and FS02.
Each server has 3 SAN Volumes. (E.g. Users, Public, Work)
Three DFS Namespaces \mydoamin.net\Users\India, \mydoamin.net\Users\Public and \mydoamin.net\Users\Work
Deduplication is enabled on all three volumes.
All users hits FS02 to access Public drive, FS01 Public is just for backup.
All users hits FS02 to access Public drive, FS01 Public is just for backup.
Issue:
There was some issue with FS02 for which we had to reboot the server, when it came back to live it took some time to rebuild the dfs database and made the connections with FS01 to start the replication. It successfully rebuild the dfs database but able to make the connection with Users and Work DFSN. It failed in making the connection with Public DFSN on FS01 because somehow FS01 Public Volume ran out of space. When i checked the backlog counts from FS01 to FS02, it was huge but when i checked vice-versa there was no backlogs. It meant that FS01 has a perfect connection with FS02.
Solution :
Public Volume on FS01 size is 500GB out of which only 500MB was left. As per the DFS Events and DeDuplication Events, all things were on hold. Like DFS Replication Service stopped replication data between FS01 and FS02 due to out of space issue. DeDuplication service also was on hold due to insufficient space.
To check DFS Replication events, Navigate to :
Start > Computer (Right Click) > Manage
System Tools > Event Viewer > Applications and services logs > DFS Replication
To check DeDuplication Logs :
System Tools > Event Viewer > Applications and services logs > Microsoft > Windows > Deduplication
So here, we have upto date copy of Public Drive on FS02. To start replication and deduplication again i had to make some space on Public Volume of FS01 so start deduplication first as per the below mentioned command.
Start-DedupJob –Volume "Drive Letter:" –Type Optimization
But it didn't help much, it just made 2GB data on the volume.
Then i used a freeware TreeSize to check about actual space consumption on this volume of both servers (FS01 and FS02. So here was the surprise, Data on volume of both servers was same but there was a huge difference in the size of "System Volume Information". See the attached screenshot of Public Volume of FS01.
After dig more into it, i found some problem with its Garbage Collection data. So i ran below mentioned command and it all made the space for which i was looking for.
Start-DedupJob –Volume "Drive Letter:" –Type GarbageCollection
So it is very important to schedule your deduplication tasks in a way that they work fine every time. If they stop/disable/malfunction somehow, then you should know where you need to troubleshoot, it can really create a good mess with your storage and stop replication too if in case it runs out of space.
Public Volume on FS01 size is 500GB out of which only 500MB was left. As per the DFS Events and DeDuplication Events, all things were on hold. Like DFS Replication Service stopped replication data between FS01 and FS02 due to out of space issue. DeDuplication service also was on hold due to insufficient space.
To check DFS Replication events, Navigate to :
Start > Computer (Right Click) > Manage
System Tools > Event Viewer > Applications and services logs > DFS Replication
To check DeDuplication Logs :
System Tools > Event Viewer > Applications and services logs > Microsoft > Windows > Deduplication
So here, we have upto date copy of Public Drive on FS02. To start replication and deduplication again i had to make some space on Public Volume of FS01 so start deduplication first as per the below mentioned command.
Start-DedupJob –Volume "Drive Letter:" –Type Optimization
But it didn't help much, it just made 2GB data on the volume.
Then i used a freeware TreeSize to check about actual space consumption on this volume of both servers (FS01 and FS02. So here was the surprise, Data on volume of both servers was same but there was a huge difference in the size of "System Volume Information". See the attached screenshot of Public Volume of FS01.
After dig more into it, i found some problem with its Garbage Collection data. So i ran below mentioned command and it all made the space for which i was looking for.
Start-DedupJob –Volume "Drive Letter:" –Type GarbageCollection
So it is very important to schedule your deduplication tasks in a way that they work fine every time. If they stop/disable/malfunction somehow, then you should know where you need to troubleshoot, it can really create a good mess with your storage and stop replication too if in case it runs out of space.
0 comments:
Post a Comment