AW: recommended server version 8.1.20 or 8.1.21?

Hi Eric, thanks. Yesterday, I installed 8.1.21. Kirsten Glöer -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager Im Auftrag von Loon, Eric van (ITOP DI) - KLM Gesendet: Donnerstag, 22. Februar 2024 11:07 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] recommended server version

AW: [ADSM-L] NFS Storage used as directory container storage pool

Hi Ricardo, You may leave the list at any time by sending a "SIGNOFF ADSM-L" command to LISTSERV AT VM.MARIST DOT EDU (or LISTSERV@MARIST.BITNET). Regard, Uwe -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager Im Auftrag von Ribeiro, Ricardo Gesendet: Dienstag, 2. August 2022

Re: AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers

compression. > Success ! > David > > > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Zoltan > Forray > Sent: Monday, June 27, 2022 10:03 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Moving archives into &g

Re: AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers

orray Sent: Monday, June 27, 2022 10:03 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers My production ISP servers have 3TB SSD for the DB/logs, 150TB internal disks and multiple NFS/ISILON and other disks as needed as well as tape. Thes

Re: AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers

ing for trouble IMHO. > > David. > > -Original Message- > From: ADSM: Dist Stor Manager On Behalf Of Zoltan > Forray > Sent: Monday, June 27, 2022 9:01 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Moving archives into > containers

Re: AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers

for trouble IMHO. David. -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Zoltan Forray Sent: Monday, June 27, 2022 9:01 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers Since I did the RESET CONVERSION against

Re: AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers

Forray > Gesendet: Montag, 27. Juni 2022 19:43 > An: ADSM-L@VM.MARIST.EDU > Betreff: Re: [ADSM-L] AW: [ADSM-L] Moving archives into containers > > Next question - how do you perform a DB Backup via Virtual Volume if you > can't use a container and have converted the only stgpool y

AW: [ADSM-L] AW: [ADSM-L] Moving archives into containers

@VM.MARIST.EDU Betreff: Re: [ADSM-L] AW: [ADSM-L] Moving archives into containers Next question - how do you perform a DB Backup via Virtual Volume if you can't use a container and have converted the only stgpool you have to container? We have 2-test ISP servers - 1-physical and 1-VM. The VM test

Re: AW: [ADSM-L] Moving archives into containers

Next question - how do you perform a DB Backup via Virtual Volume if you can't use a container and have converted the only stgpool you have to container? We have 2-test ISP servers - 1-physical and 1-VM. The VM test ISP server performs DBBackups to the physical one. After I converted the

AW: [ADSM-L] Moving archives into containers

HI Zoltan, yes, as soon as the "convert stgpool" is getting started, the ISP server prevents any further ingest of data in the source. Normally before a "convert stgpool" the management class is adjusted accordingly, so that the clients don't have to wait until the convert is done. The "reset

AW: [ADSM-L] Moving archives into containers

Hi Zoltan, you can use the "move nodedata" command to just move data of type "Archive" of a node (which is currently located/stored on tape) to an other (e.g. sequential file) pool. After the "move" is done, you can do a "convert stgpool" fort hat amount of data. When that data is converted to

Re: AW: [ADSM-L] BA Client 8.1.13.3 documentation

Thank you. I finally got the email about the update. On Fri, Jan 14, 2022 at 9:32 AM Uwe Schreiber wrote: > Hi Zoltan, > > I assume you are searching for this information ... > > > https://www.ibm.com/support/pages/node/6540692?myns=swgtiv=OCSSEQVQ=E_sp=swgtiv-_-OCSSEQVQ-_-E > > Regards, Uwe >

AW: [ADSM-L] BA Client 8.1.13.3 documentation

Hi Zoltan, I assume you are searching for this information ... https://www.ibm.com/support/pages/node/6540692?myns=swgtiv=OCSSEQVQ=E_sp=swgtiv-_-OCSSEQVQ-_-E Regards, Uwe -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager Im Auftrag von Zoltan Forray Gesendet: Freitag, 14. Januar

