Re: Aw: Re: [ADSM-L] Exchange Backup with Flashcopy Manager EXTREMELY slow

2015-02-24 Thread Billaudeau, Pierre
Hi John,
I had a similar situation with Exchange 2010 TSM DP backups and the 
reason was the VM  had been Vmotioned from one ESX to another. Lan speed went 
from 1Gbs to 100Gbs. You might want to check this.

Pierre Billaudeau
Administrateur stockage

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Jeanne 
Bruno
Envoyé : 23 février 2015 15:43
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Aw: Re: [ADSM-L] Exchange Backup with Flashcopy Manager 
EXTREMELY slow

Hello.  we skip integrity check as well.  Backups stored on a DS3512 device

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of John 
Keyes
Sent: Monday, February 23, 2015 2:47 PM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Aw: Re: [ADSM-L] Exchange Backup with Flashcopy Manager 
EXTREMELY slow

Thank you Chavdar Cholev and Jeanne Bruno for sharing. I forgot to tell, we do 
skip the integrity check, and there are only passive Databases on the server.
Are your backups going to TSM server or to a local storage? Im interested 
either way.

Best Regards,
John



Gesendet: Montag, 23. Februar 2015 um 20:20 Uhr
Von: Chavdar Cholev chavdar.cho...@gmail.com
An: ADSM-L@VM.MARIST.EDU
Betreff: Re: [ADSM-L] Exchange Backup with Flashcopy Manager EXTREMELY slow We 
have ~ 2TB full exchange backup and it takes ~ 20 hours. There is exch db 
consistency check before backup which takes considerable amount of time.
It can be switched off... but it is not recommnded

On Monday, 23 February 2015, John Keyes ra...@gmx.net wrote:

 Hello fellow TSM Admins!

 I'm struggling with Exchange Backup which over the course of the last
 few Days (mainly since the last full backup this weekend) takes about
 3-4 times as long as before.
 We have Exchange 2013 DAG with 48 Databases and a dedicaded VM to do
 the Backups (Flashcopy Manager 4.1.1, Backupdestination=local, on an
 IBM V7000 Storage).
 Right now even an incremental backup of 1 database takes ~12 minutes,
 but the volume is only 30GB big and has only 5GB (5000 x 1MB Files) on
 it. Two weeks ago this would only take 3 Minutes.
 A Full backup takes about half an hour (so I couldn't even complete a
 full backup for every database in one day). I also tried to
 full-backup the same database twice right after one another, with no 
 difference.

 This can hardly be normal, can it? Has anyone had the same problems
 and maybe could point me in the right direction?
 Also it would be great if anyone could share how much time their
 backups take...

 Best regards,
 John


--


Information confidentielle : Le présent message, ainsi que tout fichier qui y 
est joint, est envoyé à l'intention exclusive de son ou de ses destinataires; 
il est de nature confidentielle et peut constituer une information privilégiée. 
Nous avertissons toute personne autre que le destinataire prévu que tout 
examen, réacheminement, impression, copie, distribution ou autre utilisation de 
ce message et de tout fichier qui y est joint est strictement interdit. Si vous 
n'êtes pas le destinataire prévu, veuillez en aviser immédiatement l'expéditeur 
par retour de courriel et supprimer ce message et tout document joint de votre 
système. Merci.


TSM for VE 7.1.1.1 exclude vm question

2015-02-24 Thread Schaub, Steve
New to VE, looked through the docs and still unsure if this is supported:
Can I use a Client Option Set to centralize all the specific excludes of VM's, 
or am I limited to putting them in each Datamover's opt files?
If yes, can someone send me a working example?

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


Re: TSM for VE 7.1.1.1 exclude vm question

2015-02-24 Thread Ryder, Michael S
Here's an excerpt from my datamover's opt file.  We use a single opt file
and put all our excludes in it, but I would like to hear how other people
do it, too.

...snip...
EXCLUDE.DIR \\*\*$\...\USMTBackup
EXCLUDE.DIR \\server1\T$\Temp
EXCLUDE.DIR \\*\*$\...\Program Files\Crystal Decisions\Enterprise
10\FileStore\Output
EXCLUDE.DIR \\*\*$\...\SplunkUniversalForwarder
EXCLUDE.DIR \\server2\e$
EXCLUDE \\*\*$\...\hiberfil.sys
EXCLUDE \\*\*$\...\pagefil.sys
...snip...

Best regards,

Mike Ryder, x7942
RMD IT Client Services

On Tue, Feb 24, 2015 at 11:04 AM, Schaub, Steve steve_sch...@bcbst.com
wrote:

 New to VE, looked through the docs and still unsure if this is supported:
 Can I use a Client Option Set to centralize all the specific excludes of
 VM's, or am I limited to putting them in each Datamover's opt files?
 If yes, can someone send me a working example?

 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



Re: TSM for VE 7.1.1.1 exclude vm question

2015-02-24 Thread David Ehresman
You need to put the VM excludes either in each of datamover dsm.opt or put them 
in the schedule that the datamover is associated with.  We put them in the 
schedule because I can update them without logging onto each of the datamovers.

David

-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of 
Schaub, Steve
Sent: Tuesday, February 24, 2015 11:05 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] TSM for VE 7.1.1.1 exclude vm question

New to VE, looked through the docs and still unsure if this is supported:
Can I use a Client Option Set to centralize all the specific excludes of VM's, 
or am I limited to putting them in each Datamover's opt files?
If yes, can someone send me a working example?

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