Hi all,
The Windows backup utility in Windows 2008 and later is different than
ntbackup, and behaves more closely to TSM. It is likely that if VSS is
causing problems for TSM, it will also do the same for the Windows backup
tool. It needs to enumerate the available VSS writers and the files that
belong to those writers; if that functionality is not working for TSM it
probably won't work for the Windows tool as well.
Regards,
- Andy
____________________________________________________________________________
Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead |
storman AT us.ibm DOT com
IBM Tivoli Storage Manager links:
Product support:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager
Online documentation:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli
+Documentation+Central/page/Tivoli+Storage+Manager
Product Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli
+Storage+Manager/page/Home
"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 2014-07-30
11:56:46:
> From: "Prather, Wanda" <Wanda.Prather AT ICFI DOT COM>
> To: ADSM-L AT vm.marist DOT edu
> Date: 2014-07-30 11:57
> Subject: Re: Backing up systemstate with something besides VSS
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Yup.
> I haven't had this problem with Win2K8 yet, but had it all the time on
Win2K3.
> And we do exactly as Karel said, use a presched .cmd file to dump
> the system state to a flat file, then add DOMAIN -systemstate to the
> dsm.opt file so TSM won't call VSS to do the system state backup.
> Only problem is everybody remembering where you put it.
>
> The ntbackup utility in Win2K3, has been replaced with "windows
> server backup" in Win2K8.
> But it's pretty much the same thing.
> http://technet.microsoft.com/en-us/library/cc772523.aspx?ppud=4
>
> W
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Karel Bos
> Sent: Wednesday, July 30, 2014 11:37 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Backing up systemstate with something besides VSS
>
> Hi,
>
> VSS is mandatory for system state backups in forced by M$.
>
> You might look into excluding system state from TSM backups and do
> native windows backup via precmd of the system state to a flat file.
> From what I have heard windows native backup still handles the
> backup in a different way the system state where every other product
> is forced to use the unstable VSS process.
>
> Op 29 jul. 2014 21:29 schreef "Zoltan Forray" <zforray AT vcu DOT edu>:
>
> > I know this sounds strange, but let me get into the details.
> >
> > We have the W2K8R2 box that seems to lose / stop most of the VSS
> > writers, about once a month and manually starting them doesn't work
> > (requires
> > reboot) for the TSM backups. Starts producing the errors:
> >
> > ANS1948E The Microsoft volume shadow copy system components can not be
> > queried
> >
> > Running latest 7.1.0.3 client. Has been uninstalled and reinstalled
> > numerous times, including deleting all TSM directories, to no avail.
> > Server is fully patched.
> >
> > Even after rebooting the server (always during "black Tuesday"
> > patching), the backups run for a while and then start failing again,
> > requiring another reboot.
> >
> > Last failure is from today's backups. Windows event log shows a
> > failure source of "tsmVssWriter" and Event ID 4097 and plenty of other
> > VSS errors with lots of different ID's (8193, 24, 8224, 12342, 13)
> >
> > Yes, this clearly sounds like a VSS/Windows problem. Unfortunately,
> > we don't get any support from M$
> >
> > Is there a way to backup systemstate with non-VSS tools?
> >
> > Anyone else see this kind of problem?
> > --
> > *Zoltan Forray*
> > TSM Software & Hardware Administrator
> > BigBro / Hobbit / Xymon Administrator
> > Virginia Commonwealth University
> > UCC/Office of Technology Services
> > zforray AT vcu DOT 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
> >
|
