Aller au contenu principal

Deployment Spped Using Snap Deploy 4

Thread needs solution

On recommendation of the Acronis support rep I purchased a single use license of Snap Deploy 4 to move a system from a 160GB drive to a 1TB drive. I created the disc as instructed and saved an image to another network computer in my home office. That went well and the image of my disk was created in about an hour.

I removed the existing drive and physically installed the new one. I booted from the Snap Deploy disc and instructed it to do a stand alone deployment. I selected the image previously saved and it began running.

The speed at which the image is being transferred to the new drive is very slow. Describing it as "glacial" would be kind. As I write this the deployment has been running for a little over 6 hours and the progress indicator claims there are 7 hours remaining. The progress indicator has been claiming 7 hours remaining for the past few hours.

Is this normal for it to take so long? In all honesty it would have been faster to reinstall Windows 7, reload my applications, and restore the data.

All equipment in the network of 4 computers is 10/100/1G. Looking from another machine there is very little network traffic, perhaps 5 MBs (MegaBYTES).

0 Users found this helpful

Look this over and see if it helps:

http://www.deploystudio.com/Forums/viewtopic.php?id=2083

The idea of multicast is not to race out the gate at maximum speed but to get to a secure cruise speed with as many machines at the same time as my network can host... View this as a 4 lane freeway vs. a 200 lanes highway. Freeway in concept looks faster but could get congested pretty seriously and highways (200 lanes doesn't really exist..LOL!) but will get a lot more people to destination at once and if we need to add more lanes there will be no impact on the overall time.

Sometimes for small files Unicast will do a better job than Multicast. For large files and many machines, multicast is the winner.

There are several technologies involve in both scenarios (Uni vs Multi) and they cannot be compared at all.

Unicast load and performance is driven by:

1- The network protocol being used like AFP, SMB or NFS. Whatever you are using the load is on the CPU of that server.
2- The NIC (Network Interface Card) on the server and on the client machines

Each client request the file and the speed is adjusted to whatever bandwidth is available in real time. It goes up and down all the time and can go to a halt if the number of requests exceed any of the above capacities. Of course it will slow down if the hard disks cannot sustain the initial rate. As more machines request a file , everybody slow down. You may be able to reach 65 to 100MBps with a single or few machines but this will drastically slow down if you do 20 and more.

That in a nutshell is pretty much it for Unicast.

Multicast in the other hand is driven by:

1- The Switch CPU capacity to copy and synchronize the packets among all the ports on the vlan.

The server will blindly transmit at the determined speed in DeployStudio assistant to the switch. Client machines will join the broadcast where ever it is in the process and start form there. There is little to no feedback provided to the server as to the status of the client. If a client drops too many packets a failed alert will be sent to the broadcasting server and depending on the status will either retry or totally fail and hang/crash/reboot.

TTL is the number of hup (switches/vlan) that the stream can traverse to reach it's final destination. You cannot set it to 0. Leave this to 3 unless you know for sure you have more.

On a good Gigabit network , secure stream speed will be around 15 MB and disk write 45MB. And of course on a 100Mbps well, you divide those by 10. There is no magic that can be done and these values are guidelines only. Your mileage will vary.

Hope this help you understand the differences.

-TP