Ncrancher

Ncrancher

This user hasn't shared any profile information

Posts by Ncrancher

Windows 2008 DFS & VSS EventID:8193

I’ve been running into issues with DFSR and VSS which causes Shadow Copy Components backups to fail because one of the VSS writers had disappeared:

The Environment:
2 x Windows 2008 Enterprise x64 Servers
Hardware: Blades
Memory: 16GB
Disk Space: C: 40Gb, D: 100GB
Services: DFSR, Citrix XenApp 5.0, Netbackup, Terminal Server.

The Issue: Netbackup had been failing with ERROR 71 (Path not found) when we tried to backup Shadow Copy Component and we also noticed EventID: 8192 errors in the applications log from VSS. It appeared that the Shadow Copy Optimization Writer had disappeared from the list of VSS writers and this is netbackup’s API dependency.  In this case I opened a case with a Microsoft to troubleshoot further.

EVENTID: 8193

Netbackup Error: 71

Resolution: We were replicating with DFSR the local profiles for the Citrix Xenapp environment so that documents saved would appear in both location on Server A and Server B. The trouble with this method is that DFSR leaves open handles and as a result temporary profiles are created. In some cases the profile ID is locked and another one created, which in return renames the original profile id with a .bak extension in the system registry. When these backup profile IDs are created the Shadow Copy Optimization writer disappears from the writer list. I’m still asking the question to Microsoft how the profilelist and VSS “Shadow Copy Optimization” are dependant on each other.

It is NOT recommend to use DFSR to replication local user profiles i.e. C:\users and I have since removed this replication group. You will need to delete the .bak profile IDs from the following path in the registry:

\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList

an example would be:  S-1-5-21-106000298-1275210071-1417001363-12345.bak

As with all system changes I would highly recommend exporting the keys or backing up the registry.

I’ve now decided to user Terminal Server user profiles with a path set to server A and this path is replicated to Server B using DFSR, with no further issues. For DR reasons the TS path  is actually a CNAME which I can change depending on server status and this was tested to work fine during fail-over.

Windows 2008 VSS and backup issues

I’m currently working on a project and have come across issues with VSS writers affecting netbackup and causing backups to fail.

The Environment:
2 x Windows 2008 Enterprise x64 Servers
Hardware: Blades
Memory: 16GB
Disk Space: C: 40Gb, D: 100GB
Services: DFSR, Citrix XenApp 5.0, Netbackup, Terminal Server.

VSS: We are snapshotting the volumes every 6 hours.
DFSR: We have been replicating user profiles and data from Server A to Server B.

The issue: We detected the problem when the backups of Shadow Copy Components started failling. After close investigation on Server A we found none of the VSS writers were listing. The VSS writers are used by Netbackup as API to backup replicated folders and the system state.

Application Logs Events:

Log Name:      Application
Source:           VSS
Date:              04/01/2010 01:51:17
Event ID:         12291
Task Category: None
Level:             Error
Keywords:      Classic
User:              N/A
Computer:      ServerA
Description:
Volume Shadow Copy Service error: Error on creating/using the COM+ Writers publisher interface: BackupShutdown [0x8000ffff].

Log Name:      Application
Source:           VSS
Date:              04/01/2010 01:51:18
Event ID:         12301
Task Category: None
Level:              Error
Keywords:      Classic
User:          N/A
Computer:      ServerA
Description:
Volume Shadow Copy Service error: Writer ASR Writer did not respond to a GatherWriterStatus call.

Operation:
Gather writers’ status
Executing Asynchronous Operation
Context:
Current State: GatherWriterStatus

Log Name:      Application
Source:           VSS
Date:              04/01/2010 01:51:18
Event ID:         12347
Task Category: None
Level:             Error
Keywords:      Classic
User:              N/A
Computer:      ServerA
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  The Registry Writer failed to respond to a query  from VSS. Please check to see that the Event Service and Volume Shadow Copy Service  are operating properly, and please check the Application event log for any other events.

Operation:
Gather writers’ status
Executing Asynchronous Operation
Context:
Current State: GatherWriterStatus

Resolution: In the system registry check that “eventcls.dll” has the path of %SystemDrive%\system32\evencls.dll. You may need to register the dll in the system if you are unable to find any listed. The path in this example was:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\EventClasses\{FAF53CC4D73-4E36-83F1-2B23F46E513…

If the path is found to be incorrect and has since been corrected you may need to restart the following services:

  1. COM+ Event Syste,
  2. Volume Shawdow Copy

These events plus EventID: 32 normally indicate that something is wrong in the system registry with the VSS DLL depenances.

For more information please look at the following technet article http://social.technet.microsoft.com/Forums/en/winservergen/thread/5ce377db-3c2e-454f-a003-ec51e80232ce

Please also read my blog on VSS Writer: Shadow Copy Optimization Writer disappearing.

ASUSTEK N13219 Graphics Driver

Have you ever found yourself searching thousands of pages looking for a driver and only end up at these software sites? Well I’m listing all the drivers I’ve ever needed here, please help yourself (FOR FREE).

Manufacture: ASUS
Mode: NEON
Other information: N13219, AS# 445682
This graphics card appears in device manager as: NVIDIA GeForce 8400GS
Link: http://www.whatevernetworks.com/drivers/asus_N13219.zip
Date added: 1st February 2010

Test Blog

RnJvbSBCbGFja2JlcnJ5DQpTZW50IGZyb20gbXkgQmxhY2tCZXJyea4gd2lyZWxlc3MgZGV2aWNl

Ncrancher's RSS Feed
Go to Top