AW: [ADSM-L] Problems installing OC-Patch 8.1.13-100 after 8.1.13 upgrade ==> solved!

Hi, usually, this problem arises when the path to the shell (here: bash) is not found or the path to another program that is used. try: #!/usr/bin/env bash Best regards, Kirsten -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Bjørn

AW: [ADSM-L] update node command fails

Hi Uwe, thank you for clarification. Best regards, Rainer -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager Im Auftrag von Uwe Schreiber Gesendet: Mittwoch, 1. Dezember 2021 12:07 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] update node command fails HI Rainer, In ISP versions

AW: [ADSM-L] client deployment with SP 8.1.12

Hi Stefan, there are two more things missing: the catalog file (http://ftp.scc.kit.edu/pub/tsm/mirror/catalog/client/catalog.json) and corrections in the database. We also don't allow internet access for our TSM or auxiliary servers and therefore have a similar problem getting client deployment

Re: AW: [ADSM-L] Old clients cannot connect to 8.1.10 server

-archive client V6.2 or earlier -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: "Andreas Boesler" À: ADSM-L@VM.MARIST.EDU Envoyé: Jeudi 20 Août 2020 16:42:55 Objet: [ADSM-L] AW: [ADSM-L] Old clients cannot connect to 8.1.10 server Hi Erwann, p

AW: [ADSM-L] Old clients cannot connect to 8.1.10 server

Hi Erwann, perhaps you need: setopt ALLOWDESAUTH YES Kind regards, Andreas. i. A. Andreas Boesler Consultant Tel: +49 6151 8290-7780 Mobil: +49 163 8075141 Fax: +49 6151 8290-7692 E-Mail:a.boes...@profi-ag.de PROFI Engineering Systems AG Otto-Röhm-Straße 18 64293 Darmstadt

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

ine to limit > the # of containers processed in one day > > > Del > > > > > "ADSM: Dist Stor Manager" wrote on 08/01/2020 > 08:32:13 AM: > > > From: Stefan Folkerts > > To: ADSM-L@VM.MARIST.EDU > >

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

nager" wrote on 08/01/2020 08:32:13 AM: > From: Stefan Folkerts > To: ADSM-L@VM.MARIST.EDU > Date: 08/01/2020 08:32 AM > Subject: [EXTERNAL] Re: AW: [ADSM-L] Move Container (Automatic) > filling up the directories > Sent by: "ADSM: Dist Stor Manager" >

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

and 90 since my last post. > > -- > Best regards / Cordialement / مع تحياتي > Erwann SIMON > > - Mail original - > De: "Erwann SIMON" > À: "ADSM: Dist Stor Manager" > Envoyé: Jeudi 6 Décembre 2018 17:32:34 > Objet: Re: [ADSM-L] AW: [ADSM

AW: [ADSM-L] SPP Security hole

Hi Steven, I can absolutely second this opinion. As a workaround, and to minimize security issues, you could instead go and do an instant access of the disk, mounting it as an additional disk to the vm, import the Volume Group/File System and restore the files manually. Not nice, but

Re: AW: [ADSM-L] anyone running SPv8.1.8 server on rhel7.8?

It was the semaphore settings: This got it back up: [root@barge ~]# sysctl -w kernel.sem="250 256000 32 16384" kernel.sem = 250 256000 32 16384 [root@barge ~]# ps -ef | grep db2 root 3494 1 0 Apr06 ?00:00:04 /opt/tivoli/tsm/db2/bin/db2fmcd root 21406 30720 0 08:56 pts/0

AW: [ADSM-L] anyone running SPv8.1.8 server on rhel7.8?

The cause could be a misconfiguration of the linux kernel SEMIPHORE settings? What is the output of "ipcs -l" The suggested settings by IBM are: kernel.sem (SEMMNI) 16384 kernel.sem (SEMMSL) 250 kernel.sem (SEMMNS) 256 000 kernel.sem (SEMOPM) 32 Regard, Uwe -Ursprüngliche Nachricht-

Re: AW: [ADSM-L] Still have issue with not able to use Scratch LV tapes

After try all things I just did checkout on the tapes that was worm and check in them again Now tsm see them as worm after I did checkin again and seems is fine. I managed to write at one of them LIBIBM3500 RDP000LV Scratch(Worm) 2,734 LTO LIBIBM3500 RDP003LV Private(Worm) ARDTSM1 Data 2,743

AW: [ADSM-L] Still have issue with not able to use Scratch LV tapes

Lucian, what was the command used for checkin that WORM Scratch tapes? Did you use "CHECKLABEL=YES"? Using LTO it is mandatory to use that parameter during checkin. https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.9/srv.solutions/c_tapeops_worm_checkin_ulw.html Regards, Uwe

AW: [ADSM-L] Scratch tapes issue

Hi, I am new in ADSM-L group. My first post. Hope it's ok when I give you a tip. Most common with not accepted scratch tapes is that the format type in the device-class definition does not match with the tapes used. If you defined your device class with format=drives the tape type must match

Re: AW: [ADSM-L] Scratch tapes issue

Hi Uwe, Yes I defined using worm yes because these new tapes are worm tapes tsm: ARDTSM1>q devcl ULTRIUM5W f=d Device Class Name: ULTRIUM5W     Device Access Strategy: Sequential     Storage Pool Count: 1    Device Type: LTO    

AW: [ADSM-L] Scratch tapes issue

Hello Lucian, can you please provide the output of "q devcl ULTRIUM5W f=d"? Did you define using Worm-Tape Format and no Worm-Tapes are available as Scratch? Regards, Uwe -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager Im Auftrag von Lucian Vlaicu Gesendet: Montag, 23. März

Re: AW: Number of volumes per client

, LinkedIn -Original Message- From: Schulz Stefan Sent: Thursday, July 11, 2019 11:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [EXTERNAL] [ADSM-L] AW: Number of volumes per client Hi Eric, i'd suggest "select node_name,count(distinct volume_name) from volumeusage group by node_name".

AW: Number of volumes per client

Hi Eric, i'd suggest "select node_name,count(distinct volume_name) from volumeusage group by node_name". You could also further filter with "where stgpool_name..." or "where copy_type='BACKUP'/'ARCHIVE'" Best Regards, Stefan Schulz CANCOM GmbH CANCOM GmbH Sitz der Gesellschaft:

AW: [ADSM-L] Living in the future, wanting to go back (date issue on Spectrum Protect server)

Hello Stefan, i assume the only solution will be 1. rename the DC node which is storing the TSM4VE data 2. create a new DC node using the old node name, and reestablish the proxy relationships 3. do a full-backup for all VMs Regards Uwe -Ursprüngliche Nachricht- Von: ADSM: Dist Stor

Re: AW: [ADSM-L] Confused about Spectrum Protect replication compatibility

Uwe, This was 100% it. The "q server" output showed transitional but the admin was strict on the 8.1 system. I did not realize that this would cause issues with a ping server and an export server command. I created a new admin, set to transtional and used the old servers dsmadmc to login to the

AW: [ADSM-L] Confused about Spectrum Protect replication compatibility

Hi Stefan, i assume the admin-id you are using during the "ping server" is running in "strict-mode" on the 8.1.7 instance, but not on the 7.1.3 instance. This will cause the error message "down level". Regards, Uwe -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager Im Auftrag von

AW: [ADSM-L] Question on switching server roles in replication

Hi Francisco, great. Thanks! Bjørn -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager Im Auftrag von Francisco Molero Gesendet: Donnerstag, 31. Januar 2019 11:43 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Question on switching server roles in replication Hi , you can

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

rigger 95 I was running with 90 and 90 since my last post. -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: "Erwann SIMON" À: "ADSM: Dist Stor Manager" Envoyé: Jeudi 6 Décembre 2018 17:32:34 Objet: Re: [ADSM-L] AW: [ADSM-L]

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

re 2018 16:05:59 Objet: Re: [ADSM-L] AW: [ADSM-L] Move Container (Automatic) filling up the directories Hello Erwann, it depends on what you want to archive. These options were implemented to reduce the fragmentation of the containers, like the good old reclamation of sequential volumes

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

Best regards / Cordialement / مع تحياتي > Erwann SIMON > > - Mail original - > De: "Michael Prix" > À: ADSM-L@VM.MARIST.EDU > Envoyé: Mercredi 14 Novembre 2018 19:25:10 > Objet: Re: [ADSM-L] AW: [ADSM-L] Move Container (Automatic) filling up the > director

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

been made at the end of august too, then I started conversion and it has just finished. -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: "Michael Prix" À: ADSM-L@VM.MARIST.EDU Envoyé: Mercredi 14 Novembre 2018 19:25:10 Objet: Re: [ADSM-L] AW:

Re: AW: [ADSM-L] Move Container (Automatic) filling up the directories

Hello, and, to tell the rest, as both server options are not documented until now, I quote my documentation from a PMR: DEFRAGFSTRIGGER 0-99 dynamic server option DEFRAGCNTRTRIGGER 0-99 dynamic server option If the percentage of free filesystem space is lower than (100-DEFRAGFSTRIGGER)

AW: [ADSM-L] Move Container (Automatic) filling up the directories

Hi Erwann, did you recently update to version 8.1.5.100, or was the convertion from sequ. Filepool to Directory Container Pool done using version 8.1.5.100? Spectrum Protect server version 8.1.5 introduced automatic container defragmentation for directory-containers. The server checks for

Aw: Re: [ADSM-L] TSM Server on RHEL Cluster

I think all of this mentions Tivoli Automation... But I just found the solution. In //sqllib/db2nodes.cfg there is the hostname configured. I replaced it with a symlink to a locally stored and correctly configured db2nodes.cfg. No TSM starts without problems on each server. Kind Regards, John

Aw: Re: [ADSM-L] TSM 6 to 7 Upgrade questions

Thank you, thats what I needed to know. Best Regards, John > Gesendet: Donnerstag, 19. Oktober 2017 um 12:56 Uhr > Von: "Marc Lanteigne" > An: ADSM-L@VM.MARIST.EDU > Betreff: Re: [ADSM-L] TSM 6 to 7 Upgrade questions > > Just to clarify this statement: “Depending on

AW: deleting a directory container

Hallo, If your command sequence happend today, you only have to wait another day and the extents should be gone. If this ist the case BUT you would like to delete the unused container(s) earlier: Try: q extentupdates if you see „Extent Reuse Delay (Days) NOT equal

Re: AW: [ADSM-L] 2 nics on tsm server.

And what does arp say? -- Sasa Drnjevic www.srce.unizg.hr On 27.7.2017. 11:54, Schneck, Dennis wrote: > Hi, > > can you connecttelnet 1500 for example > > you should see: > > Connected to . > Escape character is '^]'. > > >

AW: [ADSM-L] 2 nics on tsm server.

Hi, can you connecttelnet 1500 for example you should see: Connected to . Escape character is '^]'. Von: ADSM: Dist Stor Manager [ADSM-L@vm.marist.edu] im Auftrag von Bo Nielsen [boa...@dtu.dk] Gesendet: Donnerstag, 27. Juli 2017 11:50 An:

Re: R: [ADSM-L] AW: [ADSM-L] NOSIGN AW: Offsite access mode for container-copy volumes

PotashCorp T: (306) 933-8921 www.potashcorp.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Marco Batazzi Sent: Friday, December 02, 2016 3:43 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] R: [ADSM-L] AW: [ADSM-L] NOSIGN AW: Offsite access mode

Re: AW: [ADSM-L] NOSIGN AW: Offsite access mode for container-copy volumes

o:ADSM-L@VM.MARIST.EDU] Im Auftrag von Efim > Gesendet: Freitag, 2. Dezember 2016 09:03 > An: ADSM-L@VM.MARIST.EDU > Betreff: Re: [ADSM-L] NOSIGN AW: Offsite access mode for container-copy > volumes > > Hi > Starting from SP 7.1.7 you can use copy pools (only tapes) for protect

