I'd say yes, hypervisors (with the right storage/procedures) mitigates the need for this. We don't back up system state for anything. But, using VMware snapshots for temporary backups, and array based snapshots for longer restores, minimizes the need that we could have for system restores.
The the machine becomes unusable, the VM team mounts an array based snapshot, and restores the whole VM (or portions if needed) and never rely on TSM. As such, we only backup files that are likely to need to be restored (logs and similar changing data) to TSM. --------------------------------------------------- David Nixon System Engineer II Technology Services Group Carilion Clinic 451 Kimball Ave. Roanoke, VA 24015 Phone: 540-224-3903 cdni...@carilionclinic.org Our mission: Improve the health of the communities we serve. ________________________________________ From: ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] on behalf of Del Hoobler [hoob...@us.ibm.com] Sent: Tuesday, December 13, 2016 5:51 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] ISP 81 Discontinued functions Let me ask a related question. Does the hypervisor world mitigate the need for this? I am seeing fewer and fewer requests for this type of recovery because of the capabilities of hypervisors and hypervisor-based backups. Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/13/2016 05:42:38 PM: > From: Tom Alverson <tom.alver...@gmail.com> > To: ADSM-L@VM.MARIST.EDU > Date: 12/13/2016 05:44 PM > Subject: Re: ISP 81 Discontinued functions > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > The worst part about this is the extremely poor setup IBM has for doing an > offline restore. They give you the instructions to create your own boot > disk. I read it over and could not believe IBM did not have a nice > pre-made recovery boot disk like Symantec, AVAMAR and Networker do. Are > there any plans for IBM to do this? Has anyone successfully made one of > these do it yourself recovery disks? > > Tom > > On Tue, Dec 13, 2016 at 10:59 AM, Hans Christian Riksheim <bull...@gmail.com > > wrote: > > > Hi Del. > > > > Why no prior warning? This was news to me until the 8.1 GA. We have several > > environments where BMR is based on online systemstate restore(which works > > very well) and now these customers say that they are ready to roll out > > Win2016. Now there is a rush to look at solutions to this sudden problem > > including testing that cumbersome PE procedure to avoid a time window with > > no tested method for BMR. > > > > Hans Chr. > > > > On Tue, Dec 13, 2016 at 4:15 PM, Del Hoobler <hoob...@us.ibm.com> wrote: > > > > > Hi Hans Chr., > > > > > > Microsoft has had this position since 2008, but IBM still tried to > > support > > > it due to customer requests. It led to too many situations where a system > > > was unstable after a restore. > > > > > > > > > Del > > > > > > ---------------------------------------------------- > > > > > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/13/2016 > > > 06:42:55 AM: > > > > > > > From: Hans Christian Riksheim <bull...@gmail.com> > > > > To: ADSM-L@VM.MARIST.EDU > > > > Date: 12/13/2016 06:43 AM > > > > Subject: Re: ISP 81 Discontinued functions > > > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > > > > > I am not sure if I follow. Has Microsoft communicated a change in its > > > > support for systemstate restores or is it just IBMs decision to not > > > bother > > > > with it anymore? > > > > > > > > Hans Chr. > > > > > > > > On Mon, Dec 12, 2016 at 9:08 PM, Del Hoobler <hoob...@us.ibm.com> > > wrote: > > > > > > > > > Hi Martin, > > > > > > > > > > It's true IBM Spectrum Protect did support online system state > > > restores > > > > > before, but it is against Microsoft's best practices to support it. > > > IBM > > > > > Spectrum Protect 8.1 is more strictly enforcing the documented best > > > > > practices from Microsoft for system state restores. > > > > > > > > > > IBM did not drop the API support for LoP BE specifically so that Data > > > > > Protection for SAP HANA on Power BE continues to be supported. > > > However, > > > > > IBM's strategic direction is LoP LE ( > > > > > > > > https://www.ibm.com/developerworks/library/l- > > power-little-endian-faq-trs/ > > > > > ). Both SAP and Data Protection for SAP HANA have LoP LE support on > > > the > > > > > roadmap for 1H17. Your investment in Linux on Power is safe, it is > > > just > > > > > that the software will switch to LE architecture from current BE > > > > > architecture in the future. > > > > > > > > > > Del > > > > > > > > > > ---------------------------------------------------- > > > > > > > > > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 12/12/2016 > > > > > 10:18:18 AM: > > > > > > > > > > > From: Martin Janosik <martin.jano...@cz.ibm.com> > > > > > > To: ADSM-L@VM.MARIST.EDU > > > > > > Date: 12/12/2016 10:19 AM > > > > > > Subject: Re: ISP 81 Discontinued functions > > > > > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > > > > > > > > > I'm also a bit nervous and curoius at the same time about > > > discontinued > > > > > > functions, namely: > > > > > > Online system state restores - You can no longer restore the system > > > > > state > > > > > > on a system that is online. Instead, use the Automated System > > > Recovery > > > > > > (ASR) based recovery method to restore the system state in offline > > > > > Windows > > > > > > Preinstallation Environment (PE) mode. > > > > > > and > > > > > > The following operating systems are no longer supported by the > > > > > > backup-archive client: > > > > > > Linux on Power Systems™ (big endian). You can still use the IBM > > > Spectrum > > > > > > Protect API on Linux on Power Systems (big endian). > > > > > > > > > > > > What is the idea behind "to be competive with x86 platform and get > > > > > > compativility certification for SAP HANA with Linux on Power > > > platform > > > > > (Big > > > > > > Endian)" (ref. > > > > > > https://blogs.saphana.com/2015/08/21/announcing-general- > > > > > > availability-of-sap-hana-on-ibm-power-systems/ > > > > > > ) and then 1.5 year later drop support of BAclient for OS"? > > > > > > > > > > > > We deployed 10+ big SAP HANA on Power8 instances last year, and now > > > we > > > > > will > > > > > > be getting "not supported" for new releases? > > > > > > > > > > > > M. Janosik > > > > > > > > > > > > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on > > 12/09/2016 > > > > > > 02:45:34 PM: > > > > > > > > > > > > > From: Chavdar Cholev <chavdar.cho...@gmail.com> > > > > > > > To: ADSM-L@VM.MARIST.EDU > > > > > > > Date: 12/09/2016 02:47 PM > > > > > > > Subject: [ADSM-L] ISP 81 Discontinued functions > > > > > > > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > > > > > > > > > > > > > Does some one check discontinued functions in new version... > > > > > > > especially part of no VM backup as standard function in BA > > > client.... > > > > > > > It is not good at all. TDP for Virtual environment for hyper-V > > > creats > > > > > > diff > > > > > > > hdds (.avhdx) > > > > > > > and my customers will not be happy with this, because you have to > > > > > merge > > > > > > > these file, > > > > > > > when you need to expand .vhdx disk for example .... > > > > > > > > > > > > > > :( > > > > > > > Regards > > > > > > > Cahvdar > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ________________________________ Notice: The information and attachment(s) contained in this communication are intended for the addressee only, and may be confidential and/or legally privileged. If you have received this communication in error, please contact the sender immediately, and delete this communication from any computer or network system. Any interception, review, printing, copying, re-transmission, dissemination, or other use of, or taking of any action upon this information by persons or entities other than the intended recipient is strictly prohibited by law and may subject them to criminal or civil liability. Carilion Clinic shall not be liable for the improper and/or incomplete transmission of the information contained in this communication or for any delay in its receipt.
