angel.isakov@siemens.com wrote: On 2:30 start Snapshot cript and finish at 3:30, but snapshot script run if i reboot serverB.

not sure what you mean ?  Snapshot script does not work unless you reboot the server (after the clone job finishes) ?  What are you using to mount/unmount clone/snapshots ? admsnap ?

Yes,

"Snapshot script does not work unless you reboot the server (after the clone job finishes)"

I use admsnap to flush/mount/unmount.

so at 12:00 you create clone and mount it on serverB, at 2:00 you unmount this clone. At 2:30 you create a snapshot and attempt to mount it on serverB and that's when it fails ? What happens exactly ? admsnap fails..you never see the drive show up in Disk Management ?

Yes,

I just never see drive in Disk Management.

Server OS is Windows 2008 64 bit FC Adapters is Emulex 8Gbps.

I tried with 2 Virtula mashines on Vmware yestarday-the same error when i use admsnap  activate -s SnapBU -d G:

"Scanning for new devices.

User specified drive letter G:

Activated session SnapBU on device \\.\PhysicalDrive3.

Warning: 0xF80B000D (The user specified a drive letter was not assigned to any activated devices)"

When i reboot serverB Snap work fine, but after snap script finish his work i have to reboot serverB again to work Clone script next time.

what if you reverse the order, clone first and then snapshot. You are using admsnap to deactivate snapshots and clones ?

I've tried to reverse order of clone and snap-the same result.

After reboot host, run only first script that i've started.

I've wrote bat file to reboot host and work fine for now, but..i dont wanna to reboot host between every job.

I've wrote bat to rescan bus(on emulex), but result is the same.

The problem is on Windows i think,because this is the same LUN-one from Clone Script, one from Snap Script.

I've never test this on Linux.

are you running this process on physical servers or virtual ?

On both.

Production- Physical-HP Blades.

Test- Virtual on Vmware.

try this, after you are done with your clone clone and it has been removed from the system. ..create snapshot manually (do not use admsnap) and present it to the storage group on serverB. Go into Disk Management and rescan, if the drive appears, run the same chkdsk command i told you about in the other thread.

Tried, but after rescan drive didn't appears.

After restart server drive is up and running.

I will try this with Windows 2003 next week if i have a time.

Thank you.