AW: [ADSM-L] NOSIGN AW: Offsite access mode for container-copy volumes

-Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht gestattet. -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Efim Gesendet: Freitag, 2. Dezember 2016 09:03 An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] NOSIGN AW

Re: NOSIGN AW: Offsite access mode for container-copy volumes

Hi Starting from SP 7.1.7 you can use copy pools (only tapes) for protect containers. http://www-01.ibm.com/support/docview.wss?uid=swg27048653 Efim > 2 дек. 2016 г., в 10:43, Tobias Karnat - adcon GmbH >

NOSIGN AW: Offsite access mode for container-copy volumes

Hello, The answer of development is not very helpful for small environments with basic edition (without DRM): Development has made it clear that there is no plan in the future to have the UPD VOL command change the status of container volumes to be updated to offsite. Here is the developer's

AW: [ADSM-L] Approach for fixing ANS4042E !?

Dear all, On Wed, 2016-11-16 at 11:02 +, Nachtwey, Bjoern wrote: > the language can easily set to "en_US" by a PRESCHEDCMD, so the trick is to > add just one line to the dsm.sys file: > > 1st i have to apologize, because there's a typo > PRESCHEDCMD "export LANG=en_US" Should be

AW: Decommission VM?

Hi David If you decommission a vm or node, the active version is changed to inactive and the other policy def which you have - e.g. verdel= nolimit - are still recognized. May be you still have other inactive fullvm versions of your VM somehow connected to your filespace. In any case, If

