Unsubscribe

[molin gregory]

Unsubscribe

Bonjour à tous,

Après de nombreuses années passées avec TSM, nous avons opté pour une autre 
solution de sauvegarde (Veeam).

Merci à tous pour votre disponibilité et vos réponses.

Best regards,
Cordialement
Grégory
"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système.

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Upgrade server from 6.3 to 7.1

[molin gregory]

Hello everyone

I plan to upgrade my server from version 6.3 to version 7.1.
Have you had problems with this procedure?

Thank you beforehand
Grégory
"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système.

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: vtl versus file systems for pirmary pool

[molin gregory]

Hello Tim,

A random storage should be considered as temporary storage. This type of pool 
that can accept an almost unlimited number of client, it facilitates backups 
sequense
Typically, it must be large enough to accommodate the daily backup.
During the maintenance plan, it must be emptied on a sequential storage pool 
(tape or VTL).
To answer your question, name meaning, the two types of storage pool have 
different uses.

The use of a random pool without emptying induced term loss of performance: 
storage ultimately becoming a great Gruyere cheese.

Regards,
Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Tim 
Brown
Envoyé : lundi 26 septembre 2011 22:05
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] vtl versus file systems for pirmary pool

What advantage does VTL emulation on a disk primary storage pool have

as compared to disk storage pool that is non vtl ?



It appears to me that a non vtl system would not require the daily reclamation 
process

and also allow for more client backups to occur simultaneously.



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com <>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255




This message contains confidential information and is only for the intended 
recipient. If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments.

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Getting unix permissions back from TSM

[molin gregory]

Hello Steve,

You can restore your system with the mksysb backup.
Select the filesystems you want to restore.

Hope that help

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Steve 
Harris
Envoyé : vendredi 16 septembre 2011 07:15
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Getting unix permissions back from TSM

Hi All

One of my accounts has just had a unix admin tried to run something like

