Mombu the Microsoft Forum

Go Back   Mombu the Microsoft Forum > Microsoft > SYSTEMS MANAGEMENT SERVER (TECHNET) > USMT (ScanstateLoadstate) problems with large mounts of data
User Name
Password
REGISTER NOW! Mark Forums Read




Reply
1 13th August 16:37
gary
External User
 
Posts: 1
Default USMT (ScanstateLoadstate) problems with large mounts of data



Hi, does anyone know if there is a limit to the amount of data that
USMT(Scanstate/Loadstate) can consistently handle. We are experiencing
irregularities and instability with USMT (Scanstate/Loadstate)when we
migrate data larger than 2 GB's. Sometimes they will scan and load
fine. It seems that the larger the amount of data being migrated the
more risk there is of loadstate failing. Is there a metric for working
out migration volumes so that we get a totally reliable reult. Some
clients have 40Gb's in their Documents and Settings folders.

Any help or advice will be greatly appreciated.

Thanks
Gary
  Reply With Quote


 


2 15th August 15:24
daniele bona
External User
 
Posts: 1
Default USMT (ScanstateLoadstate) problems with large mounts of data



we migrated on average 10 gb per user...the only problem was with too long
file names (more than 255 and symbolics).
pay attention to this.

did you see the log ? What does it says ? (scanstate.log , loadstate.log).

Please, put full logging on.
Did you try putting off compression ?

You could consider writing one scripts that first make .zip the folder you
want to migrate.

Daniele


"Gary" <garyf@softsource.co.za> ha scritto nel messaggio
news:1123676753.422684.39380@f14g2000cwb.googlegro ups.com...
  Reply With Quote


 


Reply


Thread Tools
Display Modes




666