Storage Migration Service experience

%3CLINGO-SUB%20id%3D%22lingo-sub-1558865%22%20slang%3D%22en-US%22%3EStorage%20Migration%20Service%20experience%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1558865%22%20slang%3D%22en-US%22%3E%3CP%3EI%20decided%20to%20give%20the%20storage%20migration%20service%20a%20try%20but%20I'm%20going%20to%20end%20up%20abandoning%20it%20and%20going%20back%20to%20robocopy%20because%20it%20kind%20of%20sucks%2C%20is%20a%20pain%20to%20use%20and%20doesnt%20have%20the%20features%20I%20ended%20up%20needing.%26nbsp%3B%20I%20wanted%20to%20list%20some%20of%20those%20pain%20points%20so%20maybe%20you%20could%20take%20them%20into%20account%20in%20future%20releases.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3E%3CSTRONG%3EPerformance%20sucks%3C%2FSTRONG%3E%20The%20source%20server%20i%20was%20using%20had%201.5%20TB%20of%20data%20and%20it%20took%205%20hours%20to%20inventory.%26nbsp%3B%20Blindly%20robocopying%20all%20the%20data%20takes%20half%20the%20time.%26nbsp%3B%20I%20didnt%20even%20get%20to%20the%20actual%20copy%20phase%2C%20so%20I%20dont%20even%20know%20how%20bad%20that%20would%20have%20been.%26nbsp%3B%20The%20source%20server%20hardware%20sucks%2C%20so%20thats%20a%20good%20part%20of%20why%20things%20are%20slow%2C%20but%20its%20not%20as%20fast%20as%20just%20using%20robocopy.%3C%2FLI%3E%3CLI%3E%3CSTRONG%3EWorthless%20error%20messages%26nbsp%3B%3C%2FSTRONG%3EAfter%20the%20inventory%20was%20complete%2C%20there%20were%20some%20shares%20with%20the%20error%20%22Couldn't%20inventory%20some%20devices%22.%26nbsp%3B%20Thats%20beyond%20useless%20and%20makes%20no%20sense%20in%20the%20context.%26nbsp%3B%20What%20is%20the%20%22device%22%20being%20inventoried%3F%26nbsp%3B%20It%20couldnt%20have%20been%20the%20disk%20because%20all%20these%20shares%2C%20some%20of%20which%20inventoried%20fine%2C%20are%20on%20the%20same%20disk.%26nbsp%3B%20Did%20you%20mean%20some%26nbsp%3B%3CEM%3Efiles%3C%2FEM%3E%20couldnt%20be%20inventoried%3F%26nbsp%3B%20That%20would%20make%20sense%20but%20then%20i'd%20also%20expect%20a%20list%20of%20failed%20files%20that%20I%20could%20look%20over%20to%20either%20remediate%20or%20ignore%20the%20issue.%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CSTRONG%3ECant%20select%20source%20files%26nbsp%3B%3C%2FSTRONG%3EFor%20some%20reason%20I'm%20forced%20to%20inventory%20all%20shares%20on%20a%20given%20disk.%26nbsp%3B%20This%20wastes%20time%20since%20I'm%20only%20interested%20in%20a%20specific%20share%2Ffolder.%26nbsp%3B%20Additionally%2C%20some%20of%20the%20shares%20on%20this%20source%20server%20are%20sub%20shares%20of%20other%20shares%20which%20leads%20to%20the%20inventory%20process%20scanning%20the%20same%20content%20multiple%20times.%26nbsp%3B%20Further%20decreasing%20performance.%26nbsp%3B%20You%20should%20both%20allow%20the%20selection%20of%20individual%20shares%2C%20or%20better%20yet%2C%20individual%20folders%20AND%20make%20sure%20the%20service%20is%20smart%20enough%20to%20not%20duplicate%20inventory.%26nbsp%3B%20I%20think%20the%20idea%20of%20using%20shares%20as%20the%20inventory%20source%20instead%20of%20disk%20content%20is%20a%20mistake.%26nbsp%3B%20Instead%20of%20inventorying%20shares%20you%20should%20inventory%20disk%20content%20and%20then%20flag%20what%20parts%20of%20that%20content%20are%20shared.%26nbsp%3B%20Additionally%20when%20adding%20a%20source%20server%2C%20the%20next%20step%20should%20be%20selecting%20which%20folders%20on%20the%20disk%20you%20want%20to%20inventory.%26nbsp%3B%20Default%20can%20be%20everything%2C%20with%20the%20option%20of%20a%20standard%20folder%20hierarchy%20from%20which%20you%20can%20select%20individual%20folders%2Fsubfolders.%26nbsp%3B%3C%2FLI%3E%3CLI%3E%3CSTRONG%3ECant%20map%20destination%20folders%26nbsp%3B%3C%2FSTRONG%3EI%20wanted%20to%20map%20the%20source%20folder%20to%20a%20different%20destination%20folder%2C%20and%20there%20doesnt%20appear%20to%20by%20any%20way%20to%20do%20this.%26nbsp%3B%20Instead%20it%20looks%20like%20its%20just%20going%20to%20create%20the%20same%20folder.%26nbsp%3B%20This%20is%20where%20I%20gave%20up%20because%20it%20turns%20out%20this%20just%20wont%20do%20what%20I%20need.%26nbsp%3B%26nbsp%3B%3C%2FLI%3E%3C%2FOL%3E%3CP%3EI%20think%20you%20need%20to%20go%20back%20to%20the%20drawing%20board%20on%20this%20one.%26nbsp%3B%20Maybe%20look%20at%20robocopy%20and%20use%20it%20as%20the%20design%20basis.%26nbsp%3B%20I%20was%20kind%20of%20excited%20when%20I%20read%20the%20docs%20on%20storage%20migration%20service%2C%20but%20the%20reality%20is%20its%20not%20as%20flexible%20or%20functional%20as%20I%20need.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Senior Member

