VCB and Windows 2000 - pre-freeze script doesn't work

[waldorfo2]

Hi,

I've been trying to configure Windows 2000 for use with VCB. I can do file level and full backups no problem. However when I tried to configure pre-freeze-script.bat and post-thaw-script.bat scripts it does not work!

Looks like those scripts are completely ignored and snapshot is taken immidietely. I tested it on Win XP and Windows 2003 VMs and it works fine.

I checked Windows logs and there were no entries from LGTO_Sync at all, so I thought that sync driver was disabled - but no, the driver was enabled.

Then I thoought that VMware Tools were looking for those scipts in c:\windows folder instead of c:\winnt - so I created the folder manually - didn't work.

I tried this on two Windows 2000 VMs so it's rather not a VM specific problem.

FYI: I'm using ESX 3.5 and VC 2.5 with latest patches as well as the latest build of VCB.

Anyone out there succesfully used those scripts with Windows 2000?

Thanks,

Wojtek

[dconvery]

The script needs to be in the \winnt directory. Also make sure you do a COMPLETE install of VMware tools, sometimes typical doesn't load everything.

[waldorfo2]

I tried c:\winnt directory as well - didn't work. I will try to reinstall VMtools. But the thing is that LGTO_Sync driver is installed and enabled. I thought that pre-freeze and post-thaw are executed by the driver, but I might be wrong.

[kix1979]

They are executed by the -quiesce option for the snapshot, which is also what would call the Legato sync driver. This option is automatically passed with VCB backups, and an option with normal snapshot operations. There is no GUI option for -quiesce as far as I have seen, you have to do it from the CLI or API.

Kix

[dconvery]

Double check %TEMP% on the guest. It should have a log there.

[dinny]

Hiya,

I do successfully use the pre and post VCB scripts on w2000

I found that I did have to create a c:\windows dir (as they appear to have hard coded that path as opposed to checking the env variable and using c:\winnt) - but once I created that dir and copied the two scripts in they run fine.

Only other thing I can add is that I created it in lowercase - and it and the two scripts within it, have perms for "everyone"

Maybe double check for typos in the script names - or anything in the pre and post scripts themselves that are perhaps specific to w2003?

Just logged on and checked the event viewer - sql svc was definitely stopped before, and started after, the legato sync quiescing when last nights backup ran.

Dinny

[waldorfo2]

Thanks everyone for your tips.

Unfortunately I still haven't solved the issue.

I tried to reinstall VMtools, enable/disable Sync Driver, double checked all filenames and permissions - and nothing!

It has to be something about the build of those VMs. Maybe I should try a fresh install.

Dinny: Could you please confirm which version of ESX and VCB are you using? Is it the latest build?

[kix1979]

Have you tried passing the quiesce option from the CLI when you create a snapshot? Also you might try a pre-freeze that does something simple like create a text file to make sure it works. If it doesn't run properly even with a CLI option, it is probably in the wrong directory. As far as I recall it should be C:\Windows

[dinny]

Hiya,

I'm currently on VCB 1.1, ESX 3.02 with Jan patches and VC 2.02 update 2.

But I've used it fine for the last year, from ESX 3.01 onwards, with various older versions of VCB and VC

I would agree with kix - definitely ensure the scripts work when run manually on those VMs - then at least you will know whether it's VCB related.

Also in older versions of VCB/ESX there was a timout (I think of 3 mins) - if the pre script hasn't actually completed in that time - the backup starts anyway.

That has now been patched - but I can't recall in which version?

Dinny

[dconvery]

Kix -

I thought the scripts would work as long as they are in the %PATH%?

Dave

[dinny]

I found that wasn't the case for me.

c:\winnt would be in the path by default on w2000 (have just checked and it definitely is on the VM that I tested on)

But I definitely had to create a "c:\windows" dir to contain the scripts, before they would work on w2000 - suspect some lazy coding somewhere

Dinny

[dconvery]

Good to know...Thanks Dinny!

Dave

[waldorfo2]

>>Have you tried passing the quiesce option from the CLI when you create a snapshot?

That's interesting. I thought that you can only disable quiescing by disabling SyncDriver.

Where do you specify that? (sorry but I don't have access do ESX at the moment) Is that vcbMounter option?

[depping]

for the cli the option is "-q 0"

Duncan

My virtualisation blog:

[timlane]

Dinny

Creating the folder C:\Windows and placing my scripts in that folder worked perfectly!!