DataKeeper for Windows All Documentation - SIOS

Counter Logs Do Not Work on Windows 2003Counter Logs Do Not Work on Windows 2003Performance Monitor - Counter Logs Do Not Work on Windows 2003Error/MessagePerformance Monitor counter logs do not work on Windows 2003. This problem will be resolved in afuture release of the SteelEye DataKeeper for Windows product.Suggested ActionOpen the Services MMC snap-in and change the log on account for the "Performance Logs and Alerts"(SysmonLog) service to "Local System Account".To reset the "Performance Logs and Alerts" (SysmonLog) service account to the original account,change the log on account back to "NT Authority/Network Service" specifying no password.Failed to Create MirrorUser Interface - Failed to Create Mirror - Application Event LogError/MessageLogged in the Application Event Log:File: .\GuiThread.cpp Line: 3099 Attempt to connect to remote system REMOTESERVER failed witherror 5. Please ensure that the local security policy for "Network Access: Let Everyone permissionsapply to anonymous users" is enabled on all the servers running DataKeeper.Check: Local security policy setting on the specified system.DescriptionFailed to create the mirror. Mirror is created but not stored in the job.Suggested ActionMake local security policy change, open command prompt and run "%EXTMIRRBASE %\emcmd.deletemirror ", then perform the mirror creation action again.MaxResyncPasses ValueIf, during a volume resynchronization, the number of passes made through the intent log exceeds theMaxResyncPasses registry value (200 by default), SteelEye DataKeeper logs a message to the Event Logindicating that the resync process is taking too many passes and requests that the administrator stopwhatever process is writing to the drive being resynchronized. The mirror then goes to the Paused state. Youcan increase the MaxResyncPasses value from the registry to give the resync process more time.DataKeeper for Windows Technical DocumentationPage 164