I decided to give the storage migration service a try but I'm going to end up abandoning it and going back to robocopy because it kind of sucks, is a pain to use and doesnt have the features I ended up needing.  I wanted to list some of those pain points so maybe you could take them into account in future releases.

 

  1. Performance sucks The source server i was using had 1.5 TB of data and it took 5 hours to inventory.  Blindly robocopying all the data takes half the time.  I didnt even get to the actual copy phase, so I dont even know how bad that would have been.  The source server hardware sucks, so thats a good part of why things are slow, but its not as fast as just using robocopy.
  2. Worthless error messages After the inventory was complete, there were some shares with the error "Couldn't inventory some devices".  Thats beyond useless and makes no sense in the context.  What is the "device" being inventoried?  It couldnt have been the disk because all these shares, some of which inventoried fine, are on the same disk.  Did you mean some files couldnt be inventoried?  That would make sense but then i'd also expect a list of failed files that I could look over to either remediate or ignore the issue.  
  3. Cant select source files For some reason I'm forced to inventory all shares on a given disk.  This wastes time since I'm only interested in a specific share/folder.  Additionally, some of the shares on this source server are sub shares of other shares which leads to the inventory process scanning the same content multiple times.  Further decreasing performance.  You should both allow the selection of individual shares, or better yet, individual folders AND make sure the service is smart enough to not duplicate inventory.  I think the idea of using shares as the inventory source instead of disk content is a mistake.  Instead of inventorying shares you should inventory disk content and then flag what parts of that content are shared.  Additionally when adding a source server, the next step should be selecting which folders on the disk you want to inventory.  Default can be everything, with the option of a standard folder hierarchy from which you can select individual folders/subfolders. 
  4. Cant map destination folders I wanted to map the source folder to a different destination folder, and there doesnt appear to by any way to do this.  Instead it looks like its just going to create the same folder.  This is where I gave up because it turns out this just wont do what I need.  

I think you need to go back to the drawing board on this one.  Maybe look at robocopy and use it as the design basis.  I was kind of excited when I read the docs on storage migration service, but the reality is its not as flexible or functional as I need.  

0 Replies