AW: Removing containers

Hallo David, i worked a lot with containers now. if the "computing environment weather" is fine also containers stg pool 1work fine. But if you have space problems, must use the overflow storage or have to reorganize to other stgpool directories, then handling containers can be a bit

AW: query occupancy command - file names

Hi Paul, try out that: select file_name from contents where volume_name in (select volume_name from volumes where stgpool_name='BKPLTO6POOL') Because data is taken out of contents table, this query may run very long. Regards Ulli Maenz -Ursprüngliche Nachricht- Von: ADSM: Dist Stor

Re: AW: TSM Replication

. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jeanne Bruno Sent: Monday, July 25, 2016 8:20 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] AW: TSM Replication Hello. Thanks Michael. Rick does this help you? (or do you think

Re: AW: TSM Replication

nal Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michael Malitz Sent: Saturday, July 23, 2016 12:52 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: TSM Replication ** THIS IS AN EXTERNAL EMAIL ** Use caution before opening links / attachments. Never sup

AW: TSM Replication

Hallo Jeanne Bruno, Try the following: on the target server: enter q replnode it's kind of a "circumvention" -- you will see the data you would like to know, but the target server indication in the output is not correct….ignore- But most important, you

Re: Aw: Re: [ADSM-L] postschedulecmd question

6-06-20 04:53:29: > From: John Keyes <ra...@gmx.net> > To: ADSM-L@VM.MARIST.EDU > Date: 2016-06-20 05:17 > Subject: Aw: Re: [ADSM-L] postschedulecmd question > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> > > I see, thank you. > It's a bummer

Aw: Re: [ADSM-L] postschedulecmd question

I see, thank you. It's a bummer really, since other backup solutions like bareos do provide a more elaborate control over post schedule events. Best regards, John > Gesendet: Donnerstag, 16. Juni 2016 um 15:46 Uhr > Von: "Pagnotta, Pamela (CONTR)" > An:

AW: All volumes in STGPOOL show as full. Please help.

Hi John, did you try a RECLAIM at the DEDUP-Pool to get the volumes free? What says an AUDIT VOLUME of the empty volumes? Are they really empty? Best regards Sabine -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Dury, John C.

AW: All volumes in STGPOOL show as full. Please help.

Manager Cc: Dury, John C. Subject: AW: All volumes in STGPOOL show as full. Please help. Hi John, did you try a RECLAIM at the DEDUP-Pool to get the volumes free? What says an AUDIT VOLUME of the empty volumes? Are they really empty? Best regards Sabine -Ursprüngliche Nachricht- Von

Re: השב: [ADSM-L] AW: Bring ba ck TSM Administr ator's Guide

.@mm-it.at> > תאריך: 12/12/2015 12:43 (GMT+02:00) > אל: ADSM-L@VM.MARIST.EDU > נושא: [ADSM-L] AW: Bring back TSM Administrator's Guide > > Agree Agree Agree!!! > > Michael Malitz > > -Ursprüngliche Nachricht- > Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM

AW: Bring back TSM Administrator's Guide

Agree Agree Agree!!! Michael Malitz -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Roger Deschner Gesendet: Samstag, 12. Dezember 2015 02:39 An: ADSM-L@VM.MARIST.EDU Betreff: Bring back TSM Administrator's Guide A great book is gone.

השב: [ADSM-L] AW: Bring back TSM Administr ator's Guide

Me too נשלח ממכשיר ה-Samsung שלי הודעה מקורית מאת: Michael Malitz <michael.mal...@mm-it.at> תאריך: 12/12/2015 12:43 (GMT+02:00) אל: ADSM-L@VM.MARIST.EDU נושא: [ADSM-L] AW: Bring back TSM Administrator's Guide Agree Agree Agree!!! Michael Malitz -Ursprün

Re: AW: How can I exclude files from dedupe processing?

Michael, Thank you for pointing out the exclude.dedup option. But this appears to only controls client-side deduplication. Wouldn't the TSM server still try to deduplicate these objects? ..Paul At 09:08 AM 8/3/2015, Michael malitz wrote: Hallo John, Paul, for client dedup, have a look

AW: How can I exclude files from dedupe processing?

Hallo John, Paul, for client dedup, have a look to exclude.dedup option And: compressed objects can also be good candidates for deduplication. Have a try and test reduction(s) Rgds Michael Malitz -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager

Re: Aw: Re: [ADSM-L] TSM TDPSQL crashes on log backup

Supposedly fixed in 7.1.3 in Q3 which might mean the end of September. When IBM blunders like this I think they could be quicker in correcting it. They should also extend their testing to something that at least faintly resembles a customer environment. Hans Chr. On Wed, Jul 29, 2015 at 4:43 PM,

Re: Aw: Re: [ADSM-L] TSM TDPSQL crashes on log backup

The alternative (which my SQL guy decided to implement) is to single-thread the backups, 1-DB-at-a-time. It is ugly (and generates lots of error messages on my TSM server) but since this version is required for 2014 server with mirrored DB's, he didn't have much of a choice. On Wed, Jul 29, 2015

Aw: Re: [ADSM-L] TSM TDPSQL crashes on log backup

Thanks for the answer. I tried the patch anyway, but as you said, it did not work. Now I downgraded to 7.1.1.1 and it works again. Best regards, John Gesendet: Mittwoch, 29. Juli 2015 um 14:33 Uhr Von: Zoltan Forray zfor...@vcu.edu An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] TSM TDPSQL

