Restoring backedup data in TSM
Hi all, I have backup some files in a local direcotry from TSM and got a image file 0165.bfs. Now i want to restore all those files from this 0165.bfs . when i am using dsmc restore command it is simply giving me back 0165.bfs . I want to have original files not the image itself. Can anybody help me in this ?? +-- |This was sent by devesh.gu...@nechclst.in via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Flashcopy manager
Okay, it's clear to me now. Thank you very much :) +-- |This was sent by koekiesfre...@hotmail.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Hi TSM-ers! Here is a small follow up on my PMR about the recovery log utilization. I'm at TSM level 2, still trying to convince them that there is something broken in the TSM server code. To convince them, I have changed the logmode to normal on one of my servers. I created a graph (through TSMManager) which shows the recovery log utilization during last night's client backup window and is doesn't differ much from the night before, with logmode rollforward. When running in normal mode, TSM should only use the recovery log for uncommitted transactions, so utilization should be very low. My log is 12 Gb and the backuptrigger value (75%) was still hit twice! This clearly shows that there is something wrong with TSM, let's hope I can convince Level 2 too, so my case gets forwarded to the lab. I'll keep you guys posted! Kind regards, Eric van Loon KLM Royal Dutch Airlines 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
What are you seeing for tape speeds?
Can anyone comment on what kind of speeds you are seeing on LTO-5 tape drives? Any information is much appreciated. Gary
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
I believe we've been seeing this problem as well. One night in the busiest backup period, I issued a q actlog begint=now-00:30, and got no results back but an error. I started dsmadmc -console on that server, and could see that the console output was most of an hour behind. (And the console output was scrolling so fast that it could barely be read.) In that case, I think we determined that SQL LiteSpeed was set to some rediculously small transaction size, and this was causing way too many actlog entries. I think I also noted that the session number incremented by something like 100,000 in an hour. Asking the users of SQL LiteSpeed to make some changes was enough to rememdy this problem, although we continue to fight with the logs getting full. Thanks, [RC] From: Loon, EJ van - SPLXO eric-van.l...@klm.com To: ADSM-L@VM.MARIST.EDU Date: 05/11/2011 02:05 AM Subject:Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Hi TSM-ers! Here is a small follow up on my PMR about the recovery log utilization. I'm at TSM level 2, still trying to convince them that there is something broken in the TSM server code. To convince them, I have changed the logmode to normal on one of my servers. I created a graph (through TSMManager) which shows the recovery log utilization during last night's client backup window and is doesn't differ much from the night before, with logmode rollforward. When running in normal mode, TSM should only use the recovery log for uncommitted transactions, so utilization should be very low. My log is 12 Gb and the backuptrigger value (75%) was still hit twice! This clearly shows that there is something wrong with TSM, let's hope I can convince Level 2 too, so my case gets forwarded to the lab. I'll keep you guys posted! Kind regards, Eric van Loon KLM Royal Dutch Airlines 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 U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. -
restore question
Hello. Wondering if anyone else has ever seen this scenario: We had a 2003 windows server that died last week. Got a new 2008 server this week. Did the restore for the 'user' drive for all their data. (Used the TSM gui to do the restore. TSM client version 6.1.2). But during the restore about 4 hours into it, we got the prompt to 'replace the existing file?' message for one of the files that was being restored. Now because this is a brand new server that never had any user data on it, why would we get prompted this message? Before we started the restore, we did not choose any of the restore options for the replacing,etc, because it was a brand new server, i didn't think this was necessary to do. anyone know why this happened?? thanks. Jeannie Bruno Systems Analyst jbr...@cenhud.com 284 South Ave. Poughkeepsie, NY 12601 845-486-5780 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. Thank you.
Re: restore question
It sounds as though an older version of a file was restored, then later a newer version of the same file was attempted. Were you doing a Point in Time restore? -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jeannie Bruno Sent: Wednesday, May 11, 2011 10:21 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] restore question Hello. Wondering if anyone else has ever seen this scenario: We had a 2003 windows server that died last week. Got a new 2008 server this week. Did the restore for the 'user' drive for all their data. (Used the TSM gui to do the restore. TSM client version 6.1.2). But during the restore about 4 hours into it, we got the prompt to 'replace the existing file?' message for one of the files that was being restored. Now because this is a brand new server that never had any user data on it, why would we get prompted this message? Before we started the restore, we did not choose any of the restore options for the replacing,etc, because it was a brand new server, i didn't think this was necessary to do. anyone know why this happened?? thanks. Jeannie Bruno Systems Analyst jbr...@cenhud.com 284 South Ave. Poughkeepsie, NY 12601 845-486-5780 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. Thank you. IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
Re: licensing question
-David Tyree wrote: - We are thinking about adding an additional TSM server to our environment to use for an offsite DR. Basically we would duplicate our onsite data to the new offsite TSM server. How would we go about licensing for the additional server? Or does it matter? There doesn't seem to be any source for authoritative answers to most questions about TSM licensing. However, my best guess is as follows: You will need value units for the system hosting the new offsite server, unless you already have the system licensed for some reason. You will need the same number of value units you would need if you going to install TSM client software on the same hardware and have it send backups to an existing TSM server. You will not need any additional value units for the client systems that have backups stored on one TSM server now and will have backups stored on two TSM servers in the future.
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Hi Robert! Thanks you very much for your reply! Several others on this list reported this behavior and (as far as I know) three other users opened a PMR too. I hope they have more luck, because I'm stuck. Level 2 keeps on saying that the log keeps on growing because of slow running client sessions. Indeed I see slow running client sessions, but they are slowed down by the fact that TSM is delaying all transactions because the log is used for more that 80% during a large part of the backup window! Now they refuse to help me, unless I buy a Passport Advantage contract!! Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Clark Sent: woensdag 11 mei 2011 16:05 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code I believe we've been seeing this problem as well. One night in the busiest backup period, I issued a q actlog begint=now-00:30, and got no results back but an error. I started dsmadmc -console on that server, and could see that the console output was most of an hour behind. (And the console output was scrolling so fast that it could barely be read.) In that case, I think we determined that SQL LiteSpeed was set to some rediculously small transaction size, and this was causing way too many actlog entries. I think I also noted that the session number incremented by something like 100,000 in an hour. Asking the users of SQL LiteSpeed to make some changes was enough to rememdy this problem, although we continue to fight with the logs getting full. Thanks, [RC] From: Loon, EJ van - SPLXO eric-van.l...@klm.com To: ADSM-L@VM.MARIST.EDU Date: 05/11/2011 02:05 AM Subject:Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Hi TSM-ers! Here is a small follow up on my PMR about the recovery log utilization. I'm at TSM level 2, still trying to convince them that there is something broken in the TSM server code. To convince them, I have changed the logmode to normal on one of my servers. I created a graph (through TSMManager) which shows the recovery log utilization during last night's client backup window and is doesn't differ much from the night before, with logmode rollforward. When running in normal mode, TSM should only use the recovery log for uncommitted transactions, so utilization should be very low. My log is 12 Gb and the backuptrigger value (75%) was still hit twice! This clearly shows that there is something wrong with TSM, let's hope I can convince Level 2 too, so my case gets forwarded to the lab. I'll keep you guys posted! Kind regards, Eric van Loon KLM Royal Dutch Airlines 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 U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - 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,
Re: licensing question
In general the way I understand this would work is that if you are using server to server to send data to the remote TSM server, then you will need to license it. If it is just sitting waiting for a DB restore and moving of tapes, then it does not need to be licensed. It falls back to the active/passive active/active philosophy, similar to clustering the TSM server. If they are both active at the same time, then you need licenses. Hope this helps. Gary Bowers Itrus Technologies On May 11, 2011, at 9:57 AM, Thomas Denier wrote: -David Tyree wrote: - We are thinking about adding an additional TSM server to our environment to use for an offsite DR. Basically we would duplicate our onsite data to the new offsite TSM server. How would we go about licensing for the additional server? Or does it matter? There doesn't seem to be any source for authoritative answers to most questions about TSM licensing. However, my best guess is as follows: You will need value units for the system hosting the new offsite server, unless you already have the system licensed for some reason. You will need the same number of value units you would need if you going to install TSM client software on the same hardware and have it send backups to an existing TSM server. You will not need any additional value units for the client systems that have backups stored on one TSM server now and will have backups stored on two TSM servers in the future.
Re: restore question
Happens rarely, but I've seen it before. Freaked me out. Has to do with how Windows creates the under-the-covers 8.3 DOS file names. TSM backs up and catalogs the filenames with the long-name version, but when it restores the file, NTFS will still create the 8.3 filenames by default. Here's how it can happen: Suppose you have files called whoop~1.txt whoopee2001.txt If whoopee2001.txt gets restored first (totally by accident), NTFS will create the short name whoop~1.txt for it. Then when it tries to restore whoop~1.txt, you get the error message you saw, i.e. a file name clash. (And as I recall, the error message may use the long file name, so it's not necessarily apparent what the problem is.) You have to have files of just the right names, just the right length names, in the same directory, and an accident of restore order to make it happen, so you rarely see it. (It's most likely to occur in directories where files are generated by a software package where some developer has brilliantly decided to use a lot of ~ in the generated filenames, so you may be able to identify exactly which directory has the issue.) Simple solutions: -If it only happens on 1 or 2 files, be confident that TSM is OK, write the file name down. After you've finished the big restore, go back and find those files in TSM and restore them to different directories, then drag them back to where they belong. -If it happens a lot and you are nervous about the results, or your restore needs to run a long time unattended, you can disable Windows NTFS 8.3 name creation, run your restore, then re-enable the NTFS 8.3 name creation. (The downside of that is if you have users that for some reason regularly refer to the short 8.3 form of the file name -- again most likely program developers -- they may have some patching to do after the restore.) Here are references that may explain it better and help you determine if this is your problem. The MS article has instructions for turning off 8.3 filename creation: https://www-304.ibm.com/support/docview.wss?uid=swg21304777 https://www-304.ibm.com/support/docview.wss?uid=swg1IC45443 http://support.microsoft.com/kb/121007 http://support.microsoft.com/kb/121007 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jeannie Bruno Sent: Wednesday, May 11, 2011 10:21 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] restore question Hello. Wondering if anyone else has ever seen this scenario: We had a 2003 windows server that died last week. Got a new 2008 server this week. Did the restore for the 'user' drive for all their data. (Used the TSM gui to do the restore. TSM client version 6.1.2). But during the restore about 4 hours into it, we got the prompt to 'replace the existing file?' message for one of the files that was being restored. Now because this is a brand new server that never had any user data on it, why would we get prompted this message? Before we started the restore, we did not choose any of the restore options for the replacing,etc, because it was a brand new server, i didn't think this was necessary to do. anyone know why this happened?? thanks. Jeannie Bruno Systems Analyst jbr...@cenhud.com 284 South Ave. Poughkeepsie, NY 12601 845-486-5780 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. Thank you.
Re: restore question
thanks! Our tech support didn't write down the file name and I believe it was only 1 file, but I will ask if he happens to remember the name. And I will check out those sites. - Original Message - From: Prather, Wanda wprat...@icfi.com To: ADSM-L@VM.MARIST.EDU Sent: Wednesday, May 11, 2011 12:32 PM Subject: Re: [ADSM-L] restore question Happens rarely, but I've seen it before. Freaked me out. Has to do with how Windows creates the under-the-covers 8.3 DOS file names. TSM backs up and catalogs the filenames with the long-name version, but when it restores the file, NTFS will still create the 8.3 filenames by default. Here's how it can happen: Suppose you have files called whoop~1.txt whoopee2001.txt If whoopee2001.txt gets restored first (totally by accident), NTFS will create the short name whoop~1.txt for it. Then when it tries to restore whoop~1.txt, you get the error message you saw, i.e. a file name clash. (And as I recall, the error message may use the long file name, so it's not necessarily apparent what the problem is.) You have to have files of just the right names, just the right length names, in the same directory, and an accident of restore order to make it happen, so you rarely see it. (It's most likely to occur in directories where files are generated by a software package where some developer has brilliantly decided to use a lot of ~ in the generated filenames, so you may be able to identify exactly which directory has the issue.) Simple solutions: -If it only happens on 1 or 2 files, be confident that TSM is OK, write the file name down. After you've finished the big restore, go back and find those files in TSM and restore them to different directories, then drag them back to where they belong. -If it happens a lot and you are nervous about the results, or your restore needs to run a long time unattended, you can disable Windows NTFS 8.3 name creation, run your restore, then re-enable the NTFS 8.3 name creation. (The downside of that is if you have users that for some reason regularly refer to the short 8.3 form of the file name -- again most likely program developers -- they may have some patching to do after the restore.) Here are references that may explain it better and help you determine if this is your problem. The MS article has instructions for turning off 8.3 filename creation: https://www-304.ibm.com/support/docview.wss?uid=swg21304777 https://www-304.ibm.com/support/docview.wss?uid=swg1IC45443 http://support.microsoft.com/kb/121007 http://support.microsoft.com/kb/121007 -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Jeannie Bruno Sent: Wednesday, May 11, 2011 10:21 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] restore question Hello. Wondering if anyone else has ever seen this scenario: We had a 2003 windows server that died last week. Got a new 2008 server this week. Did the restore for the 'user' drive for all their data. (Used the TSM gui to do the restore. TSM client version 6.1.2). But during the restore about 4 hours into it, we got the prompt to 'replace the existing file?' message for one of the files that was being restored. Now because this is a brand new server that never had any user data on it, why would we get prompted this message? Before we started the restore, we did not choose any of the restore options for the replacing,etc, because it was a brand new server, i didn't think this was necessary to do. anyone know why this happened?? thanks. Jeannie Bruno Systems Analyst jbr...@cenhud.com 284 South Ave. Poughkeepsie, NY 12601 845-486-5780 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. Thank you.
Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code
Hi folks, if this has already been commented on, my apologies, I hvaen't been following closely but just noticed this thread. We were experiencing log pinned issues after upgrading to 5.5.0.0 code at one of my client sites. What we were finding was that, occasionally, I'd get up in the morning and look at the server to see it completely bogged down with a huge number of backups still attempting to run, but nothing was moving - the log was at 84% (over it's trigger), and it had been firing off db backups for the last 4h to no avail, the log wasn't getting low enough. A key symptom was that in the actlog we were seeing messages to the effect of Recovery log is at 84%, transactions will be delayed by 3ms (or something like that). In opening a ticket, it was found there was an issue in the 5.5.0.0 code where, when the recovery log gets too full, it would start delaying transactions in order to prevent the log from filling too quickly. However, the side effect was that the pinning transaction would also get delayed, causing a bit of a never-ending loop. Transactions keep getting delayed, pinned transaction never gets to finish, and everything would just grind to a halt. I would have to halt the server and restart in order to get things back to normal. IBM recognized this as an issue and recommended going to any 5.5.5.0 level of code, where the problem was supposed to be fixed. I installed 5.5.5.2, and the problem has indeed gone away. It was supposed to be fixed at 5.5.5.0, though perhaps they didn't quite get it done at that code level as they hoped? I'd try installing 5.5.5.2 and see what happens regards, Paul On Wed, May 11, 2011 at 9:03 AM, Loon, EJ van - SPLXO eric-van.l...@klm.com wrote: Hi Robert! Thanks you very much for your reply! Several others on this list reported this behavior and (as far as I know) three other users opened a PMR too. I hope they have more luck, because I'm stuck. Level 2 keeps on saying that the log keeps on growing because of slow running client sessions. Indeed I see slow running client sessions, but they are slowed down by the fact that TSM is delaying all transactions because the log is used for more that 80% during a large part of the backup window! Now they refuse to help me, unless I buy a Passport Advantage contract!! Kind regards, Eric van Loon KLM Royal Dutch Airlines -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Robert Clark Sent: woensdag 11 mei 2011 16:05 To: ADSM-L@VM.MARIST.EDU Subject: Re: TSM Recovery log is pinning since upgrade to 5.5.5.0 code I believe we've been seeing this problem as well. One night in the busiest backup period, I issued a q actlog begint=now-00:30, and got no results back but an error. I started dsmadmc -console on that server, and could see that the console output was most of an hour behind. (And the console output was scrolling so fast that it could barely be read.) In that case, I think we determined that SQL LiteSpeed was set to some rediculously small transaction size, and this was causing way too many actlog entries. I think I also noted that the session number incremented by something like 100,000 in an hour. Asking the users of SQL LiteSpeed to make some changes was enough to rememdy this problem, although we continue to fight with the logs getting full. Thanks, [RC] From: Loon, EJ van - SPLXO eric-van.l...@klm.com To: ADSM-L@VM.MARIST.EDU Date: 05/11/2011 02:05 AM Subject:Re: [ADSM-L] TSM Recovery log is pinning since upgrade to 5.5.5.0 code Sent by:ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Hi TSM-ers! Here is a small follow up on my PMR about the recovery log utilization. I'm at TSM level 2, still trying to convince them that there is something broken in the TSM server code. To convince them, I have changed the logmode to normal on one of my servers. I created a graph (through TSMManager) which shows the recovery log utilization during last night's client backup window and is doesn't differ much from the night before, with logmode rollforward. When running in normal mode, TSM should only use the recovery log for uncommitted transactions, so utilization should be very low. My log is 12 Gb and the backuptrigger value (75%) was still hit twice! This clearly shows that there is something wrong with TSM, let's hope I can convince Level 2 too, so my case gets forwarded to the lab. I'll keep you guys posted! Kind regards, Eric van Loon KLM Royal Dutch Airlines 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
Management class assigned to Domino backups
Is there a way to list the management class a particular Domino mailbox backup is assigned? I need to verify that specific mailbox backups are assigned to a different management class than DEFAULT which has a longer retention policy. For remediation. The GUI for restore doesn't list that as a column. TIA, Bill
Re: Management class assigned to Domino backups
select hl_name, ll_name, class_name from backups where node_name='DOMINO-CLIENT-NAME-ALLCAPS' You'll get better performance if you can also specify ... and filespace_name='blah' but I don't' know how those are named for Domino -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill Boyer Sent: Wednesday, May 11, 2011 2:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Management class assigned to Domino backups Is there a way to list the management class a particular Domino mailbox backup is assigned? I need to verify that specific mailbox backups are assigned to a different management class than DEFAULT which has a longer retention policy. For remediation. The GUI for restore doesn't list that as a column. TIA, Bill
Re: Management class assigned to Domino backups
I was hoping to not have to query the BACKUPS table. Even using a key column it runs slow at best. I could always try connecting at the Domino nodename with the client an -VIRTUALNODE=, then doing a QUERY BACKUP. That works with Oracle RMAN and SQLServer nodes. Haven't tried it on a Domino node, yet. Always a first time... You remember the last TSMUG meeting I was discussing a client that was implementing the Cybernetics VTL dedupe unit? Well, they're still trying to implement it! No Schmidt. It still doesn't work worth a darn with TSM. They are actually trying to write new firmware code to try and get around some of the limitations they've found using TSM. Wish I could make it next week to the TSMUG meeting. Sounds like some interesting topics. We have a coworker out and he's got some big shoes to be filled. Had a major heart attack last weekend. Only a couple years older than me! Yikes!!! Bill -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Wednesday, May 11, 2011 2:51 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Management class assigned to Domino backups select hl_name, ll_name, class_name from backups where node_name='DOMINO-CLIENT-NAME-ALLCAPS' You'll get better performance if you can also specify ... and filespace_name='blah' but I don't' know how those are named for Domino -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill Boyer Sent: Wednesday, May 11, 2011 2:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Management class assigned to Domino backups Is there a way to list the management class a particular Domino mailbox backup is assigned? I need to verify that specific mailbox backups are assigned to a different management class than DEFAULT which has a longer retention policy. For remediation. The GUI for restore doesn't list that as a column. TIA, Bill
Re: Management class assigned to Domino backups
Yep, connecting as a BA client to the domino node works and will give you what you need. On Wed, 11 May 2011 15:34:17 -0400, Bill Boyer bjdbo...@comcast.net wrote: I was hoping to not have to query the BACKUPS table. Even using a key column it runs slow at best. I could always try connecting at the Domino nodename with the client an -VIRTUALNODE=, then doing a QUERY BACKUP. That works with Oracle RMAN and SQLServer nodes. Haven't tried it on a Domino node, yet. Always a first time... You remember the last TSMUG meeting I was discussing a client that was implementing the Cybernetics VTL dedupe unit? Well, they're still trying to implement it! No Schmidt. It still doesn't work worth a darn with TSM. They are actually trying to write new firmware code to try and get around some of the limitations they've found using TSM. Wish I could make it next week to the TSMUG meeting. Sounds like some interesting topics. We have a coworker out and he's got some big shoes to be filled. Had a major heart attack last weekend. Only a couple years older than me! Yikes!!! Bill -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Wednesday, May 11, 2011 2:51 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Management class assigned to Domino backups select hl_name, ll_name, class_name from backups where node_name='DOMINO-CLIENT-NAME-ALLCAPS' You'll get better performance if you can also specify ... and filespace_name='blah' but I don't' know how those are named for Domino -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Bill Boyer Sent: Wednesday, May 11, 2011 2:43 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Management class assigned to Domino backups Is there a way to list the management class a particular Domino mailbox backup is assigned? I need to verify that specific mailbox backups are assigned to a different management class than DEFAULT which has a longer retention policy. For remediation. The GUI for restore doesn't list that as a column. TIA, Bill
Re: Management class assigned to Domino backups
The windows native gui does not have this column, but you can choose the 'nsf view' from the backup archive's client gui and it does. If you are running an older backup archive client gui, say 5.5.3, you can see this same view from the web client. Frank Ramke From: Bill Boyer bjdbo...@comcast.net To: ADSM-L@vm.marist.edu Date: 05/11/2011 02:47 PM Subject:Management class assigned to Domino backups Sent by:ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Is there a way to list the management class a particular Domino mailbox backup is assigned? I need to verify that specific mailbox backups are assigned to a different management class than DEFAULT which has a longer retention policy. For remediation. The GUI for restore doesn't list that as a column. TIA, Bill
Question about Hybrid method upgrade to TSM V6.2.2 and server-to-server export
I am planning to do some upgrades using the hybrid method. The V5.5 server will be shut down, the DB extracted, and the V5.5 server will be brought back up and clients will run backups while we load the DB into 6.2. Then the V5.5 server will be disabled for client sessions, and an incremental export/import used to get the backup inventory in sync with 6.2, then clients will be cut over to the 6.2 server via a DNS change. Here's the question: The description of the hybrid method assumes that you will do the incremental export to media. I'd rather use server-to-server. I can't set up the server-to-server communication while the server names (the TSM server name, not the host name) are the same. Any reason I can't get around that by doing a SET SERVERNAME V55SERVERNAME_OLD on the V55 server, once all client sessions are cancelled? I know that causes havoc with Windows clients, but they should never be connecting to the old server again. Any suggestions/anybody tried this? Thanks W Wanda Prather | Senior Technical Specialist | wprat...@icfi.commailto:wprat...@icfi.com | www.jasi.comwww.jasi.com%20 ICF Jacob Sundstrom | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135
