We are backing up Systemstate on all Windows servers because of using TBMR for restoring system images in case of system crash. Sometimes it is painful due to big number of files, problems with VSS, etc. Problems with VSS are resolved by installing hot fixes or involving MS support.
Grigori Solonovitch, Senior Systems Architect, IT, Ahli United Bank Kuwait, www.ahliunited.com.kw -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Zoltan Forray Sent: 09 01 2014 9:12 PM To: [email protected] 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 [email protected] - 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 Please consider the environment before printing this Email. ________________________________ CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
