[prev in list] [next in list] [prev in thread] [next in thread] 

List:       adsm-l
Subject:    Re: VCB Integration, specifically how to do incrementals
From:       Wojtek_Pięcek <woju () PINGWIN ! WAW ! PL>
Date:       2007-12-22 11:56:57
Message-ID: 60d58b650712220356y4e047979w39037f146e9157e6 () mail ! gmail ! com
[Download RAW message or body]

On Dec 22, 2007 5:48 AM, Schaub, Steve <steve_schaub@bcbst.com> wrote:
> 1. offload VMWare hosts from backup processing

We talking about vmware - I can't beliew that Your virtual machine
haven't enought power to process incremental file backup. More - on
all well know operating system, not only windows.

Can You describe me structure of windows machine? Lots of files? Lots
of directories? Hi load of machine?

> 2. bare-metal recoverability

I'm not windows administrator, so my exp. in windowed enviroment is
poor, but I know about bare machine restore - tsm fully suport that,
instalation disc (windows) too, etc. Maybe restiring using this method
is weak (from tsm instructor) but I'm not expert - can You confirm
this?



> -steve
> 
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Wojtek \
>                 Piecek
> Sent: Friday, December 21, 2007 4:41 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: [ADSM-L] VCB Integration, specifically how to do incrementals
> 
> Some of users report problem with integrating VCB and tsm version 5.2.
> 
> Another question is why use vcb, when You have excelent tsm client for
> quest, especialy with some extra function like full, increment and
> other level backup - I still cant understand why use vcb.
> 
> On Dec 21, 2007 7:14 PM, Schaub, Steve <steve_schaub@bcbst.com> wrote:
> > Steve,
> > Unfortunately, our TSM servers are still at the 5.2 level (owned by
> > another group), so the 5.5 client features are not yet available to me.
> > But they look very appealing.
> > -steve
> > 
> > 
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> > Steven Harris
> > Sent: Tuesday, December 18, 2007 6:06 PM
> > To: ADSM-L@VM.MARIST.EDU
> > Subject: Re: [ADSM-L] VCB Integration, specifically how to do
> > incrementals
> > 
> > Hi Steve
> > 
> > I can't help with your query, but are you using the new facilities of
> > 5.5
> > client?  If so I would be most grateful if you could post your
> > experiences
> > here when you have some to share.
> > 
> > Thanks
> > 
> > Steve Harris
> > TSM Admin, Sydney Australia
> > 
> > "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 19/12/2007
> > 06:45:22 AM:
> > 
> > > I'm working on integrating TSM into VMWare's VI3 VCB, and I'm running
> > > into a minor glitch.
> > > 
> > > I'm thinking about doing a weekly full VCB snap, and using TSM to
> > > archive these - this works no problem.
> > > 
> > > I want also to do a daily file-level VCB snap, and perform a TSM
> > > incremental on the mounted filesystem.
> > > 
> > > The problem I'm having is that my script isn't going to know what
> > > volumes are on each vm, and because VCB uses ntfs mount points, I have
> > > to explicitly identify each one in my incremental backup command.
> > > 
> > > Anyone have a good way of finding and parsing a list of mount points
> > > within a windows .cmd batch script?
> > > 
> > > 
> > > 
> > > Thanks,
> > > 
> > > 
> > > 
> > > Steve Schaub
> > > 
> > > Systems Engineer, Windows
> > > 
> > > Blue Cross Blue Shield of Tennessee
> > > 
> > > 423-535-6574 (desk)
> > > 
> > > 423-785-7347 (mobile)
> > > 
> > > 
> > > 
> > > Please see the following link for the BlueCross BlueShield of
> > > Tennessee E-mail disclaimer:
> > http://www.bcbst.com/email_disclaimer.shtm
> > Please see the following link for the BlueCross BlueShield of Tennessee E-mail \
> > disclaimer:  http://www.bcbst.com/email_disclaimer.shtm 
> 
> 
> 
> --
> --w
> Please see the following link for the BlueCross BlueShield of Tennessee E-mail \
> disclaimer:  http://www.bcbst.com/email_disclaimer.shtm 



--
--w


[prev in list] [next in list] [prev in thread] [next in thread]