ADSM-L

Re: [ADSM-L] Is TSM for VE 7.1.1.1 pagefile aware? Is it contrained to a single process per datamover? What constitutes a successful backup?

2015-03-02 14:37:03
Subject: Re: [ADSM-L] Is TSM for VE 7.1.1.1 pagefile aware? Is it contrained to a single process per datamover? What constitutes a successful backup?
From: Matthew McGeary <Matthew.McGeary AT POTASHCORP DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 2 Mar 2015 13:35:16 -0600
Hello Steve,

There's no mention of pagefile 'awareness' in the documentation, so it's safe to say that the backup will consist of all changed blocks, regardless of what's stored on them.  As for threaded behavior, I've pinned all the cores on my datamover during heavy parallel backups using deduplication, so while it may only register as a single process in the Task Manager, it seems clear that TSM is acting like a multi-threaded application.  As for your last point, I don't know why IBM changed the status codes for VM schedules from 'Failed' to 'Completed' but I suspect it has something to do with VMWare's abysmal ability to create quiesced snapshots on a consistent basis.

We backup ~500 VMs on a daily basis and usually have 4-5 failures, all due to quiescing errors.  I guess IBM got tired of customer complaints that their VM backup schedules 'always failed' and quietly changed the status code to make the product look a little better.


__________________________

Matthew McGeary
Technical Specialist - Operations
PotashCorp
T: (306) 933-8921
www.potashcorp.com





From:        "Schaub, Steve" <Steve_Schaub AT BCBST DOT COM>
To:        ADSM-L AT VM.MARIST DOT EDU
Date:        03/02/2015 11:24 AM
Subject:        [ADSM-L] Is TSM for VE 7.1.1.1 pagefile aware?  Is it contrained to a single process per datamover?  What constitutes a successful backup?
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>





1.       Is VE pagefile aware?  I.E. is it smart enough to know not to bother backing up changed blocks from within the pagefile.sys file?

2.       It appears to me that a given datamover only uses a single Windows process, even for multiple concurrent backups.  That would seem to constrain it to a single core.  Can someone confirm/deny?  If it is, does it make sense to define multiple datamovers per "proxy server" in order to take advantage of multi-core machines?

3.       Why do schedules with failed VM backups show "successful"?
02/28/2015 02:37:11 Total number of virtual machines failed: 4
02/28/2015 02:37:11 Total number of virtual machines processed: 375
02/28/2015 02:37:11 Scheduled event 'VE_INCR_N01_BCBST_DM02' completed successfully.

Thanks,

Steve Schaub
Systems Engineer II, Backup/Recovery
Blue Cross Blue Shield of Tennessee

-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail disclaimer:  
http://www.bcbst.com/email_disclaimer.shtm

<Prev in Thread] Current Thread [Next in Thread>