Re: AW: EXPIRE INVENTORY problem

-L@VM.MARIST.EDU Subject: [ADSM-L] AW: EXPIRE INVENTORY problem Hallo Harold, you should use the command cancel expiration instead of cancel process. With cancel expiration you have checkpointing at transaction boundaries. Rgds Michael Malitz -Ursprüngliche Nachricht- Von: ADSM: Dist

Re: AW: EXPIRE INVENTORY problem

, but not the process numberfor scripting purposes and it's the middle of the night) -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Vandeventer, Harold [OITS] Sent: Thursday, May 07, 2015 8:57 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] AW

Re: AW: EXPIRE INVENTORY problem

/ مع تحياتي Erwann SIMON - Mail original - De: Jeanne Bruno jbr...@cenhud.com À: ADSM-L@VM.MARIST.EDU Envoyé: Jeudi 7 Mai 2015 16:09:53 Objet: Re: [ADSM-L] AW: EXPIRE INVENTORY problem Hello. This is good info. Does anyone know; if there are multiple Replications happening, would

Re: AW: EXPIRE INVENTORY problem

variable) in a script wasn't working for me to cancel it. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Erwann SIMON Sent: Thursday, May 07, 2015 10:23 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] AW: EXPIRE INVENTORY problem Hi Jeanne