chown -R something:something /home/fred/*

but he had an extra space in there and ran it from the root directory

chown -R something:something /home/fred/ *

This has destroyed the ownership of the operating system binaries and trashed 
the system.  Worse it was done using a distributed tool, so quite a number of 
AIX lpars are affected including the TSM server.

Once we get the TSM Server back up, is there any way to restore just the file 
permissions without restoring the data?  I can't think of a way.  Maybe there 
is a testflag to do this?  Even a listing of the file and permissions for all 
active files would be enough to be able to fix the problem.

TSM Server 5.5 AIX 5.3

Thanks

Steve

TSM Admin
Canberra Australia.

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Rman not deleting old backups

[molin gregory]

Hello,

In certain case, rman do not remove expired backup.
You have to use tdposync for find/remove manualy backups.

Regards, Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de David 
E Ehresman
Envoyé : vendredi 22 juillet 2011 17:35
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Rman not deleting old backups

Awhile back someone shared on this list their commands/scripts for verifying 
that rman was not leaving any old backups on the TSM server.
I can't seem to find it now.  Ring a bell with anyone?

David

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Probleme with TS3200 and Redhat

[molin gregory]

Hi Pierre,

Je vais essayer ta proposition.

Merci cousin :-)


Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Billaudeau, Pierre
Envoyé : lundi 11 juillet 2011 19:24
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] Probleme with TS3200 and Redhat

Hi Grégory,
Did you run a checkin command to have your scratch tapes recognized by 
your TSM instance:

Checkin LIBVolume newlib??? SEARCH=Yes volrange=nn,nn Status=SCRATCH 
Checklabel=no devtype=devtype

Pierre Billaudeau
Analyste en stockage
Livraison des Infrastructures Serveurs
Société des Alcools du Québec
514-254-6000 x 6559


-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de molin 
gregory Envoyé : 11 juillet 2011 12:41 À : ADSM-L@VM.MARIST.EDU Objet : 
[ADSM-L] Probleme with TS3200 and Redhat

Hello,

I installed a new server, a new robot on a backup site.
TSM 6.1.4.3 - Redhat 5.4 - TS3200
The bands are visible in the robot and the console.
When I do a "query drive" I get the serial numbers and WWN.
When I did a "query library" I get no serial number but not the WWN.
No band is detected by an "audit library checkl = bar / yes If anyone has an 
idea, I'm interested


Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système.

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "


--


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.

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Probleme with TS3200 and Redhat

[molin gregory]

Hello,

I installed a new server, a new robot on a backup site.
TSM 6.1.4.3 - Redhat 5.4 - TS3200
The bands are visible in the robot and the console.
When I do a "query drive" I get the serial numbers and WWN.
When I did a "query library" I get no serial number but not the WWN.
No band is detected by an "audit library checkl = bar / yes
If anyone has an idea, I'm interested


Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: How to manually delete data inside volumes

[molin gregory]

Hello,

Try : DELETE VOLUME X DISCARDDATA=YES



Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Rhuobhe
Envoyé : jeudi 7 juillet 2011 17:28
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] How to manually delete data inside volumes

Hi I want to eliminate some volumes used as exports because they are either 
done incorrectly or have become a liability. I would like to re-use them as 
scratch.

Does anyone know the procedure or command to purge data inside those tapes so I 
can use them again? thanks.

+--
|This was sent by mlit...@med.miami.edu via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: volumes associated with a node

[molin gregory]

Hello,

Try : q nodedata NODENAME stg=

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Tim 
Brown
Envoyé : mercredi 29 juin 2011 14:40
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] volumes associated with a node

Is there a select statement that will list all tape volumes that have files for

a given TSM node.



Thanks,



Tim Brown
Systems Specialist - Project Leader
Central Hudson Gas & Electric
284 South Ave
Poughkeepsie, NY 12601
Email: tbr...@cenhud.com <>
Phone: 845-486-5643
Fax: 845-486-5921
Cell: 845-235-4255




This message contains confidential information and is only for the intended 
recipient. If the reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to the intended 
recipient, please notify the sender immediately by replying to this note and 
deleting all copies and attachments.

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Ang: Re: Tsm v6 migration question

[molin gregory]

Hello Daniel,

You say : ' That's not really something new to TSM v6'.

DB2 is now the DBMS for TSM, and if DB2 improve database, DB2 has system 
requirement who was not the same in previous version

My experience:
The installer has set up the solution on our site has not implemented the 
recommendations related to DB2.
TSM crash after two months.


Best Regards
Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Daniel 
Sparrman
Envoyé : jeudi 24 mars 2011 10:17
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Ang: Re: Tsm v6 migration question

That's not really something new to TSM v6. For performance reasons, it has 
always been recommended to separate database and log on different spindles. 

As with v6, at least for larger implementations, the same rule of thumb 
applies: Try separating your DB paths on at least 4 different arrays/spindles, 
preferably 8 or more. Too many will not increase performance, rather reduce it. 
Put your active log / log mirror on spindles of it's own, as well as your 
archivelog / failover paths.

Watch out for sharing archivelog with something else (like storage) since the 
database backup trigger will look at the % used on the filesystem. So putting 
storagepools and then your archivelog in the same filesystem probably isnt the 
best of ideas.

Best Regards

Daniel Sparrman
-"ADSM: Dist Stor Manager"  skrev: -

Till: ADSM-L@VM.MARIST.EDU
Från: molin gregory 
Sänt av: "ADSM: Dist Stor Manager" 
Datum: 03/24/2011 11:06
Ärende: Re: Tsm v6 migration question

Hello Gary,

Effectively, the database grows between 10 and 20 %. (more if new features, 
like dedup, are intalled)
But, the most important with the 6.x is the architecture of database files.
You have to reserve one disk for the database, on for the actlog and one other 
for the archlog.
Having this disks on the same axe may result poor efficientie

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Lee, 
Gary D.
Envoyé : mercredi 23 mars 2011 18:44
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Tsm v6 migration question

We are preparing to migrate our tsm v5,5,4 system to 6.2.2.


Are there any rules of thumb for relating db size in v5.5.4 with what we will 
need under v6?

I assume it will be somewhat larger being a truly relational structure.

Thanks for any help.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Tsm v6 migration question

[molin gregory]

Hello Gary,

Effectively, the database grows between 10 and 20 %. (more if new features, 
like dedup, are intalled)
But, the most important with the 6.x is the architecture of database files.
You have to reserve one disk for the database, on for the actlog and one other 
for the archlog.
Having this disks on the same axe may result poor efficientie

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Lee, 
Gary D.
Envoyé : mercredi 23 mars 2011 18:44
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Tsm v6 migration question

We are preparing to migrate our tsm v5,5,4 system to 6.2.2.


Are there any rules of thumb for relating db size in v5.5.4 with what we will 
need under v6?

I assume it will be somewhat larger being a truly relational structure.

Thanks for any help.


Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: TSM snapshots for VMs

[molin gregory]

Chad,

We do not use TDP.
We use script for backup the VM.

As you can see in my previous message, our script make a snapshot, backup the 
file and then remove the snapshot.
The use this script on 40 ESX servers.

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Harris, Chad E
Envoyé : mardi 22 mars 2011 14:45
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TSM snapshots for VMs

Gregory,

Are you using the TSM for Virtual Environments TDP along with these scripts or 
something else?

Thanks,
Chad


Subject: Re: TSM snapshots for VMs


Hello Chad,

In our environment, we use TSM for TSM backups.
Each ESX Server is member of one proxynode.
We built a backup script from a config file. this file contains VMs to be
backuped

dsmc i  -asnode=ESXPROD /vmfs/volumes/SERVER/SERVER.vmx
vmware-cmd /vmfs/volumes/SERVER/SERVER.vmx createsnapshot Snapshot_SERVER
Desc_SERVER 0 0
dsmc i  -asnode=ESXPROD -filelist=/vmfs/volumes/file_list_SERVER.txt
vmware-cmd /vmfs/volumes/SERVER/SERVER.vmx removesnapshots

The file_list_SERVER.txt contains the list of file to ba backuped.
/vmfs/volumes/SERVER/SERVER-flat.vmdk
/vmfs/volumes/SERVER/VERVER.vmdk

I hope that will help

Cordialement,
Grégory Molin
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de
Harris, Chad E
Envoyé : lundi 21 mars 2011 14:52
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TSM snapshots for VMs

Fellow TSM admins,

I am curious if anyone else out here has been given the task to provide backups
of the VMware infrastructure via TSM.  I know it might be too early to be
asking this question due to the newness of the TSM VMware TDP, but any insights
that can be given will be helpful and gratefully appreciated.

Our current virtual environment has somewhere in the neighborhood of 1700 (+)
VMs.  Currently the Virtualization team has been utilizing another product 
(which shall remain nameless) to perform weekly full snapshots.  This product
has worked reasonably well up until this point in time but now they are finding
that they have outgrown the products ability to provide these snapshots.

The problem sounds easy enough to fix right; however the problem we are having
is that the Virtualization team has traditionally only been providing backups
for the first 35 GB of the primary disk, so essentially they were only
providing snapshot restorations for the OS and nothing else.  I realize that we
could go in and have the system admins install and configure TSM on ever-single
VM that needs these snapshots and then utilize include-exclude parameters to
only backup what needs to be backed up but we were more interested in the idea
of using proxy servers to run the virtual snapshots.

Taking all of this into consideration our question is this, is there a way to
configure the settings on the proxy server so that it will only backup the 
primary disk on each virtual server?

Thanks,
Chad Harris

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces
jointes de votre système.

This message and any attachments are confidential and intended to be received
only by the addressee. If you are not the intended recipient, please notify
immediately the sender by reply and delete the message and any attachments from
your system. "

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: TSM snapshots for VMs

[molin gregory]

Hello Chad,

In our environment, we use TSM for TSM backups.
Each ESX Server is member of one proxynode.
We built a backup script from a config file. this file contains VMs to be 
backuped

dsmc i  -asnode=ESXPROD /vmfs/volumes/SERVER/SERVER.vmx
vmware-cmd /vmfs/volumes/SERVER/SERVER.vmx createsnapshot Snapshot_SERVER 
Desc_SERVER 0 0
dsmc i  -asnode=ESXPROD -filelist=/vmfs/volumes/file_list_SERVER.txt
vmware-cmd /vmfs/volumes/SERVER/SERVER.vmx removesnapshots 

The file_list_SERVER.txt contains the list of file to ba backuped.
/vmfs/volumes/SERVER/SERVER-flat.vmdk
/vmfs/volumes/SERVER/VERVER.vmdk

I hope that will help

Cordialement,
Grégory Molin
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Harris, Chad E
Envoyé : lundi 21 mars 2011 14:52
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TSM snapshots for VMs

Fellow TSM admins,

I am curious if anyone else out here has been given the task to provide backups 
of the VMware infrastructure via TSM.  I know it might be too early to be 
asking this question due to the newness of the TSM VMware TDP, but any insights 
that can be given will be helpful and gratefully appreciated.

Our current virtual environment has somewhere in the neighborhood of 1700 (+) 
VMs.  Currently the Virtualization team has been utilizing another product 
(which shall remain nameless) to perform weekly full snapshots.  This product 
has worked reasonably well up until this point in time but now they are finding 
that they have outgrown the products ability to provide these snapshots.

The problem sounds easy enough to fix right; however the problem we are having 
is that the Virtualization team has traditionally only been providing backups 
for the first 35 GB of the primary disk, so essentially they were only 
providing snapshot restorations for the OS and nothing else.  I realize that we 
could go in and have the system admins install and configure TSM on ever-single 
VM that needs these snapshots and then utilize include-exclude parameters to 
only backup what needs to be backed up but we were more interested in the idea 
of using proxy servers to run the virtual snapshots.

Taking all of this into consideration our question is this, is there a way to 
configure the settings on the proxy server so that it will only backup the 
primary disk on each virtual server?

Thanks,
Chad Harris

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: File device class directories

[molin gregory]

Hello Rick

Look at http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp

Reference / Server commands / Administrative commands / Define / Define 
DEVCLASS FILE

TSM calculate space remmaining in each directory.



by cons, it is preferable to pre-allocate volumes.
Furthermore, it should not create too large volumes.
In our case, we have 500 volumes of 20 GB, which makes it easier to reclaim.




Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de 
Richard Rhodes
Envoyé : jeudi 10 mars 2011 01:31
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] File device class directories

If you have a Device Class of type FILE with multiple directories, 
how does TSM decide which directory to allocate new volumes in?  
The Admin Guide simply says that TSM decides, but gives no more 
idea than that. In a bunch of searching I've found no real explanation 
of the decision process (least amount of data, least full directory, 
round-robin, number of volumes, 
alignment of the stars).  

THanks

Rick




-
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Tsm backing up mysql databases

[molin gregory]

Hello,

Try mysqldump then dsmc i

mysqldump --add-drop-table --character-sets-dir=latin1 -u USER -pPASSWORD 
DATABASE --routines > /backup/backup_database.sql

dsmc i /backup/

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Lee, 
Gary D.
Envoyé : jeudi 24 février 2011 14:51
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Tsm backing up mysql databases

We now have a request to back up a server running some library app that uses 
mysql for its databases.

The only guidance I have seen so far searching the internet is to use adsmpipe.

Are any of you doing mysql backups, if so how?



Gary Lee
Senior System Programmer
Ball State University
phone: 765-285-1310

 

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

RE : [ADSM-L] How many disk volumes are too many?

[molin gregory]

Hello Zoltan,

First is to know if this volumes are for sequential or random access.

In our configuration, we have 3 100Go volumes for random access and more than 
500 volumes of 20Go  for sequential access.

The first avantage off have many small volumes cause TSM using as many volumes 
is want. (maximun mount point for the devclass)

The second, is to be able to reclaim very quickly such volumes. In our case, we 
reclaim with a threshold=40.


Cordialement, 
Regards,
Grégory



De : ADSM: Dist Stor Manager [ADSM-L@VM.MARIST.EDU] de la part de Zoltan 
Forray/AC/VCU [zfor...@vcu.edu]
Date d'envoi : jeudi 17 février 2011 19:15
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] How many disk volumes are too many?

I am aware of the TSM design that says the more disk volumes you have, the
more it will spread out the I/O  for better performance.  I also realize a
lot of this doesn't really apply what with RAID-5, EMC SAN, multi-terabyte
storage, etc.

So, at what point does having lots of smaller volumes (for a disk LZ), not
give you any more benefit, I/O wise?

I have a 5.3TB SAN space on my new 6.2.2.0 server.  Originally, I started
formatting 200GB volumes then moved to 300GB, up to 25-volumes.

Now I am adding another 5.3TB space and was wondering if I should continue
with 300GB or jump to 500GB?

Simultaneous sessions should not be an issue since most of these backups
are Domino TDP and therefore single thread.  I don't think there is a peak
of more than 60-simultaneous sessions.

The TSM server is a Dell T710 with 48GB RAM and 15K internal disk for the
DB & Logs.

Your thoughts?
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zfor...@vcu.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

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

I/O error - excessive read errors encountered

[molin gregory]

Hello everyone,

I meet a lot of I/O errors for the disk storage on my TSM server.
These errors prevent migration, move and space reclaim
Has anyone experienced the same kind of problem ?

All volumes on both SAS_BACK_P and VTL_BACK_P was newly created.


SAS_BACK_P  DISK307 G   0.0   0.0  100  99  
   VTL_BACK_P
VTL_BACK_P  VTL  10,716 G  46.8  46.8   95  90  
   LTO_BACK_P


01/31/2011 12:51:14  ANR8555E An error (5, ) occurred during a read 
operation
  from disk /tsm/sas/1/sas01.dsm.

01/31/2011 15:32:29  ANR1083E Space reclamation is ended for volume
  /tsm/sas/2/back2061.dsm. Excessive read errors were
  encountered. (SESSION: 2091, PROCESS: 169)

01/31/2011 16:05:58  ANR1146W Move data process terminated for volume
  /tsm/sas/2/back2055.dsm - excessive read errors
  encountered. (SESSION: 2091, PROCESS: 250)

The /var/log/messages

Jan 31 12:51:11 courge kernel: sd 2:0:0:0: SCSI error: return code = 0x0007
Jan 31 12:51:11 courge kernel: end_request: I/O error, dev sda, sector 
3142140026
Jan 31 12:51:11 courge kernel: sd 2:0:0:0: SCSI error: return code = 0x0007
Jan 31 12:51:11 courge kernel: end_request: I/O error, dev sda, sector 
3103215898
Jan 31 12:51:11 courge kernel: sd 2:0:0:1: SCSI error: return code = 0x0007
Jan 31 12:51:11 courge kernel: end_request: I/O error, dev sdb, sector 
4116825010
Jan 31 12:51:12 courge kernel: sd 2:0:0:1: SCSI error: return code = 0x0007
Jan 31 12:51:12 courge kernel: end_request: I/O error, dev sdb, sector 
4116822962
Jan 31 12:51:12 courge kernel: sd 2:0:0:1: SCSI error: return code = 0x0007

Jan 31 15:32:27 courge kernel: sd 2:0:0:1: SCSI error: return code = 0x0007
Jan 31 15:32:27 courge kernel: end_request: I/O error, dev sdb, sector 
4387960770
Jan 31 15:32:29 courge kernel: sd 2:0:0:1: SCSI error: return code = 0x0007
Jan 31 15:32:29 courge kernel: end_request: I/O error, dev sdb, sector 
1667104026

Jan 31 16:05:58 courge kernel: sd 2:0:0:1: SCSI error: return code = 0x0007
Jan 31 16:05:58 courge kernel: end_request: I/O error, dev sdb, sector 
4387962306

Thanks for your help

Regards
Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: Windows 2000 client

[molin gregory]

Hello Duane,

There is no problem for running 5.5.3 client on W2K with a 6.x TSM Server.

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org

-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] De la part de Ochs, 
Duane
Envoyé : vendredi 14 janvier 2011 21:37
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] Windows 2000 client

Good day everyone,
My TSM servers are currently at 5.5.4 and I'd like to get migrated to 6.2 this 
year.
I have some W2K clients that cannot be retired at this time and I found that 
5.5 clients are the oldest supported by 6.2

Is anyone out there using the TSM 5.3 client on W2k and any version of TSM 
server 6.*

Any "helpful" ideas would be appreciated.

Thanks,
Duane


Follow Quad/Graphics in social media 
  
  


"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: TDP Exchange indiviual mailbox restore failure

[molin gregory]

Hello,

The mailbox you want to restore

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de Bjoern 
Rackoll
Envoyé : mercredi 27 octobre 2010 17:56
À : ADSM-L@VM.MARIST.EDU
Objet : Re: [ADSM-L] TDP Exchange indiviual mailbox restore failure

Hello Gregory,

> We met the same problem.
> The only workaround we found is that both "Exchange Domain Servers" "Exchange 
> Organization Administrators" "Exchange Public Folder Administrators" and " 
> Exchange Service" have full access on the mailbox.

where exactly on the mailbox server did you set these permissions? Did I
understand you right that this works without having to install the CAS
role on the mailbox server?

Regards,

--
Bjoern Rackoll
University of Hamburg
Regionales Rechenzentrum
Zentrale Dienste
Schlueterstr. 70
D-20146 Hamburg
Tel.: +49 (0)40 42838 - 63 11
Fax: +49 (0)40 42838 - 62 70
Mobil: +49 (0)172 427 0301
E-Mail: bac...@rrz.uni-hamburg.de

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: TDP Exchange indiviual mailbox restore failure

[molin gregory]

Hello,

We met the same problem.
The only workaround we found is that both "Exchange Domain Servers" "Exchange 
Organization Administrators" "Exchange Public Folder Administrators" and " 
Exchange Service" have full access on the mailbox.

I hope that that will help you

Regards,

Cordialement,
Grégory Molin
Tel : 0141628162
gregory.mo...@afnor.org
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de Bjoern 
Rackoll
Envoyé : mercredi 27 octobre 2010 15:41
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TDP Exchange indiviual mailbox restore failure

Hi all,

during the installation of the TDP for Exchange product for a new
environment we ran into the problem that the restore of an individual
mailbox to a .pst file didn't work, the trace showed the error
'MAPI_E_NETWORK_ERROR'. TSM support suggested that it is the problem
noted in http://www-01.ibm.com/support/docview.wss?uid=swg21445283 .

However, the 'workaround' described in this technote can't be applied in
our environment (the Mailbox Server and CAS roles are on different
servers for a reason, and between these servers is a firewall preventing
Outlook clients from talking directly to the mailbox server). Has anyone
seen the same problem, and if yes, how did you deal with it?

OS: Windows 2008 Server R2, 64bit
B/A-Client: 6.2.1.3
TDP Exchange: 6.1.2.1
TSM Server: 5.5.4.0 on AIX

Regards,

--
Bjoern Rackoll
University of Hamburg
Regionales Rechenzentrum
Zentrale Dienste
Schlueterstr. 70
D-20146 Hamburg
Tel.: +49 (0)40 42838 - 63 11
Fax: +49 (0)40 42838 - 62 70
Mobil: +49 (0)172 427 0301
E-Mail: bac...@rrz.uni-hamburg.de

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "

Re: TSM V6.1 Upgrade

[molin gregory]

Hello,

Be carefull when upgrading your TSM.
The architecture for the 6 is no more like the 5.
You have to plan new storage architecture for the DB2 instance.


Excuse for my poor english..

Cordialement,
Grégory Molin
-Message d'origine-
De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de 
BrentFortune
Envoyé : mercredi 13 octobre 2010 12:52
À : ADSM-L@VM.MARIST.EDU
Objet : [ADSM-L] TSM V6.1 Upgrade

Hi All, i'm planning to upgrade a TSM V5.5 Server with 2 instances of TSM to 
TSM V6.1. Does anyone know if there are any limitations in running 2 TSM V6.1 
instances on the same machine? I ask this due to the fact taht in DB2 the TSM 
DB name is always TSMDB1.

+--
|This was sent by bre...@puleng.co.za via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--

"ATTENTION.

Ce message et les pièces jointes sont confidentiels et établis à l'attention 
exclusive de leur destinataire (aux adresses spécifiques auxquelles il a été 
adressé). Si vous n'êtes pas le destinataire de ce message, vous devez 
immédiatement en avertir l'expéditeur et supprimer ce message et les pièces 
jointes de votre système. 

This message and any attachments are confidential and intended to be received 
only by the addressee. If you are not the intended recipient, please notify 
immediately the sender by reply and delete the message and any attachments from 
your system. "