Question about restores
Hi TSMers If restoring the folder with a 'no-to-all' to overwrite any files that exist does it do any sort of modified date check? That would be nice if it came across a file that existed in the directory but TSM had a new version of. Is there a way to achieve this? Thanks Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Question about restores (more info)
Hi I'm just using a Unix TSM client. I am going to use the -latest option. So i understand it will restore the latest copy of a file no matter if its active or not, but there may be older files on the file system in question. So I don't really want to say 'skip all files that already exist', I really want to say 'skip all files that already exist unless the copy in backup is newer'. The reason for this is that the people who control the client needing to be restored built the server from some old data they had on another machine. All very messy. So, can I tell TSM to restore all files unless it finds and 'older' version in the dir in question? Thanks Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Linux Client Performance
Hi All I am in the process of setting up some Linux TSM Clients at a remote site and am wondering if there are any good resources available for performance management as so far they are running painful slowly. I have tested some ftp'ing of files and these run fine. Does anyone have pointers to nay good documentation that could help with this? Many thanks Farren Minns -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: Client restore and search?
Hi Just to say this worked a treat on the Windows client but is there such an option for Solaris. I certainly don't see it if it's there. Or am I missing something really obvious? Thanks Farren |-+---| | Prather, Wanda | | | [EMAIL PROTECTED]| | | | To| | Sent by: ADSM: Dist Stor | [EMAIL PROTECTED]| | Manager | ST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 14/03/2007 15:34 |Subject| | | Re: [ADSM-L] | | Please respond to | Client restore| | ADSM: Dist Stor| and search? | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Well, it would help to know what platform you are on. But for Windows and UNIX clients, you start the client GUI, click RESTORE, then from the top menu select EDIT - FIND. There is a very nice SEARCH capability that lets you search on names, parts of names, size, date, etc. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Wednesday, March 14, 2007 11:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Client restore and search? Hello again for the second time today I'm trying to restore some files for a user even though we are not sure where those file actually are. They are part of a content manager/commonstore env and as such have very unhelpful names. Anyway, is there a way to use the pick option (or something else) to actually search for the files in TSM so that I know where they are (and if indeed they actually still exist within TSM? Thanks Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. -- -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Volume History Question
Good morning people This is such an old question but I have just been thinking about something and want to make sure that my understanding is correct. When I want to delete volume history information, am I right in assuming that I can delete anything older than my oldest database backup. For example, in my setting I keep database backups for 4 days before they expire. So in this case, if I wanted to get rid of anything older than say, seven days, I would be safe to do so. Is this right? Thanks Farren Minns John Wiley Sons Ltd -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: Volume History Question
Many thanks Gary Helpful and concise as always. I think what I'm going to do is just keep about six months worth. Much appreciated Farren |-+---| | Lee, Gary D.| | | [EMAIL PROTECTED]| | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| RIST.EDU| | | cc| | 14/03/2007 14:20 | | | |Subject| | Please respond to | Re: [ADSM-L]| | ADSM: Dist Stor| Volume | | Manager| History | | ADSM-L@VM.MARIST.EDU | Question| | | | | | | | | | | | | | | | | | | |-+---| Sir: Depends on what you want to have available. I let my volume history grow. This is because I occasionally need to know the history of a particular tape cartridge. After it goes back to scratch, tsm loses its error information. I can use the volhist to see how many times it has cycled through stgnew through stgdelete. However, If you have no need for such historical data, you are correct. You only need data back to the oldest db backup. Gary Lee Senior System Programmer Ball State University -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Wednesday, March 14, 2007 6:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Volume History Question Good morning people This is such an old question but I have just been thinking about something and want to make sure that my understanding is correct. When I want to delete volume history information, am I right in assuming that I can delete anything older than my oldest database backup. For example, in my setting I keep database backups for 4 days before they expire. So in this case, if I wanted to get rid of anything older than say, seven days, I would be safe to do so. Is this right? Thanks Farren Minns John Wiley Sons Ltd -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. -- -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Client restore and search?
Hello again for the second time today I'm trying to restore some files for a user even though we are not sure where those file actually are. They are part of a content manager/commonstore env and as such have very unhelpful names. Anyway, is there a way to use the pick option (or something else) to actually search for the files in TSM so that I know where they are (and if indeed they actually still exist within TSM? Thanks Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: Client restore and search?
Hi Sorry yes, this is a Windows client and a Solaris server. I'm pretty sure I don't have the 'find' option for Solaris (or if I do I can't find it), but I will get the Windows admin to check his client and let me know. Many thanks Farren |-+---| | Prather, Wanda | | | [EMAIL PROTECTED]| | | | To| | Sent by: ADSM: Dist Stor | [EMAIL PROTECTED]| | Manager | ST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 14/03/2007 15:34 |Subject| | | Re: [ADSM-L] | | Please respond to | Client restore| | ADSM: Dist Stor| and search? | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Well, it would help to know what platform you are on. But for Windows and UNIX clients, you start the client GUI, click RESTORE, then from the top menu select EDIT - FIND. There is a very nice SEARCH capability that lets you search on names, parts of names, size, date, etc. Wanda Prather I/O, I/O, It's all about I/O -(me) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Wednesday, March 14, 2007 11:08 AM To: ADSM-L@VM.MARIST.EDU Subject: Client restore and search? Hello again for the second time today I'm trying to restore some files for a user even though we are not sure where those file actually are. They are part of a content manager/commonstore env and as such have very unhelpful names. Anyway, is there a way to use the pick option (or something else) to actually search for the files in TSM so that I know where they are (and if indeed they actually still exist within TSM? Thanks Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. -- -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
TSM DB2 backup problems
TSM Server 5.2.7.2 on Solaris 2.9 - TSM Client API 5.3.4.0 on Windows 2003 Hi all, and a merry xmas/new year etc :-) I am wondering if anyone can point me in the direction of error code meanings for our DB2 backups. The errors we are getting look as follows :- The task ADMINISTRATOR.Backup_RMDB_Full with status Not successful ran on the DB2 Administrative Server on server name here and completed with return code -1371. The task started on server name here at 2006-12-27 23:00:19.0 and completed at 2006-12-27 23:00:30.0. The task lasted 11 seconds. I know nothing about DB2 and no one else here seems to either (very helpful), so I really want to find out what the code -1371 means. If I have to put in a call with TSM then so be it, but I would rather see what I can find out myself first. If anyone can help then I'd be very grateful. Many thanks Farren Minns John Wiley Sons Ltd -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: TAPE DRIVE STATE UNKNOWN
Hi I sometimes have network related issues with my 3494 library. How is your TSM server connected to the library and what OS is the server? When you start TSM, does it actually say that the library is ready for operations? My library is directly attached with a crossover network cable so it's on its own private network. If I get issues with communication, i just unplug the network cable from the back of the server, leave it a few seconds and then plug it back in. It normally establishes a connection again and things are OK. Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: TSM DB2 backup problems
Hi Well I have just been doing some work with the sys admin for the server in question and it looks like there was a server related issue on the 19th (no idea what) and for some reason all but one of the dbs was still in a quiesced state. Very odd and slightly worrying but TSM is not at fault here and the backups are working again now. Many thanks Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: TAPE DRIVE STATE UNKNOWN
Hi Murugan I'm afraid that's a very different set up to the one I have here so I really don't know what could be causing the problem. Maybe someone else on this board knows a bit more about SAN attached storage? I know that sometimes a drive state will remain as unknown until it is actually used by TSM at which point it then determines the correct state, but in your case that doesn't appear to be the issue as you can't even create a path to it. Sorry Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: TSM DB2 backup problems
Thanks Richard, that's a great help. And you are right, we work between xmas and new year to troubleshoot with obscure codes! :-) Fun indeed. Regards Farren -- The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. John Wiley Sons Limited is a private limited company registered in England with registered number 641132. Registered office address: The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ. --
Re: Windows 2003 Clients and 'access to object is denied'
Hi Thanks for that. I understand that 5.3 clients should be able to work with a 5.2 server, but is this a safe option? We are not going to be moving to the server level of 5.3 until some time early next year. Thanks Farren |-+---| | Prather, Wanda | | | [EMAIL PROTECTED]| | | | To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 15/11/2006 20:19 | Re: [ADSM-L] Windows 2003 | | | Clients and 'access to| | Please respond to | object is denied' | | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Upgrade your client to 5.3.4; that eliminates many of them (although I'm still getting that error on a couple of files). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Wednesday, November 15, 2006 6:26 AM To: ADSM-L@VM.MARIST.EDU Subject: Windows 2003 Clients and 'access to object is denied' Hi all I have another question today. I can see that we are getting quite a large number of errors backing up our Windows 2003 clients. We have three such clients all running the BA version 5.2.4.10. Pretty much all the errors point to .dll files with the error being 'access to the object is denied'. I don't have a list of the files but can get one from the system administrator if it will be of use. Has anyone else seen this behaviour backing up Windows 2003 or does it point to a possible problem? Thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Windows 2003 Clients and 'access to object is denied'
That's a great vote of confidence. Many thanks Farren |-+---| | Phillip Burgess | | | [EMAIL PROTECTED]| | | CO.UK| To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 16/11/2006 10:30 | Re: [ADSM-L] Windows 2003 | | | Clients and 'access to| | Please respond to | object is denied' | | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Hi Farren I have not heard of any problems with 5.3 clients connected to a 5.2 server. Phil From: ADSM: Dist Stor Manager on behalf of Farren Minns Sent: Thu 16/11/2006 08:15 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows 2003 Clients and 'access to object is denied' Hi Thanks for that. I understand that 5.3 clients should be able to work with a 5.2 server, but is this a safe option? We are not going to be moving to the server level of 5.3 until some time early next year. Thanks Farren |-+---| | Prather, Wanda | | | [EMAIL PROTECTED]| | | | To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU | | | | Subject| | 15/11/2006 20:19 | Re: [ADSM-L] Windows 2003 | | | Clients and 'access to | | Please respond to | object is denied' | | ADSM: Dist Stor | | | Manager | | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Upgrade your client to 5.3.4; that eliminates many of them (although I'm still getting that error on a couple of files). -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Wednesday, November 15, 2006 6:26 AM To: ADSM-L@VM.MARIST.EDU Subject: Windows 2003 Clients and 'access to object is denied' Hi all I have another question today. I can see that we are getting quite a large number of errors backing up our Windows 2003 clients. We have three such clients all running the BA version 5.2.4.10. Pretty much all the errors point to .dll files with the error being 'access to the object is denied'. I don't have a list of the files but can get one from the system administrator if it will be of use. Has anyone else seen this behaviour backing up Windows 2003 or does it point to a possible problem? Thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection
Using TSM to backup a DB2 database
Hi all Running TSM Server 5.2.7.2 on Solaris 2.9. Going to be backing up a Windows 2003 DB2 client. I am just beginning to read the extensive Backing Up DB2 with IBM Tivoli Storage Management redbook and want to ask a very basic question at the start. Am I now right in thinking that I install both the BA Client for the standard backup (presumably excluding the DB2 datafiles), and the API for the DB2 backups? If this is the case, is this one licensed client or two? And do they both use separate configuration files (dsm.opt etc). This is new to me and on a Windows OS which I'm not familiar with (I mostly deal with Solaris). Thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Using TSM to backup a DB2 database
Hi David From what I can gather the standard TSM Client handles DB2 by itself without the need for a TDP license. That is if course unless I'm missing something. We do use TDP for out Lotus Domino backups and I understand that it's a totally separate install, licence etc. Thanks Farren |-+---| | David E Ehresman | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager |[EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU|U | | | cc| | 16/11/2006 14:02 | | | |Subject| | Please respond to |Re: [ADSM-L] Using | | ADSM: Dist Stor|TSM to backup a DB2| | Manager|database | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| The API and BA client are the same license. Presumably you will also be licensing TSM for DB, aka Tivoli Data Protection for Oracle (TDPO). That is a different license on top of the BA client license. David Farren Minns [EMAIL PROTECTED] 11/16/2006 5:56 AM Hi all Running TSM Server 5.2.7.2 on Solaris 2.9. Going to be backing up a Windows 2003 DB2 client. I am just beginning to read the extensive Backing Up DB2 with IBM Tivoli Storage Management redbook and want to ask a very basic question at the start. Am I now right in thinking that I install both the BA Client for the standard backup (presumably excluding the DB2 datafiles), and the API for the DB2 backups? If this is the case, is this one licensed client or two? And do they both use separate configuration files (dsm.opt etc). This is new to me and on a Windows OS which I'm not familiar with (I mostly deal with Solaris). Thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Windows filespace naming in Solaris GUI
Hi all I'm running TSM Server 5.2.7.2 on Solaris 9. My question is this. When looking at the Windows clients in the GUI and drilling down to see what file systems are being backed up, all I am seeing is that they are all named ... (three dots) but with the relevant FSID. This is obviously not causing a problem and I only noticed this because I was poking around, but is this the way it should be displayed or is something wrong? Many thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Windows 2003 Clients and 'access to object is denied'
Hi all I have another question today. I can see that we are getting quite a large number of errors backing up our Windows 2003 clients. We have three such clients all running the BA version 5.2.4.10. Pretty much all the errors point to .dll files with the error being 'access to the object is denied'. I don't have a list of the files but can get one from the system administrator if it will be of use. Has anyone else seen this behaviour backing up Windows 2003 or does it point to a possible problem? Thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Can't reset Version Data Exists parm on
I'm not sure how you managed it because you should not be able to directly modify the Active Policy Set. You have to edit the STANDARD one and then Validate (if required), and Activate it. Farren |-+---| | Orin Rehorst | | | [EMAIL PROTECTED]| | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 15/11/2006 14:36 |Subject| | | [ADSM-L] Can't reset | | Please respond to | Version Data | | ADSM: Dist Stor| Exists parm on | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| I changed the ACTIVE policy set Version Data Exists parm from 2 to 4 using GUI. I went to change it back and got: ANR1585E UPDATE COPYGROUP: Policy set ACTIVE cannot be modified. Error message says I can't change the ACTIVE set, but I changed it in the first place. Please advise. Regards, Orin Orin Rehorst ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
TSM Client file input/output error error
Hi All Running TSM Client 5.1.6.0 on Solaris against a 5.2.7.2 server on Solaris 2.9. We have been backing up this client for a long time now and it has been fine. However, the sys admin did a patch cluster install at the weekend and ever since I have been seeing the following errors. dsmsched.log 23/08/06 22:21:05 ANS4023E Error processing '/usr/local/webservers': file input/output error 23/08/06 22:21:05 --- SCHEDULEREC OBJECT END COI-DAILY-INC 23/08/06 21:30:00 23/08/06 22:21:05 ANS1512E Scheduled event 'COI-DAILY-INC' failed. Return code = 12. dsmerror.log 23/08/06 22:20:59 PrivIncrFileSpace: Received rc=164 from fioGetDirEntries: /usr/local/webservers /phy/live/htdocs/Phy/External/PhyH Any idea what I'm seeing here? Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: AW: [ADSM-L] TSM Client file input/output error error
Thanks to all, I will see what I can find. Farren |-+---| | Thomas Rupp | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 24/08/2006 10:48 |Subject| | | [ADSM-L] AW: [ADSM-L] TSM| | Please respond to | Client file input/output | | ADSM: Dist Stor| error error | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Can you read this file using another program (vi ...)? google only showed this site for PrivIncrFileSpace 164 http://www.lofland.net/LoflandBLOG/category/unix-notes/ He had a corrupted filesystem causing the error. HTH Thomas Rupp -Ursprüngliche Nachricht- Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Farren Minns Gesendet: Donnerstag, 24. August 2006 11:36 An: ADSM-L@VM.MARIST.EDU Betreff: [ADSM-L] TSM Client file input/output error error Hi All Running TSM Client 5.1.6.0 on Solaris against a 5.2.7.2 server on Solaris 2.9. We have been backing up this client for a long time now and it has been fine. However, the sys admin did a patch cluster install at the weekend and ever since I have been seeing the following errors. dsmsched.log 23/08/06 22:21:05 ANS4023E Error processing '/usr/local/webservers': file input/output error 23/08/06 22:21:05 --- SCHEDULEREC OBJECT END COI-DAILY-INC 23/08/06 21:30:00 23/08/06 22:21:05 ANS1512E Scheduled event 'COI-DAILY-INC' failed. Return code = 12. dsmerror.log 23/08/06 22:20:59 PrivIncrFileSpace: Received rc=164 from fioGetDirEntries: /usr/local/webservers /phy/live/htdocs/Phy/External/PhyH Any idea what I'm seeing here? Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Update - Re: [ADSM-L] Some strange tape related issues?
Hi all Regarding the fact that the SCRATCHCATegory value for 3590 tapes is the value of the 3490 tapes plus one, how does TSM cope with this? In my situation, with the SCRATCHCATegory set to 301(12D), and the Hex value within the library being 12E(302) surely it should not be able to see the scratch volumes? What am I missing here? Also, how do I fix volumes marked FFFA within the library manager? There are four volumes in my library with this category code. Two of them are volumes that now do not even exist (one is called 'CLEAN' and has never existed that I know of). The other two are for copypool volumes that TSM sees as offsite and I have just checked with the DR site and these volumes do indeed exist). So how do I tell the library to stop worrying about these volumes? I am having a look through the IBM TotalStorage Enterprise Tape A Practical Guide, but have not found what I am looking for so far. Thanks again as always Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU | | | cc| | 10/04/2006 15:21 | | | |Subject| | Please respond to | Re: [ADSM-L] Update - Re: | | ADSM: Dist Stor| [ADSM-L] Some strange tape| | Manager| related issues? | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Apr 10, 2006, at 5:46 AM, Farren Minns wrote: Hi again OK, here's something I have just found, and this is on the current working live server (that has worked this way for years). When I look at the lib definition within TSM, I see the following :- Library Name 3494A Library Type 349X ACS Id - Private Category 300 Scratch Category 301 But, when I do a 'mtlib -l 3494a -qI' from the command line I see the following (just an example):- 000212 FFFA 01 10 00 (this is a copypool vol) 000222 012E 00 10 00 (this is scratch) 000223 012C 00 10 00 (this is private) Now, when I punch 300 in to my scientific calculator I get a Hex value of 12C, and that fits in with the info above. But, when I enter 301 I get 12D which does not fit in with the above 3494 assignments. So how on earth is this working at all? Oddly, the explanation for this seems to have evaporated from the TSM manuals, but is preserved in ADSM QuickFacts. The 3494 started life as a 3490 tape library, and 3590s ere added later. It became the convention that the SCRATCHCATegory value was for 3490 tapes, and that value plus one was for 3590 tapes. Also, the category FFFA seems to cover copypool volumes that have yet to be moved from the library and also cleaning tapes. Is this meant to work in this way? FFFA is an aberrant state, suggesting that volumes marked that way were rudely removed from the library without going through the 3494 Library Manager, for it to be aware of what's going on. When it runs an Inventory, it registers its confusion about the state of the volumes with that category code value. Refer to Redbook IBM TotalStorage Enterprise Tape A Practical Guide for some info on that. You need to take action on this inconsistency - which may be the source of considerable volume access problems. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own
Re: 3494 Media Type
I have also seen this from time to time, and a good rub of the sticker on the leg usually does the trick :-) Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| [EMAIL PROTECTED]| | | MARIST.EDU| | 11/04/2006 13:50 | cc| | | | | Please respond to |Subject| | ADSM: Dist Stor| Re: | | Manager| [ADSM-L] | | ADSM-L@VM.MARIST.EDU | 3494 | | | Media Type| | | | | | | | | | | | | | | | | | | |-+---| On Apr 11, 2006, at 8:23 AM, David E Ehresman wrote: How does the 3494 determine which 'media type', e.g. 3590 J or K, a cart is? Our 3494 is starting to eject tapes as they are inserted complaining about unknown media type. These are tapes that have been in use for a number of years and are being reinserted into the 3494 after coming back from the offsite vault. Most of the time they are being correctly recognized simply by reinserting them into the library another time. Our non-IBM CE doesn't have a clue. Hi, David - We've seen the same thing here, with J tapes coming back from offsite: insert a bunch, have one or two rejected with that media complaint. Reinsert (one at a time), and the library then accepts the tape. It may be that the laser/receptor is having trouble reading the 'J' stickerette, where rubbing one's finger over it before inserting may remove some residue which is imperceptible to us. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: 5.3 questions
I am not using 5.3 so can not really comment. But on the CLI vs GUI debate, whilst I agree that a working knowledge of the command line interface is a necessity, the GUI can be very useful for admins like me for whom TSM admin is just maybe 10% of my job and keeping up with all parameters and flags is never going to happen. Farren |-+---| | Mark Stapleton| | | [EMAIL PROTECTED]| | || To| | Sent by: ADSM: Dist Stor | AD| | Manager | SM| | ADSM-L@VM.MARIST.EDU| -L| | | @V| | 11/04/2006 15:42 | M.| | | MA| | Please respond to | RI| | ADSM: Dist Stor| ST| | Manager| .E| | ADSM-L@VM.MARIST.EDU | DU| | | cc| | | | | |Subject| | | Re| | | : | | | [A| | | DS| | | M-| | | L]| | | 5.| | | 3 | | | qu| | | es| | | ti| | | on| | | s | | | | | | | | | | | | | | | | | | | |-+---| ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 04/11/2006 07:32:20 AM: On Mon, 10 Apr 2006, Gill, Geoffrey L. wrote: I'm finding that the more I use the console the more I dislike it. All I can say is: embrace the command line admin tool, because it didn't barely changed between 5.2 and 5.3, and is much more flexable over a slow link. We've been over this CLI vs. GUI issue before. There are those TSM admins out there that are more comfortable with the help features and fill-in-the-blank processes of the GUI, and then there are those that truly learn all of the parameters and flags of the TSM command set by using the command line. (Of course, using the CLI is much easier when you can touch type at a decent speed--a skill set that I feel is absolutely critical for a decent admin of any flavor.) -- Mark Stapleton ([EMAIL PROTECTED]) MR Backup and Recovery Management 262.790.3190 -- 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. == ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are
Re: Some strange tape related issues?
Good morning Richard On the first point I may have confused things. When I brought the new TSM server up I made sure the library was indeed in Auto mode, I just had it in manual when I did the initial db restore (which completed without any errors). However, I did not try to get the new TSM server to do an audit of the lib. This may sound like a silly question, but I'm assuming that the TSM audit commands can have no effect on the actual library inventory. I just want to make sure I don't create any more problems for myself. On the second point, I did run a few mtlib queries on the old server (after all server activity had finished and TSM had been halted), and on the new server immediately after it was connected to the library. The commands I ran were as follows :- mtlib -l 3494a -vqK -s fffd (to count all cleaning tapes) mtlib -l 3494a -vqK -s 12E (to count all scratch) mtlib -l 3494a -vqK -s 12C (to count all private) mtlib -l 3494a -vqK -s (to count all volumes) mtlib -l 3494a -qS (to get info about lib) mtlib -l 3494a -qI (to get a list of all volumes) I then compared the output from the old server with that of the new one and confirmed that the output was identical on both. I would not have gone ahead had this not been the case. I am assuming the atldd driver is in good shape, but apart from running the above queries, how can I tell? I am running a later version of the driver form that on the original server. As far as the lib being able to talk to the server OK, it has it's own dedicated little network. I didn't change anything on the library here, I just made sure that the required interface with the exact same IP address was present on the new server. Again, as the mtlib commands work, I'm assuming this is OK. On the third point, there are architectural differences. The original server resides on a Solaris 2.7 server, and the new one is Solaris 2.9. But, last time I tried this, I got as far as being able to back up the db, audit volumes etc, and it only started having problems when trying to migrate to tapes that already had a state of 'filling' (which I was hoping to solve this time round). So it doesn't sound like an OS problem here. Thanks Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU|[EMAIL PROTECTED]| | |U | | 08/04/2006 22:38 | cc| | | | | Please respond to |Subject| | ADSM: Dist Stor|Re: [ADSM-L] Some | | Manager|strange tape | | ADSM-L@VM.MARIST.EDU |related issues?| | | | | | | | | | | | | | | | | | | |-+---| On Apr 8, 2006, at 1:20 PM, Farren Minns wrote: Hi Richard I see the following which to me looks as I would expect and vol 000188 was indeed the volume I used this morning. I did not see any errors during backup or restore. The only thing is that the database volumes on the new server had mirrored copies already in place. These were stale when I started the server but then syncd ok. Could this have caused a problem? Farren - Unused mirrors should not be an issue, in that the unmirrored copy of the database should be fully viable unto itself. The Vary On which performed synchronization just copies the primary image data. You mentioned in your first posting today that the library was in Pause mode for some reason when the new instance of the TSM server was started. The library needs to be viable when TSM goes to use it at any time; and at start-up time, TSM is trying to do a lot of communication with it, for volumes consistency checking. Putting the 3494 back into Auto mode does not result in an audit, but rather a library-specific Inventory check (depending upon library settings), where the accessor runs around scanning storage cell and drive contents. Manually performing a TSM Audit Library may correct TSM's knowledge of its
Update - Re: [ADSM-L] Some strange tape related issues?
Hi again OK, here's something I have just found, and this is on the current working live server (that has worked this way for years). When I look at the lib definition within TSM, I see the following :- Library Name 3494A Library Type 349X ACS Id - Private Category 300 Scratch Category 301 But, when I do a 'mtlib -l 3494a -qI' from the command line I see the following (just an example):- 000212 FFFA 01 10 00 (this is a copypool vol) 000222 012E 00 10 00 (this is scratch) 000223 012C 00 10 00 (this is private) Now, when I punch 300 in to my scientific calculator I get a Hex value of 12C, and that fits in with the info above. But, when I enter 301 I get 12D which does not fit in with the above 3494 assignments. So how on earth is this working at all? Also, the category FFFA seems to cover copypool volumes that have yet to be moved from the library and also cleaning tapes. Is this meant to work in this way? Thanks Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU|[EMAIL PROTECTED]| | |U | | 08/04/2006 22:38 | cc| | | | | Please respond to |Subject| | ADSM: Dist Stor|Re: [ADSM-L] Some | | Manager|strange tape | | ADSM-L@VM.MARIST.EDU |related issues?| | | | | | | | | | | | | | | | | | | |-+---| On Apr 8, 2006, at 1:20 PM, Farren Minns wrote: Hi Richard I see the following which to me looks as I would expect and vol 000188 was indeed the volume I used this morning. I did not see any errors during backup or restore. The only thing is that the database volumes on the new server had mirrored copies already in place. These were stale when I started the server but then syncd ok. Could this have caused a problem? Farren - Unused mirrors should not be an issue, in that the unmirrored copy of the database should be fully viable unto itself. The Vary On which performed synchronization just copies the primary image data. You mentioned in your first posting today that the library was in Pause mode for some reason when the new instance of the TSM server was started. The library needs to be viable when TSM goes to use it at any time; and at start-up time, TSM is trying to do a lot of communication with it, for volumes consistency checking. Putting the 3494 back into Auto mode does not result in an audit, but rather a library-specific Inventory check (depending upon library settings), where the accessor runs around scanning storage cell and drive contents. Manually performing a TSM Audit Library may correct TSM's knowledge of its volumes in the library. I would use mtlib commands to get a list of the library tapes with Category Codes reported, to assure that all volumes seem reasonable and appropriate for use with the Library category code numbers as end up in the new TSM server. Presumably, your atldd driver is in good shape on the new server (?) and the 3494's Library Manager has been updated to allow access by the new server system? (I expect so, but want to assure that basics are not overlooked.) The only other thing I could think of is that there may be some architectural inconsistency which makes a db restoral type of server transfer dubious or invalid, possibly one system being 32-bit and the other 64-bit, for example. I would pore over the Activity Log in the new server looking for other problem indications. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any
Re: Update - Re: [ADSM-L] Some strange tape related issues?
Thanks Richard That certainly explains the Hex code anomaly. On the FFFA problem, there are four volumes that are 'apparently' in the lib, but are not and I have checked this. Two of them are copypool volumes, one is not part of any storage pool and the other is just called 'CLEAN' even though I have never ever had a tape with that label. All the best Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU | | | cc| | 10/04/2006 15:21 | | | |Subject| | Please respond to | Re: [ADSM-L] Update - Re: | | ADSM: Dist Stor| [ADSM-L] Some strange tape| | Manager| related issues? | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Apr 10, 2006, at 5:46 AM, Farren Minns wrote: Hi again OK, here's something I have just found, and this is on the current working live server (that has worked this way for years). When I look at the lib definition within TSM, I see the following :- Library Name 3494A Library Type 349X ACS Id - Private Category 300 Scratch Category 301 But, when I do a 'mtlib -l 3494a -qI' from the command line I see the following (just an example):- 000212 FFFA 01 10 00 (this is a copypool vol) 000222 012E 00 10 00 (this is scratch) 000223 012C 00 10 00 (this is private) Now, when I punch 300 in to my scientific calculator I get a Hex value of 12C, and that fits in with the info above. But, when I enter 301 I get 12D which does not fit in with the above 3494 assignments. So how on earth is this working at all? Oddly, the explanation for this seems to have evaporated from the TSM manuals, but is preserved in ADSM QuickFacts. The 3494 started life as a 3490 tape library, and 3590s ere added later. It became the convention that the SCRATCHCATegory value was for 3490 tapes, and that value plus one was for 3590 tapes. Also, the category FFFA seems to cover copypool volumes that have yet to be moved from the library and also cleaning tapes. Is this meant to work in this way? FFFA is an aberrant state, suggesting that volumes marked that way were rudely removed from the library without going through the 3494 Library Manager, for it to be aware of what's going on. When it runs an Inventory, it registers its confusion about the state of the volumes with that category code value. Refer to Redbook IBM TotalStorage Enterprise Tape A Practical Guide for some info on that. You need to take action on this inconsistency - which may be the source of considerable volume access problems. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Some strange tape related issues?
the off site tapes that I created earlier this morning, even though they were moved off site and the status of those volumes changed to vault. TSM knew they had been removed from the library so why is it trying to see them 'in' the library now? The command I use to move the volumes is as follows :- move drm * wherestate=mountable tostate=vault remove=bulk Again, I'm sorry for the lengthy prose, but i thought it best to be as verbose as possible. All the best Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Some strange tape related issues?
Hi Richard I see the following which to me looks as I would expect and vol 000188 was indeed the volume I used this morning. I did not see any errors during backup or restore. The only thing is that the database volumes on the new server had mirrored copies already in place. These were stale when I started the server but then syncd ok. Could this have caused a problem? date time TYPE BACKUP_SERIES VOLUME_NAME --- -- - -- 2006-04-03 10:14:19.00- BACKUPFULL 1912 000193 2006-04-04 09:40:02.00- BACKUPFULL 1913 000370 2006-04-05 09:32:03.00- BACKUPFULL 1914 000413 2006-04-06 09:59:45.00- BACKUPFULL 1915 000441 2006-04-07 09:36:42.00- BACKUPFULL 1916 000488 2006-04-08 10:05:48.00- BACKUPFULL 1917 000188 Thanks Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU|[EMAIL PROTECTED]| | |U | | 08/04/2006 16:40 | cc| | | | | Please respond to |Subject| | ADSM: Dist Stor|Re: [ADSM-L] Some | | Manager|strange tape | | ADSM-L@VM.MARIST.EDU |related issues?| | | | | | | | | | | | | | | | | | | |-+---| Farren - The kind of inconsistencies you're seeing are the kind I would expect if your new TSM server db is stale or otherwise inconsistent with the state of your production server. This particularly shows up where you have multiple TSM servers in any manner sharing the same library. There should have been a good db restoral as you went to the new server today. One quick way to check that is to do: SELECT DATE_TIME AS DATE TIME ,TYPE,BACKUP_SERIES,VOLUME_NAME - FROM VOLHISTORY WHERE TYPE='BACKUPFULL' OR TYPE='BACKUPINCR' and check the date-time values for currency. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Db Restore question
Hi all If I want to restore my database ( for example from yesterday), do I need to re-format the existing dB/log volumes or does the restore do what ever it needs to do in this regard? Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Update - Tape problem after moving TSM to new server
Hi Gary I did as you suggested and commented out the entries in the /kernel/drv/st.conf file and now when I boot -r, I see just the 0 and 1 IBM entries that I wanted, so that's great news, many thanks. Now I just hope that it solves my strange little 'unable to write to filling tapes' problem. All the best Farren |-+---| | Lee, Gary D.| | | [EMAIL PROTECTED]| | | | To| | 27/03/2006 15:05 | Farren Minns | | | [EMAIL PROTECTED] | | | cc| | | | | |Subject| | | Tape problem | | | | | | | | | | | | | | | | | | | |-+---| Sir: Are you ussing the same exact drives and libraries afor v2.9 as v2.7? As to your other question regarding st: Do you have a tape device other than the 3590 attached to the v2.9 server? If not, simply comment out all the scsi ids in the st.conf file. This will not let st grab a tape device. Gary Lee Senior System Programmer Ball State University -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.3.2/293 - Release Date: 3/26/2006 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Update - Tape problem after moving TSM to new server
Good morning Roger Thank you so much for that information. Backing out wasn't a big problem for me as the old server was still left as it was so all I had to do was connect the drives and lib again and bring it back up (phew). This is a very annoying problem though. Surely TSM should be able to see that even though the /dev/rmt/ entry has changed, it's still the exact same device type and that it should still be able to write to the volume/s in question. Is this something that is 'working as designed' or a bug/fault? Also. It's odd that I could not even audit any of the filling volumes until I changed the state to readonly. BUT, TSM could happily write to scratch tapes that had been labelled on the old server. I really don't know why this should be? I have certainly not seen this in any documentation. Thanks again Farren |-+---| | Roger Deschner| | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 26/03/2006 18:54 |Subject| | | Re: [ADSM-L] Update -| | Please respond to | Tape problem after moving| | ADSM: Dist Stor| TSM to new server| | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| This happened to me too, when doing a similar migration. I looked up my notes from the time. The problem is that your Filling tapes were started on a different drive type than you have now, and so it won't append any more data onto them. (Even if they are the very same drives, this can still happen.) How to deal with it: 1. Get some extra tapes, to use while you do the following steps. Before you do anything else after the big change, LABEL LIBVOL these new tapes so there will be something for migration and DB backup to use. 2. Mark all your Filling and Full tapes Readonly. You will still be able to restore from them OK. If you don't already have it, set a REUSEDELAY of a day or two. 3. The Full tapes should reclaim themselves normally. However, reclamation will not select any tape that is still marked as Filling, so you've got to reclaim them manually yourself with MOVE DATA. Might take a while, which is OK as long as you don't run out of tapes. 4. As tapes are cleared, whether they had been Filling (via MOVE DATA) or Full (via reclamation), you may need to do CHECKOUT LIBVOL on them followed by a LABEL LIBVOL OVERWRITE=YES before it will reuse them as scratch tapes. When you get a mixture of Pending tapes from before and after the big change, then you can easily tell which ones you need to relabel - they will be the ones that are both Pending and Readonly. When this happened to me, it was a hassle, but I found that it was a manageable hassle. I did not have to do anything as drastic as the backout you did. Sorry to hear about that - because you are having to do 3 times the work with a migrate-backout-migrate cycle. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Sat, 25 Mar 2006, Farren Minns wrote: OK, this is what I have now found out but had no idea what's going on. After completely removing and redefining the lib,drives and paths I still get the same errors as below. So, for example I can't audit volume 000700 without the error below. BUT..., if I change the state of the volume from read/write to readonly, I can. What's that all about? I can also audit volumes that have an access of read/write but that are 'full' and not 'filling'. This is very strange. Has anyone else ever seen this behaviour before ? Many thanks again Farren Minns Hi All I have just moved my TSM Server 5.1.6.2 from a Solaris 7 server to a new Solaris 9 box. Now, everything so far has gone fine and I have tested a couple of backups and also a backup of the database. When I look at the contents of the tapepool, copypool, q libv etc I see what I would expect. BUT, when I try to run migration from disk to tape there is a problem. In this example tape 000700 which is in a filling state is required but I see
Re: Update - Tape problem after moving TSM to new server
],0:ub lrwxrwxrwx 1 root root 55 Mar 15 11:43 1ubn - ../../devices/[EMAIL PROTECTED],60/IntraServer,[EMAIL PROTECTED]/[EMAIL PROTECTED],0:ubn lrwxrwxrwx 1 root root 54 Mar 15 11:43 1un - ../../devices/[EMAIL PROTECTED],60/IntraServer,[EMAIL PROTECTED]/[EMAIL PROTECTED],0:un |-+---| | Roger Deschner| | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 26/03/2006 18:54 |Subject| | | Re: [ADSM-L] Update -| | Please respond to | Tape problem after moving| | ADSM: Dist Stor| TSM to new server| | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| This happened to me too, when doing a similar migration. I looked up my notes from the time. The problem is that your Filling tapes were started on a different drive type than you have now, and so it won't append any more data onto them. (Even if they are the very same drives, this can still happen.) How to deal with it: 1. Get some extra tapes, to use while you do the following steps. Before you do anything else after the big change, LABEL LIBVOL these new tapes so there will be something for migration and DB backup to use. 2. Mark all your Filling and Full tapes Readonly. You will still be able to restore from them OK. If you don't already have it, set a REUSEDELAY of a day or two. 3. The Full tapes should reclaim themselves normally. However, reclamation will not select any tape that is still marked as Filling, so you've got to reclaim them manually yourself with MOVE DATA. Might take a while, which is OK as long as you don't run out of tapes. 4. As tapes are cleared, whether they had been Filling (via MOVE DATA) or Full (via reclamation), you may need to do CHECKOUT LIBVOL on them followed by a LABEL LIBVOL OVERWRITE=YES before it will reuse them as scratch tapes. When you get a mixture of Pending tapes from before and after the big change, then you can easily tell which ones you need to relabel - they will be the ones that are both Pending and Readonly. When this happened to me, it was a hassle, but I found that it was a manageable hassle. I did not have to do anything as drastic as the backout you did. Sorry to hear about that - because you are having to do 3 times the work with a migrate-backout-migrate cycle. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Sat, 25 Mar 2006, Farren Minns wrote: OK, this is what I have now found out but had no idea what's going on. After completely removing and redefining the lib,drives and paths I still get the same errors as below. So, for example I can't audit volume 000700 without the error below. BUT..., if I change the state of the volume from read/write to readonly, I can. What's that all about? I can also audit volumes that have an access of read/write but that are 'full' and not 'filling'. This is very strange. Has anyone else ever seen this behaviour before ? Many thanks again Farren Minns Hi All I have just moved my TSM Server 5.1.6.2 from a Solaris 7 server to a new Solaris 9 box. Now, everything so far has gone fine and I have tested a couple of backups and also a backup of the database. When I look at the contents of the tapepool, copypool, q libv etc I see what I would expect. BUT, when I try to run migration from disk to tape there is a problem. In this example tape 000700 which is in a filling state is required but I see the following error :- ANR1000I Migration process 4 started for storage pool BACKUPPOOL. ANR8447E No drives are currently available in library 3494A. ANR1401W Mount request denied for volume 000700 - mount failed. Instead, TSM loads a new scratch tape and then continues fine. What is going on here? Has any body seen this before? Thanks in advance Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private
Re: Update - Tape problem after moving TSM to new server
Hi Ian I only deleted and recreated the library, drives and paths, but I did not touch the 3590 Device Class. Do I need to remove and recreate that too? If I do this, how will it effect the tapepool copypool that this device class specified? I actually printed screen dumps of the drives etc before removing and recreating to make sure that they were the same (apart from the /dev/rmt/ entry of course). As far as I know, no special declarations of device class are made during the addition of drives/libs/paths etc anyway. I did not do a manual audit of the library? But i figured that as it could use scratch tapes and audit volumes that were full or filling (readonly), things were already OK. I could be wrong. Thanks Farren |-+---| | Smith, I (Ian) | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 27/03/2006 11:00 |Subject| | | Re: [ADSM-L] Update -| | Please respond to | Tape problem after moving| | ADSM: Dist Stor| TSM to new server| | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Did you make any changes to mountlimit or format on the device classes? When you recreated the drives and paths after the migration did you bind them to the correct device class/device type? After the migration did you audit the library? _ Ian Smith SAN/TSM Specialist IT Infrastructure Rabobank International Thames Court, One Queenhithe London EC4V 3RL t: +44 (0)20 7809 3046 f: +44 (0)20 7809 3599 m: +44 (0)7843 689914 Mailto: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: 27 March 2006 10:48 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Update - Tape problem after moving TSM to new server Good morning Roger Thank you so much for that information. Backing out wasn't a big problem for me as the old server was still left as it was so all I had to do was connect the drives and lib again and bring it back up (phew). This is a very annoying problem though. Surely TSM should be able to see that even though the /dev/rmt/ entry has changed, it's still the exact same device type and that it should still be able to write to the volume/s in question. Is this something that is 'working as designed' or a bug/fault? Also. It's odd that I could not even audit any of the filling volumes until I changed the state to readonly. BUT, TSM could happily write to scratch tapes that had been labelled on the old server. I really don't know why this should be? I have certainly not seen this in any documentation. Thanks again Farren |-+---| | Roger Deschner | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED] | | ADSM-L@VM.MARIST.EDU | cc| | | | | 26/03/2006 18:54 | Subject| | | Re: [ADSM-L] Update - | | Please respond to | Tape problem after moving| | ADSM: Dist Stor | TSM to new server | | Manager | | | ADSM-L@VM.MARIST.EDU
Re: Update - Tape problem after moving TSM to new server
Thanks Ian Sadly I wont be able to do that until I try this upgrade again (possibly this coming weekend). That's what is such a pain with this as I need to get as many ideas together before I can even attempt it again :-( Farren |-+---| | Smith, I (Ian) | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 27/03/2006 11:58 |Subject| | | Re: [ADSM-L] Update -| | Please respond to | Tape problem after moving| | ADSM: Dist Stor| TSM to new server| | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Try running the audit library lib name checklabel=barcode to refresh the library inventory in TSM from the library itself. Check the help for the specifics associated with your library. _ Ian Smith SAN/TSM Specialist IT Infrastructure Rabobank International Thames Court, One Queenhithe London EC4V 3RL t: +44 (0)20 7809 3046 f: +44 (0)20 7809 3599 m: +44 (0)7843 689914 Mailto: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: 27 March 2006 11:37 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Update - Tape problem after moving TSM to new server Hi Ian I only deleted and recreated the library, drives and paths, but I did not touch the 3590 Device Class. Do I need to remove and recreate that too? If I do this, how will it effect the tapepool copypool that this device class specified? I actually printed screen dumps of the drives etc before removing and recreating to make sure that they were the same (apart from the /dev/rmt/ entry of course). As far as I know, no special declarations of device class are made during the addition of drives/libs/paths etc anyway. I did not do a manual audit of the library? But i figured that as it could use scratch tapes and audit volumes that were full or filling (readonly), things were already OK. I could be wrong. Thanks Farren |-+---| | Smith, I (Ian) | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED] | | ADSM-L@VM.MARIST.EDU | cc| | | | | 27/03/2006 11:00 | Subject| | | Re: [ADSM-L] Update - | | Please respond to | Tape problem after moving| | ADSM: Dist Stor | TSM to new server | | Manager | | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Did you make any changes to mountlimit or format on the device classes? When you recreated the drives and paths after the migration did you bind them to the correct device class/device type? After the migration did you audit the library? _ Ian Smith SAN/TSM Specialist IT Infrastructure Rabobank International Thames Court, One Queenhithe London EC4V 3RL t: +44 (0)20 7809 3046 f: +44 (0)20 7809 3599 m: +44 (0)7843 689914 Mailto: [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: 27 March 2006 10:48 To: ADSM-L@VM.MARIST.EDU
Re: Update - Tape problem after moving TSM to new server
Of course I have another problem with this. I only have 1 frame of a 3494 and not many free slots. If I set all the filling tapes to readonly, after the next backup TSM will grab 36 brand new tapes (as I have collocation on in the library, 1 for each client). So realistically I would have to turn collocation 'off' for a period of time in order to move the data off the filling volumes and then turn it on again as and when I'm sorted. Does anybody know of any problems with turning collocation off and then on again other than slower restores. Thanks Farren |-+---| | Roger Deschner| | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 26/03/2006 18:54 |Subject| | | Re: [ADSM-L] Update -| | Please respond to | Tape problem after moving| | ADSM: Dist Stor| TSM to new server| | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| This happened to me too, when doing a similar migration. I looked up my notes from the time. The problem is that your Filling tapes were started on a different drive type than you have now, and so it won't append any more data onto them. (Even if they are the very same drives, this can still happen.) How to deal with it: 1. Get some extra tapes, to use while you do the following steps. Before you do anything else after the big change, LABEL LIBVOL these new tapes so there will be something for migration and DB backup to use. 2. Mark all your Filling and Full tapes Readonly. You will still be able to restore from them OK. If you don't already have it, set a REUSEDELAY of a day or two. 3. The Full tapes should reclaim themselves normally. However, reclamation will not select any tape that is still marked as Filling, so you've got to reclaim them manually yourself with MOVE DATA. Might take a while, which is OK as long as you don't run out of tapes. 4. As tapes are cleared, whether they had been Filling (via MOVE DATA) or Full (via reclamation), you may need to do CHECKOUT LIBVOL on them followed by a LABEL LIBVOL OVERWRITE=YES before it will reuse them as scratch tapes. When you get a mixture of Pending tapes from before and after the big change, then you can easily tell which ones you need to relabel - they will be the ones that are both Pending and Readonly. When this happened to me, it was a hassle, but I found that it was a manageable hassle. I did not have to do anything as drastic as the backout you did. Sorry to hear about that - because you are having to do 3 times the work with a migrate-backout-migrate cycle. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] On Sat, 25 Mar 2006, Farren Minns wrote: OK, this is what I have now found out but had no idea what's going on. After completely removing and redefining the lib,drives and paths I still get the same errors as below. So, for example I can't audit volume 000700 without the error below. BUT..., if I change the state of the volume from read/write to readonly, I can. What's that all about? I can also audit volumes that have an access of read/write but that are 'full' and not 'filling'. This is very strange. Has anyone else ever seen this behaviour before ? Many thanks again Farren Minns Hi All I have just moved my TSM Server 5.1.6.2 from a Solaris 7 server to a new Solaris 9 box. Now, everything so far has gone fine and I have tested a couple of backups and also a backup of the database. When I look at the contents of the tapepool, copypool, q libv etc I see what I would expect. BUT, when I try to run migration from disk to tape there is a problem. In this example tape 000700 which is in a filling state is required but I see the following error :- ANR1000I Migration process 4 started for storage pool BACKUPPOOL. ANR8447E No drives are currently available in library 3494A. ANR1401W Mount request denied for volume 000700 - mount failed. Instead, TSM loads a new scratch tape and then continues fine. What
New Question Re - Tape problem after moving TSM to new server
Trying to run TSM 5.1.6.2 on Solaris 2.9 IBMtape version - 4.1.2.6 Hi All As this isn't strictly a TSM question I will understand if it gets ignored, but does anyone know how (or if it is even possible) to get Solaris to only use the IBMtape device drivers and not to also use the default Solaris SCSI tape drivers. If I could get the OS to do that, I would hope to see my two IBMtape drives assigned to 0 and 1 (0stc, 1stc) again, and this would save me a lot of extra work. If there are any Solaris people out there that can help me with this it was be awesome. Many thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Tape problem after moving TSM to new server
Hi All I have just moved my TSM Server 5.1.6.2 from a Solaris 7 server to a new Solaris 9 box. Now, everything so far has gone fine and I have tested a couple of backups and also a backup of the database. When I look at the contents of the tapepool, copypool, q libv etc I see what I would expect. BUT, when I try to run migration from disk to tape there is a problem. In this example tape 000700 which is in a filling state is required but I see the following error :- ANR1000I Migration process 4 started for storage pool BACKUPPOOL. ANR8447E No drives are currently available in library 3494A. ANR1401W Mount request denied for volume 000700 - mount failed. Instead, TSM loads a new scratch tape and then continues fine. What is going on here? Has any body seen this before? Thanks in advance Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Update - Tape problem after moving TSM to new server
OK, this is what I have now found out but had no idea what's going on. After completely removing and redefining the lib,drives and paths I still get the same errors as below. So, for example I can't audit volume 000700 without the error below. BUT..., if I change the state of the volume from read/write to readonly, I can. What's that all about? I can also audit volumes that have an access of read/write but that are 'full' and not 'filling'. This is very strange. Has anyone else ever seen this behaviour before ? Many thanks again Farren Minns Hi All I have just moved my TSM Server 5.1.6.2 from a Solaris 7 server to a new Solaris 9 box. Now, everything so far has gone fine and I have tested a couple of backups and also a backup of the database. When I look at the contents of the tapepool, copypool, q libv etc I see what I would expect. BUT, when I try to run migration from disk to tape there is a problem. In this example tape 000700 which is in a filling state is required but I see the following error :- ANR1000I Migration process 4 started for storage pool BACKUPPOOL. ANR8447E No drives are currently available in library 3494A. ANR1401W Mount request denied for volume 000700 - mount failed. Instead, TSM loads a new scratch tape and then continues fine. What is going on here? Has any body seen this before? Thanks in advance Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re - Tape problem after moving TSM to new server
Hi Richard Well sadly for now I have had to revert to the old server again for tonights backups. All I can do now is try and work out exactly what is going on and try to have some kind of a plan to pre-empt this caveat. As far as the Private and Scratch category goes, the new settings (within TSM) were the same as for the old server so I don't think it could be that. But I will need to go through my current server with a fine tooth comb and pick out any info I may possibly need. You mention finding out the category code of volume using the mtlib command. I know a few mtlib commands that I have been using, but not one that shows the category? Also, do you think it would be necessary for me to delete and redefine the deviceclass just as I did with the lib,drives, paths etc? And, If I did that, would it trash my tapepool, copypool etc? Sorry for the all the questions but I'm tearing my hair out. It was all going so well :-) Many thanks Farren Minns |-+---| | Richard Sims [EMAIL PROTECTED] | | | | | | 25/03/2006 15:31 | To| | |Farren Minns | | |[EMAIL PROTECTED]| | | | | | cc| | | | | |Subject| | |Re: Tape problem | | |after moving TSM to| | |new server | | | | | | | | | | | | | | | | | | | |-+---| On Mar 25, 2006, at 9:59 AM, Farren Minns wrote: ANR8447E No drives are currently available in library 3494A. This kind of message is often a conflict involving devclass, made confusing because the message doesn't say as much as it could. Generically, it means that TSM thinks there are no drives of the correct *type* for the media involved. In a 3494, with its Category Codes, it may mean that the tapes ended up with a Category Code value which differs from those in the TSM Library definition. In this case, do Query LIBRary and compare the Private and Scratch categories against what the tapes actually have, as reported via the mtlib command. Whereas you can mount scratches, it suggests that your Private category code values may be off. Beyond that, query your devclass configs and compare to what your full/filling tapes show for devclass. Whereas you moved to a new Solaris platform, there may be subtle differences in the drive definitions which are causing problems. Do a SHow LIBRary and compare against your OS display of tape drive definitions. Richard ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Re - Tape problem after moving TSM to new server
Thanks Ben For now I have brought the old server up again and everything is working fine, so I am happy that the library is not doing anything silly (well, reasonably happy). I have been given a few pointers here to look at but sadly I think it will be a case of trying this all again next weekend and trying to figure out the problem as I go along. Many thanks to all for your help. I'm sure I will have more questions throughout the coming week. Farren Minns Sys Admin/Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Ben Bullock | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 25/03/2006 18:55 |Subject| | | Re: [ADSM-L] Re - Tape | | Please respond to | problem after moving TSM | | ADSM: Dist Stor| to new server | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| mtlib -l /dev/lmcp0 -q I will show you the inventory categories for the tapes. You have to translate it from HEX to check if it matches up with the TSM server categories. This is probably not your issue, but I will document it here just in case. If you see a lot of FFFA, FFFB or FF00, the library might have lost it's categories. It only happens to us once in a while when the PC in the library goes very bad, or when an admin accidentally does a reinventory all on the back of the library instead of doing an update inventory. Either way, if that happens you can get a listing from TSM with a q libvol and then apply your scratch and private categories back onto the library with the mtlib -l /dev/lmcp0 -C -VTAPE -tHEX. It is simple to script. Ben -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Saturday, March 25, 2006 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: Re - Tape problem after moving TSM to new server Hi Richard Well sadly for now I have had to revert to the old server again for tonights backups. All I can do now is try and work out exactly what is going on and try to have some kind of a plan to pre-empt this caveat. As far as the Private and Scratch category goes, the new settings (within TSM) were the same as for the old server so I don't think it could be that. But I will need to go through my current server with a fine tooth comb and pick out any info I may possibly need. You mention finding out the category code of volume using the mtlib command. I know a few mtlib commands that I have been using, but not one that shows the category? Also, do you think it would be necessary for me to delete and redefine the deviceclass just as I did with the lib,drives, paths etc? And, If I did that, would it trash my tapepool, copypool etc? Sorry for the all the questions but I'm tearing my hair out. It was all going so well :-) Many thanks Farren Minns |-+---| | Richard Sims [EMAIL PROTECTED] | | | | | | 25/03/2006 15:31 | To| | | Farren Minns | | | [EMAIL PROTECTED]| | | | | | cc| | | | | | Subject| | | Re: Tape problem | | | after moving TSM to| | | new server
Upgrade possible downgrade questions.
Hi all This Saturday I will finally be moving from an on Solaris 7 server (TSM 5.1.6.2) to a new Solaris 9 (TSM 5.2.2.7) one. My question this time regards downgrading from 5.2.2.7 to 5.1.6.2 should I need to. Do I need to physically remove any existing dB and log volumes as well as un-install the software and then re-format them? Or, once I have installed 5.1.6.2 again, can I just issue a dsmserv restore db command and it will happily use the space previously used by 5.2.2.7? From the documentation it says to 'Reinitialize any database and recovery log volumes ' which I'm assuming means to remove and reformat. Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Upgrade possible downgrade questions.
Hi Henrik I have had a few comments now regarding upgrading Hardware/OS and TSM at the same time not being the best idea so I am going to get TSM running as it is now but on the new hardware/OS and then upgrade TSM a week or so later. Many thanks for the advice Farren |-+---| | Henrik Wahlstedt | | | [EMAIL PROTECTED]| | | Sent by: ADSM: Dist Stor | To| | Manager |ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 21/03/2006 11:21 |Subject| | |Re: [ADSM-L] Upgrade | | Please respond to |possible downgrade | | ADSM: Dist Stor|questions. | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Hi Farren, Downgarding? You cant if you dont have an DB backup that was taken in the earlier format, 5.1.6.2. I´m not so sure what you are trying to do but...in short. Do: Solaris 7, 5.1.6.2 Migrate all data from disk stgpools and backup DB. Halt Restore Db to the new server, Solaris 9, 5.1.6.2 Connect libraries etc. Define new disk stgpools Verfy and test. If not OK fall back to the old solution. If OK Next week, upgrade to Solaris 9, 5.2.2.7 And yes, format new volumes before you restore your DB. Secondly, dont do everything att the same time ie upgrade TSM and change your hardware. //Henrik -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: den 21 mars 2006 09:51 To: ADSM-L@VM.MARIST.EDU Subject: Upgrade possible downgrade questions. Hi all This Saturday I will finally be moving from an on Solaris 7 server (TSM 5.1.6.2) to a new Solaris 9 (TSM 5.2.2.7) one. My question this time regards downgrading from 5.2.2.7 to 5.1.6.2 should I need to. Do I need to physically remove any existing dB and log volumes as well as un-install the software and then re-format them? Or, once I have installed 5.1.6.2 again, can I just issue a dsmserv restore db command and it will happily use the space previously used by 5.2.2.7? From the documentation it says to 'Reinitialize any database and recovery log volumes ' which I'm assuming means to remove and reformat. Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## --- The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Thank you. ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus
Re: New TSM Server, DB and STG POOL question
That's exactly what I am expecting too. I assume that you can have a library SCSI attached as opposed to LAN (as I have). But in my case SCSI target IDs etc do not matter as I only point to an alias defined in the ibmatl.conf file. I also will have to change the drives from /dev/rmt/0stc,1stc to 2 and 3stc, but apart from that everything else will be just as it was. I'm even bringing the new server up the with the same name and IP address as the old one. From the testing I have done so far I know I can restore the dB so communication with the drives is OK, and I tested a few mtlib commands and they worked too, so all should be OK... fingers crossed :-) As it stands the old server will still be there should I need to go back to it after a couple of days. I realise that this safety net will only be available for a few days but I should find out pretty quick if there are problems contacting the lib/drives etc. Many thanks again to everyone who has helped me with this and by all means if I am still missing something and if there really is a need to remove/redefine the drives,lib paths etc then I'd still be very interested to hear it. All the best Farren Minns |-+---| | Dirk Kastens | | | [EMAIL PROTECTED]| | | CK.DE| To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 20/03/2006 08:32 | Re: [ADSM-L] New TSM | | | Server, DB and STG| | Please respond to | POOL question | | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Farren Minns wrote: I may be missing something here of course. I also don't see a need for deleting and redefining the paths, drives and libraries. As I said, I connected our library from the old (AIX5.1) to the new server (AIX5.3). Although the AIX devices changed from rmt1-rmt6 to rmt0-rmt5, and although I renamed the TSM drives from DRIVE1-DRIVE6 to DRIVE0-DRIVE5, as soon as I restored the database on the new server, TSM was running without problems. There were no tapes missing and all backups and restores were running as if nothing happened. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: New TSM Server, DB and STG POOL question
Hi there Thanks for that but I'm still confused. I have already installed 5.1.6.2 on the new server and restored the dB etc to make sure that the old and new servers are exactly the same. I then upgraded to 5.2.2 and then to 5.2.2.7 without any problems (this is all just a test as the original server is still in use). Now, when I look at the tapepool I see the exact volumes I am expecting to see. Also, when I use the mtlib commands from the command line (or qlibv from within TSM), to interrogate the library I see exactly what I did when connected to the old server. So from that I would assume that both TSM and the server can still see exactly what tape volumes are where just as they did on the old server. Also, the new definitions for the drives,path,lib etc are going to be exactly the same on the new server (as they are going to be connected to the same drives and lib as before), so what does deleting and redefining actually change? The only think that will be different is that the old drives were /dev/rmt/0stc and 1stc but will now be 2stc and 3stc which I will change. Sorry, I'm not doubting you here, I'm just trying to get my head around things as this is something new I hadn't considered. Many thanks Farren Minns |-+---| | Roger Deschner| | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 17/03/2006 16:01 |Subject| | | Re: [ADSM-L] New TSM | | Please respond to | Server, DB and STG| | ADSM: Dist Stor| POOL question | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Prior to TSM 5 you could get away with just an inventory, but now it has become necessary to delete and redefine the paths, which will wipe out all your libvols. (TSM 4 didn't even have paths.) It is critical to do the two checkin libvol commands in the order in your list - scratch first, and then private - otherwise you will lose all your scratch tapes. TEST the checkin libvol step FIRST! I have been bitten badly, twice, by failures in the driver or the library itself preventing checkin libv from working. This has caused us long milti-day downtimes twice during the past year. This happened to us with a simple tape library upgrade, adding more slots to the same Quantum P7000 library. The danger you run is that with new versions of both Solaris and TSM, you are running different drivers, which could make library operations fail. Make sure this is going to work before you get into a situation where you can't back out. If things go wrong in this area you face a LONG downtime with a LOT of finger-pointing between IBM/Tivoli, Sun, and your tape library maker. They will each blame somebody else. It will get very ugly. Other than that, you are changing too many things at once for comfort. Last time I made a server change, I took great pains to insure that the TSM and AIX versions on the old and new servers were identical. At least this way, you can limit the scope of what went wrong. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] Anything you try to fix will take longer and cost more than you thought. On Thu, 16 Mar 2006, Farren Minns wrote: TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 Hi all Regarding Anton's check list below, I have a couple of questions. 1) Do I really need to delete and redefine the drives,libray,paths etc? I understand that I will need to update the /dev/rmt/??? entry for the drives to make sure they reflect how the drives are viewed on the new system. But apart from that things should in my mind be exactly the same as before. As far as the library is concerned, it's just an alias in the ibmatl.conf file anyway and I know that works as I can use the mtlib command to interrogate it. Am I missing something? and... 2) Do I really need to run the 'checkin libv' commands. Looking at the newly restored system I can see that TSM knows all the vols in the TAPEPOOL and also
Re: New TSM Server, DB and STG POOL question
Hi me again From the points on the list (below) is says to delete and redefine the lib,drives etc because of possible changed scsi-id's, but the library is referred to by it's alias in the ibmatl.conf file, and this alias will be the same on the new server. I know this works as I can use the mtlib command to speak to it. So I really can't see a reason to redefine, and thus I wont have to checkin the vols again. I may be missing something here of course. 15. delete all paths, drives and libraries 16. define all paths, libraries and drives again you must do step 15. and 16. because of possible changed scsi-id's 17. checkin libv library search=yes status=scratch checklabel=barcode 18. checkin libv library search=yes status=private checklabel=barcode Many thanks Farren |-+---| | Roger Deschner| | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 17/03/2006 16:01 |Subject| | | Re: [ADSM-L] New TSM | | Please respond to | Server, DB and STG| | ADSM: Dist Stor| POOL question | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Prior to TSM 5 you could get away with just an inventory, but now it has become necessary to delete and redefine the paths, which will wipe out all your libvols. (TSM 4 didn't even have paths.) It is critical to do the two checkin libvol commands in the order in your list - scratch first, and then private - otherwise you will lose all your scratch tapes. TEST the checkin libvol step FIRST! I have been bitten badly, twice, by failures in the driver or the library itself preventing checkin libv from working. This has caused us long milti-day downtimes twice during the past year. This happened to us with a simple tape library upgrade, adding more slots to the same Quantum P7000 library. The danger you run is that with new versions of both Solaris and TSM, you are running different drivers, which could make library operations fail. Make sure this is going to work before you get into a situation where you can't back out. If things go wrong in this area you face a LONG downtime with a LOT of finger-pointing between IBM/Tivoli, Sun, and your tape library maker. They will each blame somebody else. It will get very ugly. Other than that, you are changing too many things at once for comfort. Last time I made a server change, I took great pains to insure that the TSM and AIX versions on the old and new servers were identical. At least this way, you can limit the scope of what went wrong. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] Anything you try to fix will take longer and cost more than you thought. On Thu, 16 Mar 2006, Farren Minns wrote: TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 Hi all Regarding Anton's check list below, I have a couple of questions. 1) Do I really need to delete and redefine the drives,libray,paths etc? I understand that I will need to update the /dev/rmt/??? entry for the drives to make sure they reflect how the drives are viewed on the new system. But apart from that things should in my mind be exactly the same as before. As far as the library is concerned, it's just an alias in the ibmatl.conf file anyway and I know that works as I can use the mtlib command to interrogate it. Am I missing something? and... 2) Do I really need to run the 'checkin libv' commands. Looking at the newly restored system I can see that TSM knows all the vols in the TAPEPOOL and also the qlibv command shows me the volumes I also see on the still live server. Again, am I missing something? Many thanks again for this list Anton, much appreciated. All the best Farren Minns |-+---| | anton walde | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU | cc
Re: New TSM Server, DB and STG POOL question
TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 Hi all Regarding Anton's check list below, I have a couple of questions. 1) Do I really need to delete and redefine the drives,libray,paths etc? I understand that I will need to update the /dev/rmt/??? entry for the drives to make sure they reflect how the drives are viewed on the new system. But apart from that things should in my mind be exactly the same as before. As far as the library is concerned, it's just an alias in the ibmatl.conf file anyway and I know that works as I can use the mtlib command to interrogate it. Am I missing something? and... 2) Do I really need to run the 'checkin libv' commands. Looking at the newly restored system I can see that TSM knows all the vols in the TAPEPOOL and also the qlibv command shows me the volumes I also see on the still live server. Again, am I missing something? Many thanks again for this list Anton, much appreciated. All the best Farren Minns |-+---| | anton walde | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 15/03/2006 15:44 |Subject| | | Re: [ADSM-L] New TSM | | Please respond to | Server, DB and STG| | ADSM: Dist Stor| POOL question | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Hallo. We changed our Hardware a year ago. We asked support to help us and got a good hand-out with all the steps to make. Here is the 'cook book': 1. you must have the samt TSM-Version on the old and new server. 2. migrate all diskpools to tape 3. backup the TSM-DB on the old server maybe to a file-devclass ( better for restore ) 4. stop the old server 5. save all the config-files from the old server ( dsmserv.opt,dsmserv.dsk,devconfig.out,volhist.out,nodelock ) 6. connect the libraryies to the new server 7. install the tsm device driver on the new server all the following steps are on the new server 8. copy the config-files from step 5. to the new server, over the existing! 9. create log-files and db-files with dsmserv format 10. check the config-files! for example the devconfig.out for devclass,devices,pathes,etc. 11. restore the db from step 3. 12. change dsm.opt: nomigrrecl expinterval = disablescheds yes 13. start the tsm-server in foreground ( dsmserv ) 14. disable sessions 15. delete all paths, drives and libraries 16. define all paths, libraries and drives again you must do step 15. and 16. because of possible changed scsi-id's 17. checkin libv library search=yes status=scratch checklabel=barcode 18. checkin libv library search=yes status=private checklabel=barcode 19. create the diskpools. If you have another directory-name for the volumes, you must delete the old ones and define new ones. 20. If everything runs fine, stop the server ( halt server ), remove the options you defined in step 12 from dsm.opt and start the tsm-server as a service like you did on the old hardware THAT'S IT! Hope that helps you. Kind regards Robert Fijan -- Bis zu 70% Ihrer Onlinekosten sparen: GMX SmartSurfer! Kostenlos downloaden: http://www.gmx.net/de/go/smartsurfer ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: New TSM Server, DB and STG POOL question
Hi Dirk OK, I'm assuming that in this case I could install 5.1.6.2 on the new server, restore the dB, upgrade to 5.1.10 and then do the cleanup backupgroups rather than upgrading the old server? The reason being that as 5.1 is out of support, and as our present server has been running like a dream for years I don't want to risk breaking anything. In this way, if there are any serious problems I can just bring the old server back into action until I can sort the problem. Many thanks for your help Farren Minns |-+---| | Dirk Kastens | | | [EMAIL PROTECTED]| | | CK.DE| To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 16/03/2006 10:34 | Re: [ADSM-L] New TSM | | | Server, DB and STG| | Please respond to | POOL question | | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Farren, Farren Minns schrieb: TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 One point is missing: you should first update the old server to TSM 5.1.10 and run a cleanup backupgroups before you go to version 5.2.x. Theres a good PowerPoint presentation: http://www-1.ibm.com/support/docview.wss?uid=swg21214007aid=1 Then you could a) upgrade the old server to 5.2.7 and do the migration, or b) install TSM 5.1.10 on the new server, do the migration and upgrade to 5.2.7. That's what I did (I went to 5.3.2). Our new server is much faster than the old one. So I thought it was a better idea to let the new server do the software upgrade. 1) Do I really need to delete and redefine the drives,libray,paths etc? I didn't have to delete the drives etc. For restoring the db on the new server you only need the library and one drive defined in your new TSM server. After restoration (or before) you can define the other drives. 2) Do I really need to run the 'checkin libv' commands. No. You also do not need to copy the dsmserv.dsk to the new server. This could be confusing if you have different db and log volumes defined on the new server. You will need the volume history file so that the dsmserv restore db command will know what tapes to use. You can check it with dsmserv restore db todate=today preview=yes -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: New TSM Server, DB and STG POOL question
Hi again I have just been having a look at the powerpoint presentation and it says that the 'cleanup backupgroups' job runs as part of an upgrade to 5.2/5.3 anyway but that it can increase the length of time to covert the database. However, I have already tested going from 5.1.6.2 to 5.2.2.7 on this new server an the upgrade only took about 15mins (I only have a small database of 15GB). So do you think I can be confident that this is OK, or should I add the 5.1.10 step anyway? Thanks Farren Minns |-+---| | Dirk Kastens | | | [EMAIL PROTECTED]| | | CK.DE| To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 16/03/2006 10:34 | Re: [ADSM-L] New TSM | | | Server, DB and STG| | Please respond to | POOL question | | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Farren, Farren Minns schrieb: TSM 5.1.6.2 on Solaris 2.7 - moving to 5.2.7.0 on Solaris 2.9 One point is missing: you should first update the old server to TSM 5.1.10 and run a cleanup backupgroups before you go to version 5.2.x. Theres a good PowerPoint presentation: http://www-1.ibm.com/support/docview.wss?uid=swg21214007aid=1 Then you could a) upgrade the old server to 5.2.7 and do the migration, or b) install TSM 5.1.10 on the new server, do the migration and upgrade to 5.2.7. That's what I did (I went to 5.3.2). Our new server is much faster than the old one. So I thought it was a better idea to let the new server do the software upgrade. 1) Do I really need to delete and redefine the drives,libray,paths etc? I didn't have to delete the drives etc. For restoring the db on the new server you only need the library and one drive defined in your new TSM server. After restoration (or before) you can define the other drives. 2) Do I really need to run the 'checkin libv' commands. No. You also do not need to copy the dsmserv.dsk to the new server. This could be confusing if you have different db and log volumes defined on the new server. You will need the volume history file so that the dsmserv restore db command will know what tapes to use. You can check it with dsmserv restore db todate=today preview=yes -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: New TSM Server, DB and STG POOL question
I guess an interim upgrade to 5.1.10 and the clean-up will be pretty quick anyway so maybe I'll do it anyway just to make sure all is as clean as possible. If something's worth doing... All the best Farren |-+---| | Dirk Kastens | | | [EMAIL PROTECTED]| | | CK.DE| To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 16/03/2006 11:33 | Re: [ADSM-L] New TSM | | | Server, DB and STG| | Please respond to | POOL question | | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Farren Minns wrote: So do you think I can be confident that this is OK, or should I add the 5.1.10 step anyway? Maybe someone from IBM should answer this. If you have tested the upgrade before, it should be ok. The cleanup command only took a few minutes on our old server, so the upgrade could have been done without this step. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
New TSM Server, DB and STG POOL question
Hi All I'm running TSM on Solaris 2.7 and moving to Solaris 2.9 on a new physical server. If moving a TSM server from one machine to another, do you format space for the backup pools first, then do the restore, or do you restore your DB first and then format space for the backup pool and archive pool? I installed TSM and then formatted all the space necessary for the log and db vols, backuppool and archive devices. I then restored the db, but when I start the new TSM server instance I am seeing messages such as the following :- 03/15/06 12:50:53 ANR1315E Vary-on failed for disk volume /usr/tsmdata/back- up01.dsm - invalid label block. Now I'm guessing this is because TSM on the old server (and hence the db) knows nothing about this new device, so do I just create the disk pools after restore? Many thanks Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: New TSM Server, DB and STG POOL question
Thanks Dirk Well I set caching to off on the disk pool on the original server and then migrated down to zero before doing the DB backup. So I'm thinking that if I now just format the vols I need on the new server, it should be fine. As it is this is just a test and I'll do the proper upgrade at the weekend, so fingers crossed. Many thanks Farren |-+---| | Dirk Kastens | | | [EMAIL PROTECTED]| | | CK.DE| To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU | | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 15/03/2006 14:17 | Re: [ADSM-L] New TSM | | | Server, DB and STG| | Please respond to | POOL question | | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| I wrote: I first deleted all disk storage pools on the old server, CAUTION!!! Of yourse, I only deleted the disk pool volumes, NOT the storage pools themselves. -- Regards, Dirk Kastens Universitaet Osnabrueck, Rechenzentrum (Computer Center) Albrechtstr. 28, 49069 Osnabrueck, Germany Tel.: +49-541-969-2347, FAX: -2470 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Client 5.1.6.0 Win 2000SP4 question
Morning all Quick question. I have just noticed that one of our windows 2000 clients (Client 5.1.6.0) seems to start up 7 separate sessions during archive or backup processing. Any ideas what setting would be causing this? Many thanks Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Client 5.1.6.0 Win 2000SP4 question
Ahh, that might be it. As soon as I can get one of the sys admin guys to give me some time, I'll get them to check that. Many thanks Farren |-+---| | PAC Brion Arnaud | | | [EMAIL PROTECTED]| | | M| To| | Sent by: ADSM: Dist Stor | ADSM-L@VM.MARIST.EDU| | Manager | cc| | ADSM-L@VM.MARIST.EDU| | | |Subject| | 27/02/2006 11:06 | Re: [ADSM-L] Client | | | 5.1.6.0 Win 2000SP4 | | Please respond to | question| | ADSM: Dist Stor| | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | |-+---| Farren, Maybe RESOURCEUTILIZATION in dsm.opt ? Cheers. Arnaud ** Panalpina Management Ltd., Basle, Switzerland, CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01 Direct: +41 (61) 226 19 78 e-mail: [EMAIL PROTECTED] ** -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Monday, 27 February, 2006 11:28 To: ADSM-L@VM.MARIST.EDU Subject: Client 5.1.6.0 Win 2000SP4 question Morning all Quick question. I have just noticed that one of our windows 2000 clients (Client 5.1.6.0) seems to start up 7 separate sessions during archive or backup processing. Any ideas what setting would be causing this? Many thanks Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
TSM 5.1 to 5.2.7.0 steps
Hi all Running TSM 5.1.6.2 On Solaris 2.7. Upgrading to 5.2.7.0 on Solaris 9 Can I upgrade from 5.1.6.2 to 5.2.0 and then directly to 5.2.7.0 or are there any intermediate steps I need to go through? Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Tsm server v5.2.7 be ware
Hi Gary That's interesting and I remember your original post on this. How are you working round this in the mean time? Farren |-+---| | Lee, Gary D.| | | [EMAIL PROTECTED]| | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| MARIST.EDU| | | cc| | 08/02/2006 12:48 | | | |Subject| | Please respond to | [ADSM-L] | | ADSM: Dist Stor| Tsm server| | Manager| v5.2.7 be | | ADSM-L@VM.MARIST.EDU | ware | | | | | | | | | | | | | | | | | | | |-+---| Just ran into this a couple of weeks ago. Server v5.2.7 on solaris 2.8. However looks like it effects all platforms. Below is the message from tsm support I received last night. --- cut here - Gary, I have researched this problem further and found that there is an APAR for this problem. APAR IC48456 addresses this problem: http://www-1.ibm.com/support/docview.wss?rs=0q1=%2bIC48456uid=swg1IC48456loc=en_UScs=utf-8cc=uslang=all This is projected to be fixed in version 5.2.8. I will monitor the progress of this APAR for you. Hope this helps someone out there. Gary Lee Senior System Programmer Ball State University -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/253 - Release Date: 2/7/2006 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Tsm server v5.2.7 be ware
Sorry, just read the APAR and I see I just need to increase the MAXSCRATCH variable. Farren |-+---| | Lee, Gary D.| | | [EMAIL PROTECTED]| | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| MARIST.EDU| | | cc| | 08/02/2006 12:48 | | | |Subject| | Please respond to | [ADSM-L] | | ADSM: Dist Stor| Tsm server| | Manager| v5.2.7 be | | ADSM-L@VM.MARIST.EDU | ware | | | | | | | | | | | | | | | | | | | |-+---| Just ran into this a couple of weeks ago. Server v5.2.7 on solaris 2.8. However looks like it effects all platforms. Below is the message from tsm support I received last night. --- cut here - Gary, I have researched this problem further and found that there is an APAR for this problem. APAR IC48456 addresses this problem: http://www-1.ibm.com/support/docview.wss?rs=0q1=%2bIC48456uid=swg1IC48456loc=en_UScs=utf-8cc=uslang=all This is projected to be fixed in version 5.2.8. I will monitor the progress of this APAR for you. Hope this helps someone out there. Gary Lee Senior System Programmer Ball State University -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.375 / Virus Database: 267.15.2/253 - Release Date: 2/7/2006 ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Tsm server v5.2.7 be ware
Hi Gary I'm am going to be installing on a Solaris 2.9 server. I have the 5.2.2 CD media too, so maybe I'll give that a go first and then decide what to do. Not sure if I should go to 5.2.7 now or wait for the next fix. All the best Farren |-+---| | Lee, Gary D.| | | [EMAIL PROTECTED]| | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| IST.EDU | | | cc| | 08/02/2006 13:57 | | | |Subject| | Please respond to | Re: [ADSM-L] | | ADSM: Dist Stor| Tsm server | | Manager| v5.2.7 be| | ADSM-L@VM.MARIST.EDU | ware | | | | | | | | | | | | | | | | | | | |-+---| Sir: According to ibm's apar, it is a problem decrementing the volumes used count after the volume is deleted. There are two possible fixes here. 1. reboot server frequently. 2. increase your maxscratch settting on tape pools to such a degree that you will never come close. Number 2 has a problem if you have only a limited number of scratch tapes. Tsm often pulls a scratch when many parcially fillled tapes are still available, and thus you have tape leak See Richard's quickfacts for more info on this phenomenon. I chose option 2, increasing maxscratch. I am using a 3494, and we are changing to 3590e drives from b. This will effectively double our stape capacity in one fell swoop. By the way, I upgraded from 5.1.9 to 5.2.2 using the installation cd, then installed 5.2.4 over the top with no major problems. What version of solaris are you using? Gary Lee Senior System Programmer Ball State University -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: Wednesday, February 08, 2006 8:42 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Tsm server v5.2.7 be ware Sorry, just read the APAR and I see I just need to increase the MAXSCRATCH variable. Farren |-+---| | Lee, Gary D. | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU | MARIST.EDU| | | cc| | 08/02/2006 12:48 | | | | Subject| | Please respond to | [ADSM-L] | | ADSM: Dist Stor | Tsm server| | Manager | v5.2.7 be | | ADSM-L@VM.MARIST.EDU | ware | | | | | | | | | | | | | | | | | | | |-+---| Just ran into this a couple of weeks ago. Server v5.2.7 on solaris 2.8. However looks like it effects all platforms. Below is the message from tsm support I received last night. --- cut here - Gary, I have researched this problem further and found that there is an APAR for this problem. APAR IC48456 addresses this problem: http://www-1.ibm.com/support/docview.wss?rs=0q1=%2bIC48456uid=swg1IC48456loc=en_UScs=utf
Simple server GUI time-out question
Hi all I'm having a mental block. Which setting do I change to stop the server GUI from timing out so quickly? Many thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Simple server GUI time-out question
Doh! Thanks very much to you both. Farren |-+---| | Michael Garnebode | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 06/02/2006 09:33 |Subject| | | Re: [ADSM-L] Simple | | Please respond to | server GUI time-out | | ADSM: Dist Stor| question| | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Hi, look at SET WEBAUTHTIMEOUT (Set the Web Time-out Interval) regads Michael Garnebode Farren Minns [EMAIL PROTECTED] UK To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager [EMAIL PROTECTED] Subject .EDU [ADSM-L] Simple server GUI time-out question 06.02.2006 10:25 Please respond to ADSM: Dist Stor Manager Hi all I'm having a mental block. Which setting do I change to stop the server GUI from timing out so quickly? Many thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Database restore and mirrored volume question
Hi all Quick question, when setting up a new server and restoring the database, is it best to do the restore prior to setting up the mirrored copies, or does it not matter either way? Thanks Farren Minns ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Domino Client question
That's great. Thanks as always to all who have given me some pointers. Farren |-+---| | Helder Garcia | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager |[EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU|ARIST.EDU | | | cc| | 27/01/2006 17:30 | | | |Subject| | Please respond to |Re:| | ADSM: Dist Stor|[ADSM-L] | | Manager|Domino | | ADSM-L@VM.MARIST.EDU |Client | | |question | | | | | | | | | | | | | | | | | | | |-+---| You can use -servername option of dsmc, like ./dsmc -servername=DOMSRV1_ARCHIVE Servername option should be the name given by SERVERNAME stanza on your dsm.sys, it may be different of nodename. Or, you can make use of two option files: --- dsm.opt (content): servername DOMSRV1 --- dsm1.opt (content): servername DOMSRV1_ARCHIVE --- And call dsmc this way: ./dsmc -optfile=dsm1.opt Also, when I come to do a restore, how do I connect to a specific nodename? -- Helder Garcia ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Mac 5.2.3.12 point in time problem
Good morning all Just trying to a point in time restore from a 5.2.3.12 Client that is Unicode enabled. Now when I try to go back to 14 Jan at 06:00 I don't see the files I want even though I am also displaying active/inactive files. But, if I skip the point in time bit and just view active/inactive I see a number of versions of the files I want, some of which were indeed modified and backed up on Jan 13th. Has anyone else had similar problems or is it something I'm doing wrong? Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Mac Client 5.2.3.12 point in time problem
Hi Richard Well, looking at the dirs and files I can see the following :- 'Files' are bound to the following backup copy group. Version Data Exists - 3 Versions Data Deleted - 1 Retain Extra Versions - 180 Retain Only Version - 60 'Dirs' are bound to the following (this backup copy group was created for something else but as far as I'm aware dirs automatically bind to the backup copy group with the highest retention settings). Version Data Exists - 3 Versions Data Deleted - 1 Retain Extra Versions - 180 Retain Only Version - 751 So, looking at the above I can see no reason why there would ever be a situation where a required dir would not exist for a required file as we always keep the only last remaining copy for 751 days. Also, when using the GUI, I can still see the files when viewing active/inactive, just not when adding in the point in time too. Sorry, just struggling to get my head round this. Many thanks for your help Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU|[EMAIL PROTECTED]| | |U | | 27/01/2006 12:35 | cc| | | | | Please respond to |Subject| | ADSM: Dist Stor|Re: [ADSM-L] Mac | | Manager|5.2.3.12 point in | | ADSM-L@VM.MARIST.EDU |time problem | | | | | | | | | | | | | | | | | | | |-+---| On Jan 27, 2006, at 7:01 AM, Farren Minns wrote: Good morning all Just trying to a point in time restore from a 5.2.3.12 Client that is Unicode enabled. Now when I try to go back to 14 Jan at 06:00 I don't see the files I want even though I am also displaying active/inactive files. But, if I skip the point in time bit and just view active/inactive I see a number of versions of the files I want, some of which were indeed modified and backed up on Jan 13th. Has anyone else had similar problems or is it something I'm doing wrong? This question comes up at least once a week, and almost always involves GUI use in conjunction with faulty directory retention policies, where the GUI needs to iteratively query the server for directory structure information as it drills down through the file system, and directories are missing. The client manuals, Technotes, APARs, Oxford, and SHARE presentations tell of this. Here is what the Mac client manual says: Note: If there are no backup versions of a directory for the point-in- time you specify, files within that directory are not restoreable from the GUI. However, you can restore these files from the command line. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Mac Client 5.2.3.12 point in time problem
Thanks Richard I can confirm that the files and dirs are bound to the correct policy values and that we do not have a DIRMc setting in place. Thanks for your help and I'll have a look at that technote now. Regards Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU | | | cc| | 27/01/2006 14:07 | | | |Subject| | Please respond to | Re: [ADSM-L] Mac | | ADSM: Dist Stor| Client 5.2.3.12 point | | Manager| in time problem | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Jan 27, 2006, at 8:36 AM, Farren Minns wrote: Hi Richard Well, looking at the dirs and files I can see the following :- 'Files' are bound to the following backup copy group. Version Data Exists - 3 Versions Data Deleted - 1 Retain Extra Versions - 180 Retain Only Version - 60 'Dirs' are bound to the following (this backup copy group was created for something else but as far as I'm aware dirs automatically bind to the backup copy group with the highest retention settings). ...unless instructed otherwise via DIRMc, per client manual and Admin Guide. Version Data Exists - 3 Versions Data Deleted - 1 Retain Extra Versions - 180 Retain Only Version - 751 So, looking at the above I can see no reason why there would ever be a situation where a required dir would not exist for a required file as we always keep the only last remaining copy for 751 days. Also, when using the GUI, I can still see the files when viewing active/inactive, just not when adding in the point in time too. Adding PIT makes the operation much more restrictive, and requires existence of the directory instance which matches that time period. Irregularities can screw this arrangement up, as for example system clock values having been incorrect at backup time. Rather than inspecting current policy values and what you think should have happened, you need to inspect the actual assignments of the (surviving) directory objects in TSM storage. Current policy values are just that: changes to policies over time, and unexpected bindings, can be the cause of expired objects. Have a look at Technote 1162784 as well, where IBM lays out the issue. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Domino Client question
Hi all Can anyone tell me where I find information on setting up a client with two different node names etc. I'm looking in the BA client manual but not finding anything that looks relevant. Many thanks Farren |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager |[EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU|ARIST.EDU | | | cc| | 26/01/2006 16:06 | | | |Subject| | Please respond to |Re:| | ADSM: Dist Stor|[ADSM-L] | | Manager|Domino | | ADSM-L@VM.MARIST.EDU |Client | | |question | | | | | | | | | | | | | | | | | | | |-+---| Hi Farren, For long-term archival, you should still use the Data Protection for Domino client because you want to make sure that the databases being backed up have full integrity. Many customers accomplish this by setting up a secondary TSM NODENAME like DOMSRV1_ARCHIVE and perform a monthly Data Protection for Domino backup using a different nodename with different policy setting to meet their longterm archival needs. Another thing you can look at is IBM DB2 CommonStore for Lotus Domino: http://www-306.ibm.com/software/data/commonstore/lotus/ Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/26/2006 10:56:41 AM: Hi Del OK, that all makes sense, but in this case where we are doing full backups every weekend, and if we wanted to keep data for a year (at least) we are going to end up with 52 full copies of the db in backup. Which again leads me to think that the domino client may not be the best tool for long term archive storage of data. Would I be right in thinking this, or is this the way things are generally done with domino databases? All the best Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Domino Client question
Hi So, I can have two nodenames pointing to one tsm sever i.e. pointing to the same tcpserveraddress? In my example I assume I would want to do the following. SErvername DOMSRV1 Nodename DOMSRV1 COMMmethod TCPip TCPPort 1500 TCPServeraddress tsmbackup passwordaccess generate schedlogname /opt/tivoli/tsm/client/ba/log/domsrv1_sched.log errorlogname /opt/tivoli/tsm/client/ba/log/domsrv1_error.log SErvername DOMSRV1_ARCHIVE Nodename DOMSRV1_ARCHIVE COMMmethod TCPip TCPPort 1500 TCPServeraddress tsmbackup passwordaccess generate schedlogname /opt/tivoli/tsm/client/ba/log/domsrv1_archive_sched.log errorlogname /opt/tivoli/tsm/client/ba/log/domsrv1_arch_error.log Will the TSM Server see this as two seperate clients? I'm wondering what I would see from a filesystem point of view. Also, when I come to do a restore, how do I connect to a specific nodename? Sorry for all the question. Farren |-+---| | Hooft, Jeroen | | | [EMAIL PROTECTED]| | | OM | To| | Sent by: ADSM: Dist Stor |[EMAIL PROTECTED]| | Manager |ARIST.EDU | | ADSM-L@VM.MARIST.EDU| cc| | | | | 27/01/2006 15:36 |Subject| | |Re:| | Please respond to |[ADSM-L] | | ADSM: Dist Stor|Domino | | Manager|Client | | ADSM-L@VM.MARIST.EDU |question | | | | | | | | | | | | | | | | | | | |-+---| Don't know the location of this mechanism in the manuals, but here is an example for AIX. The idea is that the same notes-system makes the backups using different nodenames. The idea is to have to different dsm.opt files. 1 for the normal and 1 for the longtime backups. In the dsm.sys file you will need a server entry for both dsm.opt files. dsm.sys SERVERNAME DOMSRV1 NODENAME DOMSRV1 tcpadd xxx etc... SERVERNAME DOMSRV1_ARCHIVE NODENAME DOMSRV1_ARCHIVE tcpadd xxx etc.. For the regular backups a reference to the default dsm.opt is made export DSMI_CONFIG=/path/dsm.opt For the long term archival, you refer before the backup to the other dsm.opt export DSMI_CONFIG=/path/dsm_archive.opt Regards Jeroen -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Farren Minns Sent: vrijdag 27 januari 2006 16:22 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Domino Client question Hi all Can anyone tell me where I find information on setting up a client with two different node names etc. I'm looking in the BA client manual but not finding anything that looks relevant. Many thanks Farren |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU | ARIST.EDU | | | cc| | 26/01/2006 16:06 | | | | Subject| | Please respond to | Re: | | ADSM: Dist Stor | [ADSM-L] | | Manager | Domino
Domino Client question
Hi all A user is trying to restore a lotus domino database on a Windows NT server, and when we look at active/inactive files, there are only five (we do full backups every weekend). So, my question here is where is it getting the 'keep 5 copies' from. The normal backup copy group for the server keeps 7 copies of all normal files, so I'm assuming it can't be this. Thanks in advance Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Domino Client question
Aaah, does the 'retextra' option override the 'versions data exists'? The 'retextra' for the default backup copy group is 30 and the 'versions data exists' is set to 7. But I assume if the databases are only backed up fully each week, there would never be any more than 4-5 active/inactive copies? Is my thinking correct? Thanks Farren |-+---| | Helder Garcia | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager |[EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU|ARIST.EDU | | | cc| | 26/01/2006 15:14 | | | |Subject| | Please respond to |Re:| | ADSM: Dist Stor|[ADSM-L] | | Manager|Domino | | ADSM-L@VM.MARIST.EDU |Client | | |question | | | | | | | | | | | | | | | | | | | |-+---| Check Retextra option on copygroup too. On 1/26/06, Farren Minns [EMAIL PROTECTED] wrote: Hi all A user is trying to restore a lotus domino database on a Windows NT server, and when we look at active/inactive files, there are only five (we do full backups every weekend). So, my question here is where is it getting the 'keep 5 copies' from. The normal backup copy group for the server keeps 7 copies of all normal files, so I'm assuming it can't be this. Thanks in advance Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## -- Helder Garcia ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Domino Client question
Ok, so now I know why we are only seeing the 5 files. But this has lead management to ask if this system of backing data up is really the best way forward. Sadly for me I wasn't involved in the set-up of the domino clients or the nature of the data being backed up, so I had no way of knowing there was a potential problem lurking in the background. So, in this instance users are scanning documents in (important contracts etc) that would clearly need to be kept for a lot longer than thirty days if they were deleted. So, is a domino client good for this? Would I realistically be looking to continue using the domino client to do the weekly incremental backups that we keep for up to 30 days, but then use the normal TSM client to do monthly archives of the databases that we then keep for a required amount of time? Or, can the domino client handle all of this? Thanks again for all your help Farren |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager |[EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU|ARIST.EDU | | | cc| | 26/01/2006 15:07 | | | |Subject| | Please respond to |Re:| | ADSM: Dist Stor|[ADSM-L] | | Manager|Domino | | ADSM-L@VM.MARIST.EDU |Client | | |question | | | | | | | | | | | | | | | | | | | |-+---| Hi Farren, Look in the DSM.OPT file for Data Protection for Domino. Are there any INCLUDE statements that are binding the backups to a different management class? If not, check to see what the default management class is for the Data Protection for Domino NODENAME. It may have a different default management class, with different default policies. Those are the two things I would look at first. Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/26/2006 09:38:24 AM: Hi all A user is trying to restore a lotus domino database on a Windows NT server, and when we look at active/inactive files, there are only five (we do full backups every weekend). So, my question here is where is it getting the 'keep 5 copies' from. The normal backup copy group for the server keeps 7 copies of all normal files, so I'm assuming it can't be this. Thanks in advance Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been
Re: Domino Client question
Hi Del OK, that all makes sense, but in this case where we are doing full backups every weekend, and if we wanted to keep data for a year (at least) we are going to end up with 52 full copies of the db in backup. Which again leads me to think that the domino client may not be the best tool for long term archive storage of data. Would I be right in thinking this, or is this the way things are generally done with domino databases? All the best Farren |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager |[EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU|ARIST.EDU | | | cc| | 26/01/2006 15:39 | | | |Subject| | Please respond to |Re:| | ADSM: Dist Stor|[ADSM-L] | | Manager|Domino | | ADSM-L@VM.MARIST.EDU |Client | | |question | | | | | | | | | | | | | | | | | | | |-+---| Hi Farren, Right. RETEXTRA says how long to keep the inactive versions. If you want to keep your database backups based on time, (which many customers do for Domino and Exchange, for example), you should set VEREXISTS to Nolimit and VERDELETED to Nolimit, and set the RETEXTRA and RETONLY to the length of time you want to save the backups. That way, if you need to do adhoc backups in the middle of the week for maintanence reasons, etc, you won't jeopardize your older backups, for forcing them to prematurely expire. Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/26/2006 10:21:31 AM: Aaah, does the 'retextra' option override the 'versions data exists'? The 'retextra' for the default backup copy group is 30 and the 'versions data exists' is set to 7. But I assume if the databases are only backed up fully each week, there would never be any more than 4-5 active/inactive copies? Is my thinking correct? Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Domino Client question
Thanks again Del That does sound like a better way forward, but can someone point me in the right direction of information on how to configure two TSM clients (nodenames), on one machine. This is not something I am familiar with? I'll start browsing the manuals I have anyway but first hand experience with this kind of thing is always a good point of reference. Thanks Farren |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager |[EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU|ARIST.EDU | | | cc| | 26/01/2006 16:06 | | | |Subject| | Please respond to |Re:| | ADSM: Dist Stor|[ADSM-L] | | Manager|Domino | | ADSM-L@VM.MARIST.EDU |Client | | |question | | | | | | | | | | | | | | | | | | | |-+---| Hi Farren, For long-term archival, you should still use the Data Protection for Domino client because you want to make sure that the databases being backed up have full integrity. Many customers accomplish this by setting up a secondary TSM NODENAME like DOMSRV1_ARCHIVE and perform a monthly Data Protection for Domino backup using a different nodename with different policy setting to meet their longterm archival needs. Another thing you can look at is IBM DB2 CommonStore for Lotus Domino: http://www-306.ibm.com/software/data/commonstore/lotus/ Thanks, Del Del Hoobler Tivoli Storage Manager Development IBM Corporation ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 01/26/2006 10:56:41 AM: Hi Del OK, that all makes sense, but in this case where we are doing full backups every weekend, and if we wanted to keep data for a year (at least) we are going to end up with 52 full copies of the db in backup. Which again leads me to think that the domino client may not be the best tool for long term archive storage of data. Would I be right in thinking this, or is this the way things are generally done with domino databases? All the best Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Rebuilding a TSM Server ?
Hi all *** TSM 5.1.6.2 on Solaris 2.7, moving to TSM 5.2.?.? on Solaris 2.9 *** OK, I'm in the process of building a new replacement TSM server (Solaris). When it's ready I will hopefully be able to turn the old machine off and bring the new one up again with the same host name/tcp address and away we'll all go. I have already got the server ready, patched, IBMTape and lmcpd drivers installed etc, so I'm about ready to move on to the TSM side of things. The procedures that I assume I now need to go through are as follows. Anything with a question mark is something I'm not sure about. 1) Install TSM - Done 2) Register necessary licenses 3) Define Tape/Library devices and paths for manual library ready for restore. 4) Create device configuration file for above and add entry into the dsmserv.opt file. 5) Copy volume history file from original server ? 6) Format Backuppool volume/s 7) Format Database volume/s 8) Format Log volume/s Question re above: If for example my present database is 10GB and made up of 5*2GB volumes, do I need to create the new volumes like for like or could I just create one 10GB volume. i.e. is it only important to make sure the necessary space is required and not the exact same volume layout. This question goes for backuppool, log and database volumes. 9) Restore database with the DSMSERV RESTORE DB command and utilizing the device config file pointed to by the dsmserv.opt file. 10) Alter the device configuration to change the library definition from 'manual' to '349X' to take our 3494 library into account. - also add the 'enable3590library yes' entry to the dsmserv.opt file. Does the above plan of action look about right or am I making it too simple. Just wondering if I'm missing something important. 11) At this point I will be ready to upgrade the TSM Server install from 5.1.6.2 Questions re above: a) Is it necessary to run an auditdb prior to doing this? b) What are peoples thoughts on the most stable 5.2 release to move to? Many thanks in advance for any advice. All the best Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Rebuilding a TSM Server ?
Thanks Len As far as moving the data off the backuppool prior to the restore of the db etc, does that just mean doing a full migration to take? I assume it does but am happy to ask again just to make sure :-) Farren |-+---| | len boyle | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| ST.EDU| | | cc| | 20/01/2006 13:34 | | | |Subject| | Please respond to | Re: [ADSM-L] | | ADSM: Dist Stor| Rebuilding a | | Manager| TSM Server ? | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| Good Morning Farren I am sure that you will get a number of good answers, but here are a few points. I am sure I will be corrected for any faults in my logic. It been a little while since I have had to move the tsm server to a new box and there may be newer better thoughts. When you create the space on the new server, you only have to create the same or greater for the log and db volumes. You can use a new layout based on your best thoughts for performance. For the storage pools you might want to move all data off the disk storage pool volumes before the move. Then you will not have do a restore of the storage pools after the tsm server is restored on the new server. Otherwise you will have to restore the disk storage pools after you restore your db and have a running system. But for the restore of the db you do not need your full operating size. For the initial set up of the tape library and drives, you only need to define one tape drive. After you restore the db, your old device configuration will be in effect. Which means if it is different you will have to delete and redefine the hardware to TSM. You might want to look at the redbook for TSM DR. len - Original Message - From: Farren Minns [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Friday, January 20, 2006 7:25 AM Subject: [ADSM-L] Rebuilding a TSM Server ? Hi all *** TSM 5.1.6.2 on Solaris 2.7, moving to TSM 5.2.?.? on Solaris 2.9 *** OK, I'm in the process of building a new replacement TSM server (Solaris). When it's ready I will hopefully be able to turn the old machine off and bring the new one up again with the same host name/tcp address and away we'll all go. I have already got the server ready, patched, IBMTape and lmcpd drivers installed etc, so I'm about ready to move on to the TSM side of things. The procedures that I assume I now need to go through are as follows. Anything with a question mark is something I'm not sure about. 1) Install TSM - Done 2) Register necessary licenses 3) Define Tape/Library devices and paths for manual library ready for restore. 4) Create device configuration file for above and add entry into the dsmserv.opt file. 5) Copy volume history file from original server ? 6) Format Backuppool volume/s 7) Format Database volume/s 8) Format Log volume/s Question re above: If for example my present database is 10GB and made up of 5*2GB volumes, do I need to create the new volumes like for like or could I just create one 10GB volume. i.e. is it only important to make sure the necessary space is required and not the exact same volume layout. This question goes for backuppool, log and database volumes. 9) Restore database with the DSMSERV RESTORE DB command and utilizing the device config file pointed to by the dsmserv.opt file. 10) Alter the device configuration to change the library definition from 'manual' to '349X' to take our 3494 library into account. - also add the 'enable3590library yes' entry to the dsmserv.opt file. Does the above plan of action look about right or am I making it too simple. Just wondering if I'm missing something important. 11) At this point I will be ready to upgrade the TSM Server install from 5.1.6.2 Questions re above: a) Is it necessary to run an auditdb prior to doing this? b) What are peoples thoughts on the most stable 5.2
Re: Rebuilding a TSM Server ?
Thank you all so much for your advice with this, it's very much appreciated and i'll let you know if it goes well (or if i'm crying in the comms room) :-) Farren |-+---| | len boyle | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| ST.EDU| | | cc| | 20/01/2006 13:58 | | | |Subject| | Please respond to | Re: [ADSM-L] | | ADSM: Dist Stor| Rebuilding a | | Manager| TSM Server ? | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| Hello Farren It depends on if you have cache mode turned on. You might want to look at the move command to do a final clear of the disk storage pools. It has been a long time, so I am not sure if you have to anything funny with the storage pools like mark them destroyed and then do a trival restore etc. I am at home so I do not have my references. But do check out the dr notes in the ibm redbook for this topic on dr's as that what you are doing here. Let us know how it works out. len - Original Message - From: Farren Minns [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Friday, January 20, 2006 8:42 AM Subject: Re: [ADSM-L] Rebuilding a TSM Server ? Thanks Len As far as moving the data off the backuppool prior to the restore of the db etc, does that just mean doing a full migration to take? I assume it does but am happy to ask again just to make sure :-) Farren |-+---| | len boyle | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU | ST.EDU | | | cc| | 20/01/2006 13:34 | | | | Subject| | Please respond to | Re: [ADSM-L] | | ADSM: Dist Stor | Rebuilding a | | Manager | TSM Server ? | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| Good Morning Farren I am sure that you will get a number of good answers, but here are a few points. I am sure I will be corrected for any faults in my logic. It been a little while since I have had to move the tsm server to a new box and there may be newer better thoughts. When you create the space on the new server, you only have to create the same or greater for the log and db volumes. You can use a new layout based on your best thoughts for performance. For the storage pools you might want to move all data off the disk storage pool volumes before the move. Then you will not have do a restore of the storage pools after the tsm server is restored on the new server. Otherwise you will have to restore the disk storage pools after you restore your db and have a running system. But for the restore of the db you do not need your full operating size. For the initial set up of the tape library and drives, you only need to define one tape drive. After you restore the db, your old device configuration will be in effect. Which means
Re: Still huge problems with Mac OSX client 5.2.3.12
Morning all Can someone tell me where I can get a complete list of the trace flags available to the Mac client? Many thanks Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Still huge problems with Mac OSX client 5.2.3.12
Hi Well sadly we are still running TSM Server 5.1.6.2 as I'm still waiting for new server hardware to arrive to do the upgrade. It's been a struggle to get the money for the new kit hence I'm a little behind the times. I don't think a 5.3 client would work on a 5.1 server (though I could be wrong). Farren |-+---| | James R Owen | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 02/12/2005 09:22 |Subject| | | Re: [ADSM-L] Still huge | | Please respond to | problems with Mac OSX | | ADSM: Dist Stor| client 5.2.3.12 | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Farren, Is there some reason that you can't upgrade to the latest Mac TSM client: 5.3.2.? All/most of our OSX backup complaints were fixed with Mac TSM client 5.3.2.0. -- [EMAIL PROTECTED] (203.432.6693) Farren Minns wrote: Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU | ADSM-L@VM.MARIST.EDU | | | cc| | 01/12/2005 16:45 | | | | Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor | problems with Mac OSX | | Manager | client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ## ## The information contained
Re: Still huge problems with Mac OSX client 5.2.3.12
Hi all Many thanks for all the help with this, but it looks like converting the file systems to Unicode is the only way forward. So now I have a 500Gb backup to do, oh dear :-( All the best to everyone Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons Ltd |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Still huge problems with Mac OSX client 5.2.3.12
Hi all Right, I know I have been here before but we are still having some baaad problems with our Mac OSX 5.2.3.12 clients. I'm currently still only running TSM Server 5.1.6.2 on Solaris until the hardware arrives for the upgrade (v soon), but as far as I am concerned, there should be no problem running 5.2 clients on a 5.1 server. In fact, as far as I know the TSM structure is designed to accommodate this. Now, at the moment, the file systems on the two Mac servers are NOT unicode enabled as this will mean full backups for both servers (which will take some time). I would rather get the server upgrade out of the way before doing this if it's even necessary. So, the problems I am seeing are whole groups of directories not being backed up! Since the upgrade to 5.2.3.12 I have been allowing the client to backup via the scheduler demon (which I could never get to work properly before). But I can see that where the client used to check some 300,000 files, it now only check 70,000 approx! I have never seen such problems with any other clients flavours and I really don't know where to start looking. Are there other people out there running Mac clients that are getting complete successful backups and if so is there something I'm doing wrong. Sadly I'm not a Mac admin so there may be something OS based that is wrong. Any help would be much appreciated as people are not very happy (and who can blame them). All the best Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Still huge problems with Mac OSX client 5.2.3.12
Hi all Well, it looks like we were having quite a few problems with version 5.1.5.16 of the Mac OSX client, but since going to 5.2.3.12 we have had even more. So, while I'm waiting to see if IBM can help me, I will probably have to end up going back to the previous version of the client. Now, I know that the older version of the client will be unable to restore data backed up by the later version, but is there anything else I need to be aware of when trying to downgrade. I assume that there will be data left lying around in the database with no-where to go? What happens to this, if anything? Thanks in advance Farren Minns Hi all Right, I know I have been here before but we are still having some baaad problems with our Mac OSX 5.2.3.12 clients. I'm currently still only running TSM Server 5.1.6.2 on Solaris until the hardware arrives for the upgrade (v soon), but as far as I am concerned, there should be no problem running 5.2 clients on a 5.1 server. In fact, as far as I know the TSM structure is designed to accommodate this. Now, at the moment, the file systems on the two Mac servers are NOT unicode enabled as this will mean full backups for both servers (which will take some time). I would rather get the server upgrade out of the way before doing this if it's even necessary. So, the problems I am seeing are whole groups of directories not being backed up! Since the upgrade to 5.2.3.12 I have been allowing the client to backup via the scheduler demon (which I could never get to work properly before). But I can see that where the client used to check some 300,000 files, it now only check 70,000 approx! I have never seen such problems with any other clients flavours and I really don't know where to start looking. Are there other people out there running Mac clients that are getting complete successful backups and if so is there something I'm doing wrong. Sadly I'm not a Mac admin so there may be something OS based that is wrong. Any help would be much appreciated as people are not very happy (and who can blame them). All the best Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Still huge problems with Mac OSX client 5.2.3.12
Many thanks Richard I have opened a PMR with IBM anyway and sent them the requested Error, Trace logs etc. But I will also do as you recommend and perform some of my own diagnostic backups to see if that helps light my way. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU| | | cc| | 01/12/2005 16:45 | | | |Subject| | Please respond to | Re: [ADSM-L] Still huge | | ADSM: Dist Stor| problems with Mac OSX | | Manager| client 5.2.3.12 | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Dec 1, 2005, at 6:47 AM, Farren Minns wrote: ...I have never seen such problems with any other clients flavours and I really don't know where to start looking. ... Farren - I have some familiarity with the Mac client, but was hoping that a regular user of it would have insights and post a solution. Whereas whole directories are seemingly being left out of the backup, by all means check for Excludes or ownership/permissions underlying that. Given the gross nature of the issue, pursuit should be simpler than with an insidious issue. A means of pursuing further is to perform diagnostic backups... Go into Preferences: in Diagnostics, Enable Tracing, select an output file for it, and start with Trace Flags perform general. That will produce minimal output, where it will tell you exactly what options are in effect during the operation and what was excluded. You can escalate to more profuse trace flags as needed. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Mac client and special characters question
Hi all I am seeing strange errors in the log of one of our TSM Mac 5.2.3.12 clients (recently upgraded from 5.1.5.16. I have already asked a question on this and got some pointers. I have pinned the problem down to the backup of special characters but I'm still unsure what the fix for this is (if any). Can someone please point me in the right direction. Many thanks Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Mac client and special characters question
Thanks for that. I have had a look at the filespaces and as far as the TSM server is concerned, they are indeed set to Is Filespace Unicode = NO. So, from what I have read I have to put an entry in the TSM System Preferences on the client that sets autofsrename to yes. I also understand that this will then rename the old fs to something_OLD and then create a new fs. So does this mean that the entire fs will be backed up again? and When it comes to future restores, will I then see both the new unicode fs and also the *_OLD one? And how does this effect restores, will I have to select the files I may want from the *_OLD fs and restore them to a different location (i.e. the new fs)? I have one more question. On this particular client there are a couple of filespaces that no longer exist but that I want kept in backup. Will this process effect those also or just the file spaces being backed up again? Thanks again Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU| ADSM-L@VM.MARIST.EDU | | | cc| | 25/11/2005 13:21 | | | |Subject| | Please respond to | Re: [ADSM-L] Mac | | ADSM: Dist Stor| client and special| | Manager| characters question | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| On Nov 25, 2005, at 6:39 AM, Farren Minns wrote: Hi all I am seeing strange errors in the log of one of our TSM Mac 5.2.3.12 clients (recently upgraded from 5.1.5.16. I have already asked a question on this and got some pointers. I have pinned the problem down to the backup of special characters but I'm still unsure what the fix for this is (if any). Can someone please point me in the right direction. I presume that the errors are: ANS1304W An active backup version could not be found The TSM 5.2 Macintosh client manual says: Beginning with Tivoli Storage Manager version 5.2, the Macintosh client is Unicode enabled. Technote 1171487 may pertain, where a client is using Unicode filenames but the TSM filespace is not Unicode enabled. Alternately, you may have the more traditional case where a given file system object name has at one time been a file, and at another time, a directory, which greatly confuses things. You can perform a Select in the Backups table to verify this. If so, you may be able to perform repeated Selective backups to push the bad stuff out as the retained versions limit is exceeded. Richard Sims ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: exclude directory structure
OK, to all Regarding the move to unicode file spaces. Is this something that people are doing (have done), as a matter of course or just if the need arises. For me this is the first time I have come across the problem of some files not backing up correctly and I'm a little loath to now be faced with backing up our entire client base again. What are your thoughts Farren |-+---| | Richard Sims [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | | | Manager | To| | ADSM-L@VM.MARIST.EDU|[EMAIL PROTECTED]| | |T.EDU | | 25/11/2005 15:36 | cc| | | | | Please respond to |Subject| | ADSM: Dist Stor|Re: [ADSM-L] | | Manager|exclude| | ADSM-L@VM.MARIST.EDU |directory | | |structure | | | | | | | | | | | | | | | | | | | |-+---| I see...you are attempting a compensation for the snapshot requirements issue. I would recommend stepping back and looking at the big picture, afresh: avoid digging a deeper hole in this scenario. In particular, a modern computer which has less than 5 GB of available disk space is ridiculously in need of either housekeeping or disk upgrade, where the latter can be internal, external peripheral, or networked disk space - which is to say that there are many opportunities. The client owner should consider that the running disk may be of considerable age now, and may be worth replacing with a much more capacious disk, which will avoid all the problems involved should the old disk suddenly die - particularly as it sounds like there is not a complete backup now for that disk. Or, the Windows computer may be so old that it is worth wholly replacing. You are, in effect, being mired in a problem which really belongs to the client owner. If you find no cooperation there, consider pursuing conventional Incremental backup, dealing with open files via retries or software subsystem shutdown during the backup, depending upon what's keeping them open. Richard Sims On Nov 25, 2005, at 8:47 AM, Sandra wrote: Dear richard, I m alittle confused. I will create a .bat file which will take incremental backup of 1 drive: dsmc -optfile=dsm.opt incremental -filesonly and the other .bat file would backup D drive: dsmc -optfile=dsm-d.opt incremental -filesonly I m doing this because i have less amount of HDD space 5GB on C and open files snapshot is taking tooo much space and then the system hangs. ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
ANS1304W An active backup version could not be found?
Hi All We recently upgraded an OSX mac client from version 5.1.5.16 to version 5.2.3.12. I have just run an incremental backup and I am see quite a few instances of the following message after trying to expire certain files :- ANS1304W An active backup version could not be found I'm not really sure what this is trying to tell me. Has anyone else had similar? Thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
5.1.6.2 to 5.2 Upgrade - How to
Hi all I have a new server coming in the next couple of weeks and will at last be able to get us moved off TSM 5.1.6.2 and on to 5.2.?.?. As such, my plan of action is going to be as follows. I know the points are basic, but for now I want to make sure the general plan is acceptable before working out the details. Install the new server, OS (Solaris 2.9), patches, tape and library drivers etc Install TSM and get it to the same level as the current live server. Connect the new server to the lib via a fibre switch and do a restore of the db. Do an audit db on the restored database to make sure it's OK. Upgrade the new TSM install to 5.2 ( do I want to go right up to 5.2.6.4 here?) Once this is done, my basic plan is to shut down the live TSM server, and reconfigure the new server to have the same host name, IP address etc. I'm assuming that I can then bring this up and as far as the clients are concerned, backups will be able to carry on like nothing has happened. As I say, I know there are a number of small things to do, but does the general plan look sound? Also, we are backing up pretty much all 5.1 clients at present and as far as I know this is fine (5.1 clients on 5.2 server). It's not likely that I'll be able to get the clients upgraded prior to the server. Am I likely to see any real problems with this? I know it's all a bit vague at the moment, but I'm trying to get it all straight in my head. Many thanks for any advice Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Version of 5.2 server and DB question
Hi all I'm about to be getting a new server and can at last install TSM 5.2 on Solaris. Is it best to go right up to the latest version of that release (5.2.6.4 I believe)? Also, as I can plan things a bit better on this new server I want to size my DB a bit more efficiently. Now, I know this is an old question with many posts but I couldn't seem to get a concrete answer. My DB is only 14GB and 80% used, so I think I'll allocate 30GB to give me loads of space for growth. So, is it best to have 3*10GB volumes, or 30*1GB etc. Basically should I have more smaller ones, and if so how small is too small? Thanks Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
TSM MAC Client Inlude query
Hi all TSM Mac X BA Client 5.1.5.16 I'm having a little problem. I need to include a sub-dir and its contents with another management class so that just those files will be kept for longer. I am using the following line in the TSM System Preferences file. INCLUDE Safe Volume:FM7_Backup:Backup:...:* ORACLE But when I back up any files below that, they aren't getting rebound. What am I doing wrong? Sadly I know nothing about MACs so it may be something silly. Many thanks in advance Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re TDP for Lotus Domino (again)
Hi all I'm still having some problems (re email below), understanding under what conditions the Domino dbs are backed up. Can I assume that I am right on the following:- If the dbs are logged and transaction logs are being created and backed up, only the transaction logs will be backed up during an incremental which is why we would need to do selective backups of the entire dbs each week to cut down on the amount of rolling forward to be done? But, in this case, will the DBIIDs of the logged databases ever change? Thanks Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services Hi Farren, From the Users Guide: Incremental Backup An incremental backup provides a conditional backup function that performs a full online backup of Domino databases under the following conditions: The database is within the Domino data path or symbolically linked to the Domino data path by directory or database links. The database is not excluded from backup by exclude statements within the Tivoli Storage Manager options file. If the database is logged, the DBIID has changed. If the database is not logged, it has been modified since the last backup occurred (data and non-data modification dates are checked). The database is new or newly included in the backup. Thanks, Del ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Re TDP for Lotus Domino (again)
Hi I'm sorry, I'm still slightly confused. The problem is that under incremental backup I am not often seeing the databases backed up. I now know that if the db is compacted that will change the dbiid and thus it will be backed up, but is this enough. My position is this. We do a full backup each weekend, so I'm happy with this. Each day we do an incremental which apparently doesn't back any databases up, but we do then back up the transaction logs. So I'm happy that we can restore from the weekly and then roll forward without too much trouble. So can I be happy that things are working as necessary, or should the database dbiids be changing under other circumstances as well and thus being backed up during the week also? I apologise if I'm just being dumb here :-( Many thanks again Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ. Tel: +44 (0) 1243 770406 Fax: +44 (0) 1243 775878 |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| DU| | | cc| | 03/11/2005 12:48 | | | |Subject| | Please respond to | Re: [ADSM-L] Re | | ADSM: Dist Stor| TDP for Lotus | | Manager| Domino (again)| | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| Hi Farren, The transaction logs are not backed up during a domdsmc incremental command. The transaction logs are backed up with the domdsmc archivelog command. You are correct that many customers do a domdsmc selective command once a week (or more often, depending on the amount of log data generated) so that when a database is recovered, not as many transaction logs need to be replayed against the restored database. DBIIDs can change under different circumstances such as database compaction. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 11/03/2005 06:40:48 AM: Hi all I'm still having some problems (re email below), understanding under what conditions the Domino dbs are backed up. Can I assume that I am right on the following:- If the dbs are logged and transaction logs are being created and backed up, only the transaction logs will be backed up during an incremental which is why we would need to do selective backups of the entire dbs each week to cut down on the amount of rolling forward to be done? But, in this case, will the DBIIDs of the logged databases ever change? Thanks Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services Hi Farren, From the Users Guide: Incremental Backup An incremental backup provides a conditional backup function that performs a full online backup of Domino databases under the following conditions: The database is within the Domino data path or symbolically linked to the Domino data path by directory or database links. The database is not excluded from backup by exclude statements within the Tivoli Storage Manager options file. If the database is logged, the DBIID has changed. If the database is not logged, it has been modified since the last backup occurred (data and non-data modification dates are checked). The database is new or newly included in the backup. Thanks, Del ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise
Re: Re TDP for Lotus Domino (again)
That's wonderful ! Many thanks for all your help with this. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | [EMAIL PROTECTED]| | ADSM-L@VM.MARIST.EDU| DU| | | cc| | 03/11/2005 14:14 | | | |Subject| | Please respond to | Re: [ADSM-L] Re | | ADSM: Dist Stor| TDP for Lotus | | Manager| Domino (again)| | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | | | | |-+---| Farren, You should be happy. Things are working exactly as they should. That is one of the large benefits that you get by using transaction logging. Since every change to a logged database is captured in the transaction log, you are backing up only the necessary changes when you back up the transaction logs. The DBIIDs shouldn't normally change during the week, unless you run maintenance activity (like compaction)... which most customers perform on the weekends just before their full (selective) backups. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 11/03/2005 08:56:34 AM: Hi I'm sorry, I'm still slightly confused. The problem is that under incremental backup I am not often seeing the databases backed up. I now know that if the db is compacted that will change the dbiid and thus it will be backed up, but is this enough. My position is this. We do a full backup each weekend, so I'm happy with this. Each day we do an incremental which apparently doesn't back any databases up, but we do then back up the transaction logs. So I'm happy that we can restore from the weekly and then roll forward without too much trouble. So can I be happy that things are working as necessary, or should the database dbiids be changing under other circumstances as well and thus being backed up during the week also? I apologise if I'm just being dumb here :-( Many thanks again Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services John Wiley Sons, Ltd. ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Another TDP for Domino Question
Morning all I'm trying to understand under what conditions a Lotus Domino database gets backed up during an incremental. In our case we do a full backup of all the dbs over the weekend and then incremental all week including the transaction logs. So, if we have full backups followed by transaction logs, under what circumstances are the dbs backed up incrementally. Thanks Farren ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Problem after time change
Hi All I'm sure this has been covered before and I've been looking on adsm.org but haven't found a decent answer yet. Basically, I'm running TSM Server 5.1.6.2 on Solaris. The problem client node in question is a Windows Server 2003 Standard Edition NAS with TSM client 5.2.0.6 running on it. After the clocks went back at the weekend it has started backing up files that as far as I can tell have not changed (although I'm not a Windows admin so I may be missing something). It doesn't appear to be doing a backup of absolutely everything (it managed to check 500,000 files before backing any up), but sadly the dir it is currently backing up is full of ghost images and is going to take a while. Has anyone else had any similar problems in the past? Many thanks Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Problem after time change
item in the pop-up menu. (Alternatively, you can double-click on the clock display in the task bar.) Either of these actions will bring up the Date/Time Properties dialog. Click on the Time Zone tab and you should see the Automatically adjust clock for daylight saving changes checkbox. If the box is checked (the default installation setting), then your system is configured to automatically adjust for DST. Users in regions that do not observe DST (such as Arizona) will be unaffected by this problem, provided that the system's time zone settings are similarly configured to not observe DST. WHAT IBM/TIVOLI IS DOING ABOUT THIS Here are the actions that we are taking or have taken to date: 1) We have opened a severity 1 APAR, IC28544, to address this problem. 2) We have designed and built fixtests for the 3.7.2 and 4.1.1 Windows clients. The fixtest version numbers are 3.7.2.17 and 4.1.1.17. The fixtests should be available in a little while. They will be posted to the anonymous FTP server ftp.software.ibm.com in the following locations: Version 4.1.1.17: Directory /storage/tivoli-storage-management/patches/client/v4r1/Windows/v411/sing le Package name start with: IP22088_17 V3.7 PTF 2: Directory /storage/tivoli-storage-management/patches/client/v3r7/Windows/v372/i386 /single Package name starts with: IP21933_17 A follow-up note will be posted when the fixtests are actually available for download. 3) Even with the availability of a fixtest, most customers will be unable to roll it out in time for the time change. We have documented circumventions for this problem (see below), as the DST to STD switch is this weekend. 4) We are working on notifying all of our customers in the most expedient manner possible. 5) We are continuing our escape and root-cause analyses in order to prevent this kind of problem from happening again. CIRCUMVENTIONS Here are the known circumventions available thus far: 1) Lock all client nodes to prevent access to the TSM server. After the fixtest has been applied to each system, unlock that system's node(s). Since many nodes may be affected, a batch script may be helpful in facilitating the locking and unlocking of the nodes. 2) If the fixtest can not yet be applied, consider using the -INCRBYDATE option to back up the clients. The easiest way to do this is to add it to existing schedules' options setting via the UPDATE SCHEDULE administrator command. Example: UPDATE SCHEDULE STANDARD DAILY OPTIONS=-INCRBYDATE or if your schedule already contains options, such as -SUBDIR=YES: UPDATE SCHEDULE STANDARD DAILY OPTIONS=-INCRBYDATE -SUBDIR=YES Please refer to the Tivoli Storage Manager Administrator's Reference for further information on the UPDATE SCHEDULE command. Please refer to the Tivoli Storage Manager for Windows Using the Windows Backup-Archive Client for further information on the -INCRBYDATE option. 3) Same as #1 above, except instead of locking each node, disable all client sessions on the TSM server. This is easier than having to lock and unlock each node, but would require that all affected systems have the fixtest applied before re-enabling the server for client sessions. 4) Shut down your TSM server(s) until all affected systems can have the fixtest applied. 5) If the additional network and TSM server overhead is not a concern, you can just let the backups run to completion. However, because this can cause unchanged files to be backed up, the oldest version of each affected file will be expired. In order to avoid premature expiration, you may wish to add '1' to each backup copygroup's VEREXISTS setting. For example, if VEREXISTS is currently set to '15', you may wish to change it to '16'. Use the UPDATE COPYGROUP and ACTIVATE POLICYSET commands to implement this change. Example: UPDATE COPYGROUP STANDARD STANDARD STANDARD STANDARD VEREXISTS=16 ACTIVATE POLICYSET STANDARD STANDARD Please refer to the Tivoli Storage Manager Administrator's Reference for further information on the UPDATE COPYGROUP and ACTIVATE POLICYSET commands. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Farren Minns Sent: 31 October 2005 14:40 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Problem after time change Hi All I'm sure this has been covered before and I've been looking on adsm.org but haven't found a decent answer yet. Basically, I'm running TSM Server 5.1.6.2 on Solaris. The problem client node in question is a Windows Server 2003 Standard Edition NAS with TSM client 5.2.0.6 running on it. After the clocks went back at the weekend it has started backing up files that as far as I can tell have not changed (although I'm not a Windows admin so I may be missing something). It doesn't appear to be doing a backup
Restore question
Hi all Is there a way to ascertain what tape volumes will be required for a file/dir restore before actually running it? Thanks Farren John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
TDP for Lotus Domino 5.1.5.1 (license question)
Hi Thanks for the input, and sorry for the confusion. The script included was indeed for the incremental backups and a different one is used for the selective. One thing that has occurred to me is the licensing. I have registered a license on the server and can see that it is being used, but does anything in particular need to be done from the client point of view. As far as I know, the user will have downloaded the Domino client from ftp://index.storsys.ibm.com/. Will this be ok as an initial install or would that need to be used only as an install over an exisiting 'paid in full' version. I am only asking because looking at the readme for the client it says that is comes in various flavours (Paid In Full, PTF, Try and Buy etc). Thanks again Farren Minns John Wiley Sons Ltd IT - Hosting Services |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 18/10/2005 17:59 |Subject| | | Re: [ADSM-L] TDP for| | Please respond to | Lotus Domino 5.1.5.1| | ADSM: Dist Stor| problem | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Hi Farren, A few observations: 1. The script below is doing an incremental backup... not a selective. With incremental backups, the .NSF file will not be backed up unless the DBIID has changed. The archivelog will capture the changes. The User's Guide discusses this in more detail. 2. I recommend that you upgrade to the latest Data Protection for Domino. Site: ftp.software.ibm.com Dir: /storage/tivoli-storage-management/patches/tivoli-data-protection/domino/win32/v5301/ It includes fixes for some GUI crashes. 3. domdsmc does allow wildcards, so you could do something like: domdsmc incremental mail2\* /subdir=no If you don't want some databases backed up, you can EXCLUDE them. The User's Guide discusses this in more detail. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/18/2005 11:19:02 AM: Hi all I have just had a client on the phone with a TDP for Domino problem. I am not really familiar with this or the Windows 2000 server it's running on and may well not provide enough information from the off so please let me know what else is required. Running TSM Server 5.1.6.2 on Solaris. The problem is with a 5.1.5.1 TDP Domino Client running on Windows 2000 SP4 (5:00:2195). Basically, if he does a selective backup (using the script below) it works fine, but incrementals seem to run OK but don't actually back anything up (except the transaction logs I think). Any ideas what the problem might be ? Also, he was originally trying to backup the mail dir but the GUI would just keep dropping out when he tried to do a manual backup. As such he has attempted to create a new dir called mail2 with database links pointing to the necessary databases. When he does this and used the GUI to look in mail2, it works fine. I'm sorry if I haven't provided the correct info but I'm not a Windows admin and have very limited knowledge in this realm. Many thanks in advance Farren Minns John Wiley Sons Ltd The batch file that he runs looks as follows. He only needs to backup the specified directories. cd domino domdsmc incremental mail2\abassett.nsf /subdir=no domdsmc incremental mail2\bioessays.nsf /subdir=no domdsmc incremental mail2\abradfie.nsf /subdir=no domdsmc incremental mail2\achase.nsf /subdir=no domdsmc incremental mail2\scole.nsf /subdir=no domdsmc incremental mail2\ggranger.nsf /subdir=no domdsmc incremental mail2\shadfiel.nsf /subdir=no domdsmc incremental mail2\shamer.nsf /subdir=no domdsmc incremental mail2\jlangrid.nsf /subdir=no domdsmc incremental mail2\spiper.nsf /subdir=no domdsmc incremental mail2\drobinso.nsf /subdir=no domdsmc incremental mail2\sswann.nsf /subdir=no domdsmc incremental mail2\ptrevorr.nsf /subdir=no domdsmc
Re: TDP for Lotus Domino 5.1.5.1 problem
Hi again Providing I have installed the base 5.1.5.0 TDP for Domino with the Paid license, can I just then use the 5.3.0.1 patch download to upgrade or do I need to source a different version of the media? Also, in the readme for 5.3.0.1 is says that TSM API 5.3.0 or later is also required. I'm assuming that this is part of the TDP for Domino install? Is this the case? Sorry to keep coming back with more questions but as I don't have direct access to the domino server in question, I'm relying on getting all my info straight and then getting it right first time. It doesn't help that I don't know exactly what order things on this server were done in. I know it's at 5.1.5.1 and I can see that there is both a PAID and dummy license present. But, I can also see this message at the top of the activity log:- 09/27/2005 14:24:42 ACD0053E License file (C:\PROGRA~1\Tivoli\TSM\domino\domclient.lic) could not be opened. 09/27/2005 14:25:18 ACD0057E The checksum in the license file (C:\PROGRA~1\Tivoli\TSM\domino\domclient.lic) does not match the license string text. ... so I know that at some point 5.1.5.1 was installed directly without the prior 5.1.5.0 install. Anyway, thanks for all your help so far, it's very much appreciated. All the best Farren Minns Solaris System Admin / Oracle DBA IT - Hosting Services |-+---| | Del Hoobler | | | [EMAIL PROTECTED] | | | Sent by: ADSM: Dist Stor | To| | Manager | ADSM-L@VM.MARIST.EDU| | ADSM-L@VM.MARIST.EDU| cc| | | | | 18/10/2005 17:59 |Subject| | | Re: [ADSM-L] TDP for| | Please respond to | Lotus Domino 5.1.5.1| | ADSM: Dist Stor| problem | | Manager| | | ADSM-L@VM.MARIST.EDU | | | | | | | | | | | | | | |-+---| Hi Farren, A few observations: 1. The script below is doing an incremental backup... not a selective. With incremental backups, the .NSF file will not be backed up unless the DBIID has changed. The archivelog will capture the changes. The User's Guide discusses this in more detail. 2. I recommend that you upgrade to the latest Data Protection for Domino. Site: ftp.software.ibm.com Dir: /storage/tivoli-storage-management/patches/tivoli-data-protection/domino/win32/v5301/ It includes fixes for some GUI crashes. 3. domdsmc does allow wildcards, so you could do something like: domdsmc incremental mail2\* /subdir=no If you don't want some databases backed up, you can EXCLUDE them. The User's Guide discusses this in more detail. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 10/18/2005 11:19:02 AM: Hi all I have just had a client on the phone with a TDP for Domino problem. I am not really familiar with this or the Windows 2000 server it's running on and may well not provide enough information from the off so please let me know what else is required. Running TSM Server 5.1.6.2 on Solaris. The problem is with a 5.1.5.1 TDP Domino Client running on Windows 2000 SP4 (5:00:2195). Basically, if he does a selective backup (using the script below) it works fine, but incrementals seem to run OK but don't actually back anything up (except the transaction logs I think). Any ideas what the problem might be ? Also, he was originally trying to backup the mail dir but the GUI would just keep dropping out when he tried to do a manual backup. As such he has attempted to create a new dir called mail2 with database links pointing to the necessary databases. When he does this and used the GUI to look in mail2, it works fine. I'm sorry if I haven't provided the correct info but I'm not a Windows admin and have very limited knowledge in this realm. Many thanks in advance Farren Minns John Wiley Sons Ltd The batch file that he runs looks as follows. He only needs to backup the specified directories. cd domino domdsmc incremental mail2\abassett.nsf /subdir=no domdsmc incremental mail2\bioessays.nsf /subdir=no domdsmc incremental mail2\abradfie.nsf
TDP for Lotus Domino 5.1.5.1 problem
Hi all I have just had a client on the phone with a TDP for Domino problem. I am not really familiar with this or the Windows 2000 server it's running on and may well not provide enough information from the off so please let me know what else is required. Running TSM Server 5.1.6.2 on Solaris. The problem is with a 5.1.5.1 TDP Domino Client running on Windows 2000 SP4 (5:00:2195). Basically, if he does a selective backup (using the script below) it works fine, but incrementals seem to run OK but don't actually back anything up (except the transaction logs I think). Any ideas what the problem might be ? Also, he was originally trying to backup the mail dir but the GUI would just keep dropping out when he tried to do a manual backup. As such he has attempted to create a new dir called mail2 with database links pointing to the necessary databases. When he does this and used the GUI to look in mail2, it works fine. I'm sorry if I haven't provided the correct info but I'm not a Windows admin and have very limited knowledge in this realm. Many thanks in advance Farren Minns John Wiley Sons Ltd The batch file that he runs looks as follows. He only needs to backup the specified directories. cd domino domdsmc incremental mail2\abassett.nsf /subdir=no domdsmc incremental mail2\bioessays.nsf /subdir=no domdsmc incremental mail2\abradfie.nsf /subdir=no domdsmc incremental mail2\achase.nsf /subdir=no domdsmc incremental mail2\scole.nsf /subdir=no domdsmc incremental mail2\ggranger.nsf /subdir=no domdsmc incremental mail2\shadfiel.nsf /subdir=no domdsmc incremental mail2\shamer.nsf /subdir=no domdsmc incremental mail2\jlangrid.nsf /subdir=no domdsmc incremental mail2\spiper.nsf /subdir=no domdsmc incremental mail2\drobinso.nsf /subdir=no domdsmc incremental mail2\sswann.nsf /subdir=no domdsmc incremental mail2\ptrevorr.nsf /subdir=no domdsmc incremental mail2\elsuk.nsf /subdir=no domdsmc incremental mail2\awilkins.nsf /subdir=no domdsmc incremental mail2\jsibley.nsf /subdir=no domdsmc incremental mail2\mcawaiting.nsf /subdir=no domdsmc incremental mail2\mcexport.nsf /subdir=no domdsmc incremental mail2\sybex.nsf /subdir=no domdsmc incremental mail2\ou.nsf /subdir=no domdsmc incremental mail2\authorcorrs.nsf /subdir=no domdsmc incremental mail2\rlong.nsf /subdir=no domdsmc incremental mail2\stmcover.nsf /subdir=no domdsmc incremental mail2\ptcover.nsf /subdir=no domdsmc incremental mail2\bjs.nsf /subdir=no domdsmc incremental mail2\eic2.nsf /subdir=no domdsmc incremental mail2\rward.nsf /subdir=no domdsmc incremental mail2\stcopyuk.nsf /subdir=no domdsmc incremental mail2\etep.nsf /subdir=no domdsmc incremental mail2\hypproofs.nsf /subdir=no domdsmc incremental mail2\ggpb.nsf /subdir=no domdsmc incremental mail2\prequest.nsf /subdir=no domdsmc incremental mail2\indrevew.nsf /subdir=no domdsmc incremental mail2\aisaac.nsf /subdir=no domdsmc incremental mail2\gboonen.nsf /subdir=no domdsmc incremental mail2\aucorrslw.nsf /subdir=no domdsmc incremental mail2\outsourcers.nsf /subdir=no domdsmc incremental mail2\pod.nsf /subdir=no domdsmc incremental mail2\bookreprints.nsf /subdir=no domdsmc incremental mail2\manufacturing.nsf /subdir=no domdsmc incremental mail2\ukdcgood.nsf /subdir=no domdsmc incremental mail2\aucorrsthoms.nsf /subdir=no domdsmc archivelog rem exit ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
Re: Basic newbie questions
Hi all I have another quick question for you re moving TSM from one OS to another. I have already had some great replies on this subject (thank you), but my new question is this. I understand that you can't simply move database volumes from one OS to another, but can you use something like dumpdb or unloaddb and then load/import the database information to another TSM server running on a different OS? Many thanks in advance Farren Minns John Wiley Sons Ltd ## The information contained in this e-mail and any subsequent correspondence is private and confidential and intended solely for the named recipient(s). If you are not a named recipient, you must not copy, distribute, or disseminate the information, open any attachment, or take any action in reliance on it. If you have received the e-mail in error, please notify the sender and delete the e-mail. Any views or opinions expressed in this e-mail are those of the individual sender, unless otherwise stated. Although this e-mail has been scanned for viruses you should rely on your own virus check, as the sender accepts no liability for any damage arising out of any bug or virus infection. ##
