Zoltan, Yes, we back up the SS, and have dealt with all the issues associated with capturing them.
As has been discussed here countless times, with 2k3 most of the issues were addressed by applying the hotfix rollup. With 2008 I have been confronted with several occasions where machines having the issue you describe below of the sys writer disappearing (and instability of other writers). In every case I can remember it was always permissions related. Most cases it was our IT Security staff restricting the Network Service and/or System account. It doesn't matter how many times I talk to them sooner or later it happens again. Of course I discovered this after beating my head against the wall for days on end trying to resolve it! -Rick Adamson -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Zoltan Forray Sent: Thursday, January 09, 2014 1:12 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] POLL: Backing up Windows Systemstate A question about backing up systemstate, which seems to give us numerous headaches. Do you backup systemsstate on your Windows servers and WHY? My Windows folks constantly contact me about errors backup up and getting failures related to the systemstate files/process or VSS. For example, today's headache is a 2008 box failing with *"System Writers 'system writer' do not exist * and yes, doing a "vssadmin list writers" does not list "system writers". They have been fighting this since November, with no solution to fixing this problem. All hits/suggested solutions from Google searches have been tried, to no avail. I don't thing the server owners are willing to do a complete rebuild. The simple solution would be to NOT backups systemstate. For a simple 2008 server, what do we lose by not backing up systemstate? -- *Zoltan Forray* TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