Re: AW: EXPIRE INVENTORY problem

, you must use the parentheses for server routing information. -- Best regards / Cordialement / مع تحياتي Erwann SIMON - Mail original - De: Jeanne Bruno jbr...@cenhud.com À: ADSM-L@VM.MARIST.EDU Envoyé: Jeudi 7 Mai 2015 17:45:50 Objet: Re: [ADSM-L] AW: EXPIRE INVENTORY problem Hello

Re: AW: EXPIRE INVENTORY problem

: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michael malitz Sent: Wednesday, May 06, 2015 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: EXPIRE INVENTORY problem Hallo Harold, you should use the command cancel expiration instead of cancel process. With cancel

Re: AW: EXPIRE INVENTORY problem

- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michael malitz Sent: Wednesday, May 06, 2015 10:17 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: EXPIRE INVENTORY problem Hallo Harold, you should use the command cancel expiration instead of cancel process. With cancel

AW: EXPIRE INVENTORY problem

Hallo Harold, you should use the command cancel expiration instead of cancel process. With cancel expiration you have checkpointing at transaction boundaries. Rgds Michael Malitz -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] Im Auftrag von Rick

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

/27/2015 03:48 AM Subject: Aw: Re: [ADSM-L] Re: [ADSM-L] Exchange Backup with Flashcopy Manager EXTREMELY slow Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Hello guys, the time for our Exchange Backups is still steadily increasing. As you can see below, a vss snapshot now takes 5

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

