Re: TDP for MSSQL VSS and best practice
Hi Steven! If you are going to use the legacy backup method be sure to upgrade to 7.1.0.1 first because otherwise the legacy parameter in your tdpsql.cfg file is not processed properly. The client works but issues an error that the software is not properly configured. Kind regards, Eric van Loon AF/KLM Storage Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Steven Harris Sent: vrijdag 25 juli 2014 5:56 To: ADSM-L@VM.MARIST.EDU Subject: TDP for MSSQL VSS and best practice -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi All Having managed to finally get my customers to set up some new infrastructure with V6 TSM servers, I'm now going through the process of upgrading clients. The 5.5 TDP for SQL has long been in use, is well understood and is stable. The new TDP version 7.1 that we are moving to now has the option of VSS or legacy backups. I understand that VSS backups are essential if we need to offload backup processing or use hardware snapshots, or multiple local VSS restore points in the one day, but most of our SQL apps are small backup-in-full-once-a-day affairs. I feel inclined to continue to use legacy backup for these, mostly because of the set-up overhead and complexity for VSS. What is best practice? If you use both legacy and VSS, what criteria inform that choice? Does TSM for VE significantly affect the equation? (I don't have that yet, but the writing is on the wall) Regards Steve. Steven Harris TSM Admin, Canberra Australia. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJT0dU5AAoJENyzJ5R4j0ydwIIIAKUo6HIXeG76Q5yveRi19UnZ JNGZQTdJaUK7K915GCxTA7NlC0HL5H8E9vs889kWR1oERWDQ3C/bd7+jZQ/cPBIG rWZK4vq8hsyQPKiV0Bn4V8C/o/kiOIRc8pg5V/lqvP14bbYKC29zMbwQysT+gXkZ gOICtZommjeNphA0xeve1x0abdhorqATk97xmsbdPI59JGIcG1fU4aUhsCABSY/P T0soM6XsBqZGw43Pzht2R6Ky5S7OSUhiYQgMWLCzbHCBAVgWxO+slOK/8jciZr9L C85KGMIcO+k+HBAPZIPZ8hLmM+l7K7biUhbPCgF33WryXeTbLZH94mg/ymH2rmE= =gl+l -END PGP SIGNATURE- For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch Airlines) is registered in Amstelveen, The Netherlands, with registered number 33014286
TSM journal backup setup fails.
Hallo Guys, I am trying to configure a TSM Jbb backup on linux, I get following errors after I start jbb service. 07/28/2014 15:11:46 ANS0361I DIAG: startJbbThread(): FS Monitor Thread initialization failed, rc=18 07/28/2014 15:15:14 Version 6, Release 4, Level 1.7 Last Update: Jan 23 2014 /opt/tivoli/tsm/client/ba/bin/tsmjbbd, /opt/tivoli/tsm/client/ba/bin, Prefs file: /opt/tivoli/tsm/client/ba/bin/tsmjbbd.ini, Journal dir: /SZIR/data/journaldbs 2 File System(s) specified for Journaling: /PALD /PALD/vhosts/backup 07/28/2014 15:15:17 ANS0361I DIAG: openMonitorDir(): PF_OpenDriver RC=5003 . The device driver could not be opened 07/28/2014 15:15:17 ANS0361I DIAG: initReadFsChangesInfo(): Error opening '/PALD'. 07/28/2014 15:15:17 ANS0361I DIAG: FsMonitorThreadInit(): Error opening fs '/PALD' for change monitoring . 07/28/2014 15:15:17 ANS0361I DIAG: tsMonitorThreadInit(): FsMonitorThreadInit() failed. 07/28/2014 15:15:17 ANS0361I DIAG: startJbbThread(): FS Monitor Thread initialization failed, rc=18 07/28/2014 15:15:17 ANS0361I DIAG: openMonitorDir(): PF_OpenDriver RC=5003 . The device driver could not be opened 07/28/2014 15:15:17 ANS0361I DIAG: initReadFsChangesInfo(): Error opening '/PALD/vhosts/backup'. 07/28/2014 15:15:17 ANS0361I DIAG: FsMonitorThreadInit(): Error opening fs '/PALD/vhosts/backup' for change monitoring . 07/28/2014 15:15:17 ANS0361I DIAG: tsMonitorThreadInit(): FsMonitorThreadInit() failed. 07/28/2014 15:15:17 ANS0361I DIAG: startJbbThread(): FS Monitor Thread initialization failed, rc=18 My tsmjbb.ini file is Errorlog=/WORK/TMP/Jbberror.log Journaldir=/SZIR/data/journaldbs [JournalExcludeList] ; Note that this list contains the journal database files. *.jdb.jbbdb *.jdbInc.jbbdb [JournaledFileSystemSettings] JournaledFileSystems=/PALD /PALD/vhosts/backup ; Override stanza for /PALD /PALD/vhosts/backup [JournaledFileSystemSettings./PALD] JournalDir=/otherfs/tsmjournal PreserveDBOnExit=1 DeferFsMonStart=1 DeferRetryInterval=2 logFsErrors=1 + [root@degtlu bin]# rpm -qa |grep -i tiv TIVsm-API64-6.4.1-7.x86_64 TIVsm-filepath-6.4.1-0.x86_64 tivoli-1.0.0-1.noarch TIVsm-JBB-6.4.1-7.x86_64 TIVsm-BA-6.4.1-7.x86_64 Any Ideas!!! Grüße Vikas Arora *e Mail* : vikar...@gmail.com
ISILON backing up directly to TSM server.
Good Morning All, I have an ISILON that is backing up directly to a TSM server. The library is mounted to the TSM server, not the ISILON. My question is, I have a stgpool created that the data format was NAS but, I had to change the data format to NATIVE to get the backup to work. Now, when you perform a q vol * stg=naspool, the tapes all say empty even though the backup has been running for a while. Any ideas on how to see the information assigned to these tapes? tsm: SERVER1q vol * stg=naspool Volume Name Storage Device EstimatedPct Volume Pool NameClass Name Capacity Util Status --- -- - - 23L4 NASPOOL LTO40.0 M0.0 Empty 26L4 NASPOOL LTO40.0 M0.0 Empty 33L4 NASPOOL LTO40.0 M0.0 Empty 000101L4 NASPOOL LTO40.0 M0.0 Empty 000157L4 NASPOOL LTO40.0 M0.0 Empty 000823L4 NASPOOL LTO40.0 M0.0 Empty 000843L4 NASPOOL LTO40.0 M0.0 Empty 000846L4 NASPOOL LTO40.0 M0.0 Empty 000850L4 NASPOOL LTO40.0 M0.0 Empty L00660L4 NASPOOL LTO40.0 M0.0 Empty L00665L4 NASPOOL LTO40.0 M0.0 Empty L00678L4 NASPOOL LTO40.0 M0.0 Empty L00693L4 NASPOOL LTO40.0 M0.0 Empty L00700L4 NASPOOL LTO40.0 M0.0 Empty L00705L4 NASPOOL LTO40.0 M0.0 Empty L00720L4 NASPOOL LTO40.0 M0.0 Empty L00804L4 NASPOOL LTO40.0 M0.0 Empty L00974L4 NASPOOL LTO40.0 M0.0 Empty L00988L4 NASPOOL LTO40.0 M0.0 Empty L01231L4 NASPOOL LTO40.0 M0.0 Empty _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ CONFIDENTIALITY NOTICE: This email message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information and/or Protected Health Information (PHI) subject to protection under the law, including the Health Insurance Portability and Accountability Act of 1996, as amended (HIPAA). If you are not the intended recipient or the person responsible for delivering the email to the intended recipient, be advised that you have received this email in error and that any use, disclosure, distribution, forwarding, printing, or copying of this email is strictly prohibited. If you have received this email in error, please notify the sender immediately and destroy all copies of the original message.
TSM DB replication
Where is the most current documentation for setting up DB2 replication for the TSM DB to keep an DR instance of TSM in-sync with a production TSM? David
deduplication status
I've searched the archives but I can't really find the answer I'm looking for. Running on version 6.3.1.0. I have a primary storage pool running dedup. I run the ID DEDUP command, the reclamation command, and the expiration command throughout the daily cycle. I run the Q STGP F=D command to check the Duplicate Data Not Stored numbers and I'm getting 39% right now. Which sounds pretty good, I guess. My question is how to I tell if I'm running the dedup processes aggressively enough. Can I do something to increase that number? I realize that the dedup processes are never really finished because of the new data that is constantly coming in and old data is getting expired. Is there something I can look at to be able to tell if I need to adjust the ID DUP commands I'm running? More processes, less processes or change how long I run it... Something that tells me how much data has not been deduped yet versus how much has been processed. Is that kind of info accessible? David Tyree System Administrator South Georgia Medical Center 229.333.1155
Re: tsm for ve question
Hi Keith, FULLvm and FIle are only for VMware. Details on what they do in a VMware environment can be found here: http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.doc/c_bac_usingvcb.html For Hyper-V, as of today, HYPERVFULL is the only option available for VMBACKUPType. This is a FULL VM VSS-based backup. Look here on the functions/features of this: http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.doc/c_bac_hyperv.html Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/27/2014 11:00:16 AM: From: Arbogast, Warren K warbo...@iu.edu To: ADSM-L@vm.marist.edu Date: 07/27/2014 11:00 AM Subject: Re: tsm for ve question Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Hi Gary and Del; The TSM 7.1 Backup Archive Guide for Windows includes HYPERVFULL, along with FIle and FUllvm, in the possible arguments for the VMBACKUPType option. The description says it is Required for Hyper- V systems. Specified a full virtual machine backup of all virtual machines that are defined on the Hyper-V host machine. Del: Since this implies that hyper-v is already supported, at least in part, could you say more about what is and what is not supported for hyper-v backups? With many thanks, Keith Arbogast Indiana University
Re: tsm for ve question
I submitted an RFE related to this in May of 2013. You can see it here: http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfeCR_ID=34722 Ray Storer NIBCO INC. 574.295.3457 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: Monday, July 28, 2014 12:20 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] tsm for ve question Hi Keith, FULLvm and FIle are only for VMware. Details on what they do in a VMware environment can be found here: http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.doc/c_bac_usingvcb.html For Hyper-V, as of today, HYPERVFULL is the only option available for VMBACKUPType. This is a FULL VM VSS-based backup. Look here on the functions/features of this: http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.0/com.ibm.itsm.client.doc/c_bac_hyperv.html Thank you, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/27/2014 11:00:16 AM: From: Arbogast, Warren K warbo...@iu.edu To: ADSM-L@vm.marist.edu Date: 07/27/2014 11:00 AM Subject: Re: tsm for ve question Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Hi Gary and Del; The TSM 7.1 Backup Archive Guide for Windows includes HYPERVFULL, along with FIle and FUllvm, in the possible arguments for the VMBACKUPType option. The description says it is Required for Hyper- V systems. Specified a full virtual machine backup of all virtual machines that are defined on the Hyper-V host machine. Del: Since this implies that hyper-v is already supported, at least in part, could you say more about what is and what is not supported for hyper-v backups? With many thanks, Keith Arbogast Indiana University CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
Re: TSM journal backup setup fails.
See if the advice given in the following technote helps. It mentions it is for AIX but the same could apply to Linux. http://www.ibm.com/support/docview.wss?uid=swg21372961 Best regards, - Andy Andrew Raibeck | Tivoli Storage Manager Level 3 Technical Lead | stor...@us.ibm.com IBM Tivoli Storage Manager links: Product support: http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Storage_Manager Online documentation: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Documentation+Central/page/Tivoli+Storage+Manager Product Wiki: https://www.ibm.com/developerworks/mydeveloperworks/wikis/home/wiki/Tivoli +Storage+Manager/page/Home ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 2014-07-28 09:25:12: From: Vikas Arora vikar...@gmail.com To: ADSM-L@vm.marist.edu Date: 2014-07-28 09:26 Subject: TSM journal backup setup fails. Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Hallo Guys, I am trying to configure a TSM Jbb backup on linux, I get following errors after I start jbb service. 07/28/2014 15:11:46 ANS0361I DIAG: startJbbThread(): FS Monitor Thread initialization failed, rc=18 07/28/2014 15:15:14 Version 6, Release 4, Level 1.7 Last Update: Jan 23 2014 /opt/tivoli/tsm/client/ba/bin/tsmjbbd, /opt/tivoli/tsm/client/ba/bin, Prefs file: /opt/tivoli/tsm/client/ba/bin/tsmjbbd.ini, Journal dir: /SZIR/data/journaldbs 2 File System(s) specified for Journaling: /PALD /PALD/vhosts/backup 07/28/2014 15:15:17 ANS0361I DIAG: openMonitorDir(): PF_OpenDriver RC=5003 . The device driver could not be opened 07/28/2014 15:15:17 ANS0361I DIAG: initReadFsChangesInfo(): Error opening '/PALD'. 07/28/2014 15:15:17 ANS0361I DIAG: FsMonitorThreadInit(): Error opening fs '/PALD' for change monitoring . 07/28/2014 15:15:17 ANS0361I DIAG: tsMonitorThreadInit(): FsMonitorThreadInit() failed. 07/28/2014 15:15:17 ANS0361I DIAG: startJbbThread(): FS Monitor Thread initialization failed, rc=18 07/28/2014 15:15:17 ANS0361I DIAG: openMonitorDir(): PF_OpenDriver RC=5003 . The device driver could not be opened 07/28/2014 15:15:17 ANS0361I DIAG: initReadFsChangesInfo(): Error opening '/PALD/vhosts/backup'. 07/28/2014 15:15:17 ANS0361I DIAG: FsMonitorThreadInit(): Error opening fs '/PALD/vhosts/backup' for change monitoring . 07/28/2014 15:15:17 ANS0361I DIAG: tsMonitorThreadInit(): FsMonitorThreadInit() failed. 07/28/2014 15:15:17 ANS0361I DIAG: startJbbThread(): FS Monitor Thread initialization failed, rc=18 My tsmjbb.ini file is Errorlog=/WORK/TMP/Jbberror.log Journaldir=/SZIR/data/journaldbs [JournalExcludeList] ; Note that this list contains the journal database files. *.jdb.jbbdb *.jdbInc.jbbdb [JournaledFileSystemSettings] JournaledFileSystems=/PALD /PALD/vhosts/backup ; Override stanza for /PALD /PALD/vhosts/backup [JournaledFileSystemSettings./PALD] JournalDir=/otherfs/tsmjournal PreserveDBOnExit=1 DeferFsMonStart=1 DeferRetryInterval=2 logFsErrors=1 + [root@degtlu bin]# rpm -qa |grep -i tiv TIVsm-API64-6.4.1-7.x86_64 TIVsm-filepath-6.4.1-0.x86_64 tivoli-1.0.0-1.noarch TIVsm-JBB-6.4.1-7.x86_64 TIVsm-BA-6.4.1-7.x86_64 Any Ideas!!! Grüße Vikas Arora *e Mail* : vikar...@gmail.com
Re: deduplication status
39 is actually not a great number; it means you are getting less than 2 for 1 dedup. Unless you have backups running hard 24 hours a day, those dedup processes should finish. When you do Q PROC, if the processes have any work to do, they show as ACTIVE, if not they show IDLE. I'd think that at some point during the day, you should have at least one of them go idle, then you know you have been as aggressive as you can be. If not I'd add processes until you can see some idle time on at least one of them. Just my 2cents. W -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Tyree, David Sent: Monday, July 28, 2014 11:42 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] deduplication status I've searched the archives but I can't really find the answer I'm looking for. Running on version 6.3.1.0. I have a primary storage pool running dedup. I run the ID DEDUP command, the reclamation command, and the expiration command throughout the daily cycle. I run the Q STGP F=D command to check the Duplicate Data Not Stored numbers and I'm getting 39% right now. Which sounds pretty good, I guess. My question is how to I tell if I'm running the dedup processes aggressively enough. Can I do something to increase that number? I realize that the dedup processes are never really finished because of the new data that is constantly coming in and old data is getting expired. Is there something I can look at to be able to tell if I need to adjust the ID DUP commands I'm running? More processes, less processes or change how long I run it... Something that tells me how much data has not been deduped yet versus how much has been processed. Is that kind of info accessible? David Tyree System Administrator South Georgia Medical Center 229.333.1155
