waninae39 Posted March 29, 2012 Report Share Posted March 29, 2012 after the last set of MS xp patches and retrospect BU update to V 7.7.620 the BU starts up but never completes. regardless of whicd device is being backed up, it stops at the same point and never completes below is a sample of the log file showing where it hangs anyone have this problem? any ideas? i need a working solution soon + Normal backup using workshop-bu-sched at 28/03/2012 7:20 AM Progress 28/3/2,012 7:20:24: Preparing to execute... Progress 28/3/2,012 7:20:25: Updating Catalog File... Progress 28/3/2,012 7:20:25: Please wait... To Backup Set Workshop... 28/03/2012 7:20:26 AM: Connected to yy-pcxx * Resolved container yy-pcxx to 1 volumes: Local Disk (C:) on yy-pcxx Progress 28/3/2,012 7:20:35: Preparing for Open File Backup... T-5: VssWEnumWriterMetadata: Can't exclude writers on Windows XP, API call not supported T-7: Windows XP VSS Writer found: Microsoft Writer (Service State) T-7: Windows XP VSS Writer found: MSDEWriter T-7: Windows XP VSS Writer found: WMI Writer T-7: Windows XP VSS Writer found: Microsoft Writer (Bootable State) T-8: VssWGetDevice: volPath = \\?\Volume{a56a366c-a435-11dd-a79b-806d6172696f}\, devString = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1 - 28/03/2012 7:20:24 AM: Copying Local Disk (C:) on yy-pcxx Progress 28/3/2,012 7:20:51: Preparing to execute... lvtrNeedsChangeId: server volume = 0, needs change id = 0 lvtrRescan: avail - minstart = 858,993,456, minstart = 163,840, minmem = 98,304 T-21: VssWEnumWriterMetadata: Can't exclude writers on Windows XP, API call not supported Excluded 3,132 files, 7.5 G Exec::ExecCreateStateFolder: C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State... Progress 28/3/2,012 7:23:19: Please wait... Progress 28/3/2,012 7:23:20: Copying Local Disk (C:) on yy-pcxx... Progress 28/3/2,012 7:23:20: Copying Local Disk (C:) on yy-pcxx... Progress 28/3/2,012 7:23:32: Closing... Progress 28/3/2,012 7:23:34: Updating Catalog File... 28/03/2012 7:23 AM, extoBuildStateFiles: start save snapshot tree 28/03/2012 7:23 AM, extoBuildStateFiles: start write snapshot tree 28/03/2012 7:23 AM, extoBuildStateFiles: start building snapshot Progress 28/3/2,012 7:23:37: Building Snapshot... vtopBuildStateFiles: Beginning system state backup of root volume "C:\" vtopBuildStateFiles: system root volume, accessDbs = 1, dbflags = 452 vtopBuildStateFiles: Copying Windows XP Meta Information to the state folder. T-36: VssWStoreMetadata: Copying Meta Info for Writer: Microsoft Writer (Service State) T-36: Copying Meta Info for Component: Content Indexing Service T-36: VssWStoreMetadata: compName = Content Indexing Service, copying included files T-36: Copying Meta Info for Component: Config Directory T-36: VssWStoreMetadata: compName = Config Directory, copying included files T-36: Copying Meta Info for Component: Event Logs T-36: VssWStoreMetadata: compName = Event Logs, copying included files T-36: VssWStoreMetadata: Copying Meta Info for Writer: WMI Writer T-36: Copying Meta Info for Component: WMI T-36: VssWStoreMetadata: compName = WMI, copying included files T-36: VssWStoreMetadata: Copying Meta Info for Writer: Microsoft Writer (Bootable State) T-36: Copying Meta Info for Component: COM+ Registration Database T-36: VssWStoreMetadata: compName = COM+ Registration Database, copying included files T-36: Copying Meta Info for Component: Registry T-36: RegGetUserClassRegPath: common app data folder = C:\Documents and Settings\All Users.WINDOWS\Application Data T-36: RegGetUserClassRegPath: app data folder = Application Data T-36: RegGetUserClassRegPath: local app data folder = C:\Documents and Settings\wanina\Local Settings\Application Data T-36: RegGetUserClassRegPath: local settings folder = Local Settings T-36: VssWAddToFileList: srcPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Documents and Settings\All Users\NTUser.Dat, destPath = \MetaInfo\writer0002\comp0001\file0011 T-36: VssWCopyUserReg: couldn't copy All Users dummy registry key 'All Users', -1,101 T-36: VssWAddToFileList: srcPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1\Documents and Settings\Default User\NTUser.Dat, destPath = \MetaInfo\writer0002\comp0001\file0011 T-36: VssWStoreMetadata: compName = Registry, copying included files vtopGetWin2Db: saving windows 2000 db, id = 128 T-88: W2dbBackupStart: DsBackupPrepare successful! vtopGetSecurity: saving security vtopSaveCatalogMetadata: saving metadata information vtopSaveNTInfo: saving snapshot information 28/03/2012 7:26 AM, extoBuildStateFiles: start save Metadata 28/03/2012 7:26 AM, extoBuildStateFiles: start save snapfile 28/03/2012 7:26 AM, extoBeginOne: start TMatchRemove untagged nodes 28/03/2012 7:26 AM, extoBeginOne: start TMatchRemove matched nodes 28/03/2012 7:26 AM, extoBeginOne: start TTrim nodes 28/03/2012 7:26 AM, extoBeginOne: start TGC Progress 28/3/2,012 7:26:43: Copying Snapshot... lvtrRescan: avail - minstart = 858,993,456, minstart = 163,840, minmem = 98,304 Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 29, 2012 Report Share Posted March 29, 2012 The log just kinda ends. What about the remaining part of the log? What do you see on screen when this happens? Quote Link to comment Share on other sites More sharing options...
waninae39 Posted March 30, 2012 Author Report Share Posted March 30, 2012 hello that is the complete log. it stalll at the end of this log the screen shows a std prgress bar that never moves past about 40% it doesn't matter which device is backed up, they all stall at the same point in the log now ... Progress 28/3/2,012 7:26:43: Copying Snapshot... lvtrRescan: avail - minstart = 858,993,456, minstart = 163,840, minmem = 98,304 as you can see, it shows the BU running for 7.5 hrs. on the system for this BU, it normally completes in under 40 minutes any guidance? restrospect patch issue issue with the latestMS xp x64 drivers? Quote Link to comment Share on other sites More sharing options...
waninae39 Posted March 31, 2012 Author Report Share Posted March 31, 2012 here is another example from a differant machine running win7. the last example was an xp pro machine both halt at the same place in the process anyone else see this? what is the BU sw doing at this stage to cause it to halt? this BU halted after 20 min. this machine usually takes about 30 minutes to do a regular BU + Executing Immediate Backup at 31/03/2012 12:05 AM Progress 31/3/2,012 0:5:19: Preparing to execute... Progress 31/3/2,012 0:5:19: Updating Catalog File... Progress 31/3/2,012 0:5:19: Please wait... To Backup Set aa-bb-win7-pc... Progress 31/3/2,012 0:5:20: Preparing for Open File Backup... T-9: VssWEnumWriterMetadata: Excluding writer "Shadow Copy Optimization Writer" from the backup. T-11: Windows XP VSS Writer found: Task Scheduler Writer T-11: Windows XP VSS Writer found: VSS Metadata Store Writer T-11: Windows XP VSS Writer found: Performance Counters Writer T-11: Windows XP VSS Writer found: ASR Writer T-11: Windows XP VSS Writer found: IIS Config Writer T-11: Windows XP VSS Writer found: IIS Metabase Writer T-11: Windows XP VSS Writer found: WMI Writer T-11: Windows XP VSS Writer found: COM+ REGDB Writer T-11: Windows XP VSS Writer found: MSSearch Service Writer T-11: Windows XP VSS Writer found: Registry Writer T-16: VssWGetDevice: volPath = \\?\Volume{9ea1caf8-d4ae-11e0-b432-806e6f6e6963}\, devString = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 T-16: VssWGetDevice: volPath = \\?\Volume{9ea1caf9-d4ae-11e0-b432-806e6f6e6963}\, devString = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy21 T-16: VssWGetDevice: volPath = \\?\Volume{9ea1cafa-d4ae-11e0-b432-806e6f6e6963}\, devString = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy22 - 31/03/2012 12:05:19 AM: Copying MAIN (C:) on aa-bb-win7-pc Progress 31/3/2,012 0:5:37: Preparing to execute... lvtrNeedsChangeId: server volume = 0, needs change id = 0 lvtrRescan: avail - minstart = 858,993,456, minstart = 163,840, minmem = 98,304 T-27: VssWEnumWriterMetadata: Excluding writer "Shadow Copy Optimization Writer" from the backup. Excluded 173 files, 7.1 G Exec::ExecCreateStateFolder: C:\Documents and Settings\All Users\Application Data\Retrospect\RtrExec.dir\Exec\State... Progress 31/3/2,012 0:7:34: Please wait... Progress 31/3/2,012 0:7:35: Copying MAIN (C:) on aa-bb-win7-pc... Progress 31/3/2,012 0:7:35: Copying MAIN (C:) on aa-bb-win7-pc... Progress 31/3/2,012 0:8:10: Writing index... Progress 31/3/2,012 0:8:10: Writing index... Progress 31/3/2,012 0:8:10: Please wait... Progress 31/3/2,012 0:8:11: Copying MAIN (C:) on aa-bb-win7-pc... Progress 31/3/2,012 0:8:45: Writing index... Progress 31/3/2,012 0:8:45: Writing index... Progress 31/3/2,012 0:8:45: Please wait... Progress 31/3/2,012 0:8:46: Copying MAIN (C:) on aa-bb-win7-pc... Progress 31/3/2,012 0:8:58: Closing... Progress 31/3/2,012 0:9:0: Updating Catalog File... 31/03/2012 12:09 AM, extoBuildStateFiles: start save snapshot tree 31/03/2012 12:09 AM, extoBuildStateFiles: start write snapshot tree 31/03/2012 12:09 AM, extoBuildStateFiles: start building snapshot Progress 31/3/2,012 0:9:13: Building Snapshot... vtopBuildStateFiles: Beginning system state backup of root volume "C:\" vtopBuildStateFiles: system root volume, accessDbs = 1, dbflags = 452 vtopBuildStateFiles: Copying Windows XP Meta Information to the state folder. T-42: VssWStoreMetadata: Copying Meta Info for Writer: Task Scheduler Writer T-42: Copying Meta Info for Component: TasksStore T-42: VssWStoreMetadata: compName = TasksStore, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: VSS Metadata Store Writer T-42: Copying Meta Info for Component: WriterMetadataStore T-42: VssWStoreMetadata: compName = WriterMetadataStore, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: Performance Counters Writer T-42: Copying Meta Info for Component: PerformanceCounters T-42: VssWStoreMetadata: compName = PerformanceCounters, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: ASR Writer T-42: Copying Meta Info for Component: ASR T-42: VssWStoreMetadata: compName = ASR, copying included files T-42: Copying Meta Info for Component: Volume{9ea1caf8-d4ae-11e0-b432-806e6f6e6963} T-42: VssWStoreMetadata: compName = Volume{9ea1caf8-d4ae-11e0-b432-806e6f6e6963}, copying included files T-42: Copying Meta Info for Component: Volume{9ea1cafa-d4ae-11e0-b432-806e6f6e6963} T-42: VssWStoreMetadata: compName = Volume{9ea1cafa-d4ae-11e0-b432-806e6f6e6963}, copying included files T-42: Copying Meta Info for Component: Volume{9ea1caf9-d4ae-11e0-b432-806e6f6e6963} T-42: VssWStoreMetadata: compName = Volume{9ea1caf9-d4ae-11e0-b432-806e6f6e6963}, copying included files T-42: Copying Meta Info for Component: harddisk0 T-42: VssWStoreMetadata: compName = harddisk0, copying included files T-42: Copying Meta Info for Component: BCD T-42: VssWStoreMetadata: compName = BCD, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: IIS Config Writer T-42: Copying Meta Info for Component: IISCONFIG T-42: VssWStoreMetadata: compName = IISCONFIG, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: IIS Metabase Writer T-42: Copying Meta Info for Component: IISMETABASE T-42: VssWStoreMetadata: compName = IISMETABASE, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: WMI Writer T-42: Copying Meta Info for Component: WMI T-42: VssWStoreMetadata: compName = WMI, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: COM+ REGDB Writer T-42: Copying Meta Info for Component: COM+ REGDB T-42: VssWStoreMetadata: compName = COM+ REGDB, copying included files T-42: VssWStoreMetadata: Copying Meta Info for Writer: MSSearch Service Writer T-42: VssWStoreMetadata: Copying Meta Info for Writer: Registry Writer T-42: Copying Meta Info for Component: Registry T-42: RegGetUserClassRegPath: common app data folder = C:\ProgramData T-42: RegGetUserClassRegPath: app data folder = ProgramData T-42: RegGetUserClassRegPath: local app data folder = C:\Windows\System32\config\systemprofile\AppData\Local T-42: RegGetUserClassRegPath: local settings folder = AppData T-42: VssWAddToFileList: srcPath = \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20\Users\All Users\NTUser.Dat, destPath = \MetaInfo\writer0009\comp0000\file0005 T-42: VssWCopyUserReg: couldn't copy All Users dummy registry key 'All Users', -1,101 T-42: VssWStoreMetadata: compName = Registry, copying included files vtopGetWin2Db: saving windows 2000 db, id = 128 T-248: W2dbBackupStart: DsBackupPrepare successful! vtopGetSecurity: saving security vtopSaveCatalogMetadata: saving metadata information vtopSaveNTInfo: saving snapshot information 31/03/2012 12:22 AM, extoBuildStateFiles: start save Metadata 31/03/2012 12:22 AM, extoBuildStateFiles: start save snapfile 31/03/2012 12:22 AM, extoBeginOne: start TMatchRemove untagged nodes 31/03/2012 12:22 AM, extoBeginOne: start TMatchRemove matched nodes 31/03/2012 12:22 AM, extoBeginOne: start TTrim nodes 31/03/2012 12:22 AM, extoBeginOne: start TGC Progress 31/3/2,012 0:22:43: Copying Snapshot... lvtrRescan: avail - minstart = 858,993,456, minstart = 163,840, minmem = 98,304 Quote Link to comment Share on other sites More sharing options...
bobbodavis Posted April 20, 2012 Report Share Posted April 20, 2012 We have problems like this all the time - what version are the clients running - make sure they're up to 7.7.114. It may also be firewall related, whenever you upgrade, the Windows firewall rules may not work - it says something to this effect in the whitepaper. You can try running the firewall reset application on the client and/or server: client x64 location: C:\Program Files (x86)\Retrospect\Retrospect Client\retfwset.exe client x86 location: C:\Program Files\Retrospect\Retrospect Client\retfwset.exe server x64 or x86 location: C:\Program Files\Retrospect\Retrospect 7.7\retfwset.exe Usually though, I've found it easiest to just reload the client altogehter. This entails removing the application from control panel / add/remove programs Then check for any left over "retrospect data" in these locations and delete them C:\ProgramData\Retrospect Client C:\Program Files (x86)\Retrospect C:\Program Files\Retrospect C:\Documents and Settings\All Users\Application Data\Retrospect Client Might not hurt to download and run CCLeaner (free reg cleanup tool) afterwards too, just to make sure there are no lurking REG keys left behind. Once you're sure that all of these directories have been deleted from the client (after removing the application from control panel add/remove programs), reboot the client and perform a fresh client install with 7.7.114. I imagine this is going to suck if every single one of your clients is doing the same thing. We get random client problems here and there and the only way they ever seem to truly get fixed is to remove the client, deep clean it for any traces of Retrospect, reboot and reinstall. Good luck! One other thing to note. Retrospect does not automatially remove the "old" client that you just removed from the computer. You have to manually remove it from Configure / Clients in the left side panel options. If you don't and you accidentally point your backup script and/or backup set to the old client instead of the new one (once you've rejoined the client to the server), you'll still get the error -530 backup client not found, because of course, it won't actually exist since you're still pointing them to the client that was previously removed. Quote Link to comment Share on other sites More sharing options...
aesmith Posted May 4, 2012 Report Share Posted May 4, 2012 This hotfix for MS worked for my Win7 clients that where getting the stall at the initializing open file backup. http://support.microsoft.com/kb/2548124 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.