um 13:36 Uhr Von: Billaudeau, Pierre p.billaud...@saq.qc.ca An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] Aw: Re: [ADSM-L] Exchange Backup with Flashcopy Manager EXTREMELY slow Hi John, I had a similar situation with Exchange 2010 TSM DP backups and the reason was the VM had been

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

: 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

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.

Re: 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

AW: req: tsm db backup completed with failure and taking all scratch tapes fro DB BC

Hallo Srikanth I don't know, if somebody else already mentioned: My be a relief somehow: Change server option : ARCHLOGUSEDTHRESHOLD to 90 or 95 (default is 80) rgds Michael Malitz, MA Project Manager, PMP® IBM/Tivoli Certified Instructor (TSM ITM) Power Administrator for TSM

Aw: Re: [ADSM-L] FCM Local Backup Volumes not returned to VSS_RESERVED Host

No, I have not. Thanks a lot Del! I don't know how I did not notice that. Best regards   Gesendet: Mittwoch, 19. November 2014 um 14:22 Uhr Von: Del Hoobler hoob...@us.ibm.com An: ADSM-L@VM.MARIST.EDU Betreff: Re: [ADSM-L] FCM Local Backup Volumes not returned to VSS_RESERVED Host Hi Tom, Do

Re: AW: Defining a script that references a file

Michael, No, no one had mentioned it, and I failed to think in that wide a loop. Thanks sir. George Huebschman (George H.) The contents of this email are the property of PNC. If it was not addressed to you, you have no legal right to read it. If you think you received it in error, please

AW: Defining a script that references a file

Hallo George, i don't know, if somebody already mentioned the following: why not: 1.) Create your script input file /usr/tivoli/tsm/client/ba/bin/move.datadynamically containing the mode date commands as you already do it today! 2.) create a macro move_data.mac (one

AW: Backup job status

