Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Symantec Ghost Multicast Freeze/Pause when Restoring

Created: 03 Oct 2013 | 3 comments

Hi,
I seems to have a weird issue when performing symantec ghost cloning; during the clone restore process, the restore would pause/stop for a few mins which seem like the multicast cloning has failed; however after a few minutes; it resumes again. On the network switches; I could see igmp reports/query with the client however the restore does not continue. Occasionally, it would pause/stop indefinitely and I would need to restart the cloning again.

I would like to ask what may be the possible reasons for it especially the pause in ghost cloning? I have check the ghost server cpu/memory utilization as well as network switches and it seems they are working fine within 20-30% utilization. The ghost is setup for pim spare mode on the network. Not too sure if it may be a network or ghost issue.

Any suggestions is appreciated.

Operating Systems:

Comments 3 CommentsJump to latest comment

EdT's picture

You mention IGMP but have not confirmed whether IGMP snooping is enabled on the switches. It needs to be enabled if you want multicasting to work.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.

cwtang's picture

Hi,

The switches used are Cisco and igmp snooping is enabled. PIM-SM has also been enabled. Multicast ghosting can succeed however sometime it pause/stops for sometime and continue/sometimes it stops/pause indefintely while other times the multicast ghosting complete successfully without any pause. Not too sure if it may be a network or ghost issue. Are there any areas I can look out for?

Any suggestions is appreciated.

EdT's picture

Probably the simplest way to proceed would be to monitor the network traffic with something like wireshark and check whether there is any unusual activity at the point where Ghost pauses.  Are there any connected machines that are hibernated or otherwise not fully active?  It is not unheard of for powered down NICS to do odd things on the network.  I'm assuming you are on a production network with other clients present and not a dedicated imaging network with no other machines connected.

If your issue has been solved, please use the "Mark as Solution" link on the most relevant thread.