Known Issue-Known Issue - Stuck at "Performing block level transfer"

Symptoms: 

Migration console output is stuck at "Performing block level transfer" stage.

Normally, the step takes from 30 mins to 6 hours depending on your disk size (for larger disk it takes longer).

 

Explanation: 

Current Cloudscraper version has this issue on some Windows versions.

On one of migration steps, Cloudscraper investigates Pagefile settings of your WIndows machine.

The primary reason of the investigation is to exclude temporary but space-consuming Pagefile data from the disk.

On some systems Cloudscraper exclusion algorithm hangs when Pagefile is too fragmented.

Diagnostics: 

Open "logs" directory inside of Cloudscraper installation dir. Locate "migrate.log" and open it.

Scroll till the end of the file.

There should be a mixture of Inserting piece \ Removed extent messages.

Its last rows should resemble this sample logs:

2016-04-20 17:39:47,071 Removing block [39961886720;39962656768)
2016-04-20 17:39:47,071 Inserting piece [39961886720;39962152960)
2016-04-20 17:39:47,071 Inserting piece [39962185728;39962656768)
2016-04-20 17:39:47,414 Removed extent [39962087424;39962120192)
2016-04-20 17:39:49,082 Removing block [39961886720;39962152960)
2016-04-20 17:39:49,082 Inserting piece [39961886720;39962087424)
2016-04-20 17:39:49,082 Inserting piece [39962120192;39962152960)
2016-04-20 17:39:49,348 Removed extent [39954370560;39954403328)
2016-04-20 17:39:50,565 Removing block [39954128896;39954411520)
2016-04-20 17:39:50,565 Inserting piece [39954128896;39954370560)
2016-04-20 17:39:50,565 Inserting piece [39954403328;39954411520)
2016-04-20 17:39:50,799 Removed extent [39953571840;39953604608)

2016-04-20 17:39:47,071 Removing block [39961886720;39962656768)
2016-04-20 17:39:47,071 Inserting piece [39961886720;39962152960)
2016-04-20 17:39:47,071 Inserting piece [39962185728;39962656768)
2016-04-20 17:39:47,414 Removed extent [39962087424;39962120192)
2016-04-20 17:39:49,082 Removing block [39961886720;39962152960)
2016-04-20 17:39:49,082 Inserting piece [39961886720;39962087424)
2016-04-20 17:39:49,082 Inserting piece [39962120192;39962152960)
2016-04-20 17:39:49,348 Removed extent [39954370560;39954403328)
2016-04-20 17:39:50,565 Removing block [39954128896;39954411520)
2016-04-20 17:39:50,565 Inserting piece [39954128896;39954370560)
2016-04-20 17:39:50,565 Inserting piece [39954403328;39954411520)
2016-04-20 17:39:50,799 Removed extent [39953571840;39953604608)
2016-04-20 17:39:47,071 Inserting piece [39961886720;39962152960)
2016-04-20 17:39:47,071 Inserting piece [39962185728;39962656768)
2016-04-20 17:39:47,414 Removed extent [39962087424;39962120192)
2016-04-20 17:39:49,082 Removing block [39961886720;39962152960)
2016-04-20 17:39:49,082 Inserting piece [39961886720;39962087424)
2016-04-20 17:39:49,082 Inserting piece [39962120192;39962152960)
2016-04-20 17:39:49,348 Removed extent [39954370560;39954403328)
2016-04-20 17:39:50,565 Removing block [39954128896;39954411520)
2016-04-20 17:39:50,565 Inserting piece [39954128896;39954370560)
2016-04-20 17:39:50,565 Inserting piece [39954403328;39954411520)
2016-04-20 17:39:50,799 Removed extent [39953571840;39953604608)
Solution: 

There is an undocumented option to ignore pagefile settings.

 

The pagefile workaround is the following.

1. Find transfer.ini you saved on initial migration.
2. Open it in Notepad and add the following row to the end of file

[Fixes]
pagefile=

3. Save it.
4. Open local utility at C:\Program Files\Migrate2iaas\Cloudscraper\Cloudscraper.exe
5. Choose "Resume Existing Transfer"
6. Browse to your ini file
7. Enter your secret AWS key
8. Click Next>
9. Start the migration