Hallo Mike, you could have a look to our Power Administrator for TSM Freeware version ( www.tsmpoweradmin.com), where you are able to see graphically the current and past backup/schedule status of all your backup jobs and in addition you could use our free adjustable out of the box

AW: SET DRMDBBACKUPEXPIREDAYS

Hallo Ricky, each TSM installation/environment is different, but assuming, that you do a TSM backup every day, for me, 60 days seem to be too much. I would suggest, that 7 days would be enough. But that’s also depending of course on your company's SLA prereqs/dependencies. Rgds Michael

Re: AW: SET DRMDBBACKUPEXPIREDAYS

unreasonable for any of those cases. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Michael malitz Sent: Wednesday, June 18, 2014 2:31 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: SET DRMDBBACKUPEXPIREDAYS Hallo Ricky, each TSM

AW: Manually Expire Archive

Hallo John, you are right, the classical rebinding to another Mgmtclass is not possible. May be this helps: One of the ways would be to add (temporarily) another domain to your TSM system, specify the according same policy definitions with different retentions values and just add only

AW: TSMVE Excludes

Hallo David, options specified in TSM Schedules are processed first. General precedence rule: 1. Options defined on the server with server-enforced client options. The server overrides client values. 2. Options entered locally on the command line. 3. Options defined on the

AW: AW: Tsm replication 7.1

Robert Ouzen Gesendet: Donnerstag, 1. Mai 2014 07:35 An: ADSM-L@VM.MARIST.EDU Betreff: Re: AW: Tsm replication 7.1 Hi Michael Thank you very much for the information . make more sense now. Your link is very helpful too .. I have just need another clarification about the policy retention

Re: AW: AW: Tsm replication 7.1

...@tsmpoweradmin.com Sent: Monday, May 19, 2014 1:33 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] AW: AW: Tsm replication 7.1 Hallo Robert, to answer the last part of your question: ...So if I have for a node a policy (archive) of keeping 365 days and on the TARGET server I just want to keep 60 days

AW: Replicate Node design change?

Hallo Harald, Have a try (and test) the following procedure 1.) on S2 SRS: q replnode * -- to find out all relevant nodes 2.) on S3 TRS: remove replnode nodes,group -- convert nodes to target and as result change replstate and replmode to none 3.) on S3 TRS: remove replserver

AW: Tsm replication 7.1

Hallo Robert, interesting questions: As I'm currently documenting and testing as well the node replication feature (see http://www.mm-it.at/de/TSM_Node_Replication_CMDs_Options_at_a_glance.html) I try to share my current knowledge: Domain Change on Target Replication Server:

Re: AW: Tsm replication 7.1

@VM.MARIST.EDU Subject: [ADSM-L] AW: Tsm replication 7.1 Hallo Robert, interesting questions: As I'm currently documenting and testing as well the node replication feature (see http://www.mm-it.at/de/TSM_Node_Replication_CMDs_Options_at_a_glance.html) I try to share my current knowledge

AW: Drive utilization

In addition to the other mentioned tools there exist also thePower Administrator for TSM providing information about drive utilization during certain time frames. The next PA Version 5.0 - coming out in 2 days - will extend drill down analysis of drive utilization. You will also

Re: AW: Drive utilization

If you are using IBM hardware there is a free tool for monitoring library utilization. There is also the tape portion of the TPC storage management product if your shop uses that. Regards, Steve Steven Harris TSM Admin Canberra Australia On Apr 1, 2014 5:53 AM, Michael malitz

Re: AW: TSM REPORTING and EMAILS

] De la part de Michael malitz Envoyé : jeudi 6 février 2014 08:53 À : ADSM-L@VM.MARIST.EDU Objet : [ADSM-L] AW: TSM REPORTING and EMAILS Hallo James, one alternative would be to use / test the FREEWARE version of the Power Administrator for TSM. (www.tsmpoweradmin.com) There we allow one set

  1   2   3   4   5   6   7   8   9   10   >