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. ##
ISC/AC on Linux x86-64
Hi all, I have a customer who is thinking about migrating their Windows TSM Server to a Linux x86-64 install. I have already checked the availability of the TSM server for this platform, but couldn't verify if the ISC/AC runs on it. I saw the ISC/AC for Linux x86, but saw nothing about 64bit. Customer said that 64bit is the driving force of this migration, so if they must use Linux x86-32, they will rather stay on Windows. Anyone saw something about it? Thanks, Paul
HP itanium and 64-bit support
A server will be installed here with the following specs: HP itanium with 4 processors, running Windows 2003 and SQL Server 2005. I'm currently at SM Server 5.2.0.0 on Windows 2000 machine. Anyone had a problem with BA client 64-bit and/or TDP for SQL client 64-bit ? Thanks Yiannakis Yiannakis Vakis Systems Support Group, I.T.Division Tel. 22-848523, 99-414788, Fax. 22-337770
Multiple schedulers for same node name
Dear All, On windows 2000 client running TSM 5.3 client, how can i setup 2 schedulers with same node name. Objective is to initiate separate backups for C drive and D drive using same node name. Also when i give -optfile=filename.opt in the options in the scheduled task, it says invalid option when the backup starts. Regards, Sandra _ Sent via SUPERwebmail - Supernet web-based email service http://www.super.net.pk/mail
Re: Mac client and special characters question
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
Re: exclude directory structure
On Nov 24, 2005, at 11:55 PM, Sandra wrote: ... How can I prevent directory structure to be backed up while at the same time i want to do incremental backup using schedule ! There is a FILESOnly client option; but thoroughly consider the ramifications of its use before doing so. I would be loathe to back up a file system and include only files, particularly in Windows. Richard Sims
Re: exclude directory structure
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. Regards, Sandra [EMAIL PROTECTED] wrote : > On Nov 24, 2005, at 11:55 PM, Sandra wrote: > > > ... > > How can I prevent directory structure to be backed up while at the > > same time i want to do incremental backup using schedule ! > > There is a FILESOnly client option; but thoroughly consider the > ramifications of its use before doing so. I would be loathe to back > up a file system and include only files, particularly in Windows. > > Richard Sims > > _ Sent via SUPERwebmail - Supernet web-based email service http://www.super.net.pk/mail
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 | | | cc| | 25/11/2005 13:21 | | | |Subject| | Please respond to | Re: [ADSM-L] Mac | | "ADSM: Dist Stor| client and special| | Manager"| characters question | | | | | | | | | | | | | | | | | | | |-+---| 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: Mac client and special characters question
On Nov 25, 2005, at 9:40 AM, Farren Minns wrote: 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. Refer to the Technote or the client manual: you can opt to either have TSM automatically perform the filespace rename, or do it manually. I would manually rename the filespace on the server, as I would not want things happening without my control, particularly as it affects later access to the data. So does this mean that the entire fs will be backed up again? Yes - it's starting fresh. 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)? Yes, just like restoring across file systems in the same client. The client owner has to remember about the old filespace. 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? Affected is just the one filespace that receives this special attention. File systems which no longer exist on the client do not in any way participate in backup processing. Orphan filespaces - the bane of TSM server administrators - need tracking, periodic communication with client administrators (email), and manual deletion at some time in the future. The orphans continue to participate in time-based objects expiration, but not versions-based expiration, as there is no new incoming data. Richard Sims
Re: exclude 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.
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| | |[EMAIL PROTECTED]| | |T.EDU | | 25/11/2005 15:36 | cc| | | | | Please respond to |Subject| | "ADSM: Dist Stor|Re: [ADSM-L] | | Manager"|exclude| | |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. ##
Re: Migrate TSM Server 4.2.4 on AIX 4.3.3 to 5.3 on Linux Howto (retry)
==> On Fri, 25 Nov 2005 16:57:56 +0100, Christoph Martin <[EMAIL PROTECTED]> said: > help export server says that you can decide wether you want to export the > node information (Client node definitions) and the node file data too. The > question is, if I have to export the node file data too, or if I can reuse > the file data tapes in the new server. You have to export and import all the data, when moving from one platform to another. If you export only the node _definitions_, then you can have one sudden changeover. The passwords for the nods will be copied over, and everything in your TSM universe will do an "initial incremental" at once. I think this is probably not a good plan. :) > The default option is FILEData=None > It is no option for us to export the file data. We have about 3 hundred AIT > tapes with file data. If you want to retain the backup history now present on your "old" TSM server, you will need to export and import the nodes. You can do this in smaller chunks, if you care to, a node at a time, for instance. There are many ways you might accomplish the transfer; http://open-systems.ufl.edu/services/NSAM/whitepapers/50ways.html is my attempt to catalog some of them. Moving from platform to platform is a Big Deal; don't expect it to be quick or trivial, on any axis. I'd say "Stay on AIX"; 510s aren't that expensive. :) - Allen S. Rout
Re: exclude directory structure
In fact what matters most here is that i have been backing up another server which has more than 20 GB of available space on C drive and upon snapshotcache of D on C, causes the system to hang until hard booted. Q1- Why this snapshot is of so big size? Q2- Keeping the nodename same, how can i schedule incremental backup which would use 2nd option file? For ex. dsm.opt would run the backup of C drive with its specific include/excludes and dsm-d.opt would run backup of D with its specific include/exclude. Kind REgards, Sadat Farren Minns wrote: > 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| > | |[EMAIL PROTECTED]| > | |T.EDU | > | 25/11/2005 15:36 | cc| > | | | > | Please respond to |Subject| > | "ADSM: Dist Stor|Re: [ADSM-L] | > | Manager"|exclude| > | |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. > ##
SQL select for file size
I know that this question has been addressed before, but I just want to check that the situation remains the same with the current releases, or if anybody has come up with a cheeky workaround/better solution. I am looking for a relatively efficient way of finding out how much data in size is stored by TSM for certain files or file types (ie. .mp3 .wav .avi ) I can get a list of the files with select ll_name,hl_name from backups where node_name='XXX' and filespace_id=x and ll_name like'%.MP3%' If I know what volumes the node/filespace resides on, I can get the file size with select node_name,filespace_name,file_name,file_size from contents where volume_name='XXX' Is the file size accurate or is it the size of the aggregate that the file is contained within ? (They all seem a little too rounded for my liking) Also, this is not particularly easy in a non-colocated environment. So, is listing the volumes that the node/filespace is stored on and then selecting from the contents of this list of volumes the only way. And, even if this is scripted, is it accurate or is it just the size of the aggregates. Knowing that the GUI will list the filesize but it doesn't seem readily available from SQL queries is truly a Friday afternoon annoyance. Leigh
Re: 3592J1A tape drive
On Nov 25, 2005, at 1:03 AM, Nicolas Savva wrote: Hi to all I am using a 3494 Tape Library within two 3590 tape drive and now i am trying to add another 2 3592J1A tape drives. What private and scratch category do i have to specify in my tape library? The choice is arbitrary, as long as it does not impinge upon the numbers used by the library instance which supports your earlier, 3590 drives and avoids reserved numbers. In addition when i connect the two new 3592 tape drive on the FC Switch and define the tape drives on the TSM, while i am executing the command "Q SAN" i don't receive any answer. Drives connected to your host system via FibreChannel do not unto themselves constitute a SAN. Richard Sims
Re: SQL select for file size
I'm not aware of any change in TSM architecture which allows querying actual client file sizes as stored in TSM server storage, from the server. The actual sizes can be obtained via 'dsmc Query Backup' client queries (which a server administrator may be able to perform via Virtualnodename, if the client password is known, and a like client platform is available). Another, ungainly, approach is to scan the client backup logs for sizes. File size is one of the file system attributes which is accessible to the TSM client because it is programmed to understand the nuances of the various file systems it handles. To appreciate the difficulty of having the server understand client file system particulars, consider the problems of a non-Unicode server trying to understand and report even the file system name of a Unicode client. Richard Sims
Re: ISC/AC on Linux x86-64
If you are using a x86-64 linux, means that you have a new PIV, Xeon or an AMD 64. All this processors, as the linux, can handle x86-32 instructions. So, you can install 32 bits ISC. I'm using here, no problems. Braulio Junior IT Manager [EMAIL PROTECTED] Linux User #208017 - Get Counted at http://counter.li.org/ - The rain it raineth on the just And also on the unjust fella, But chiefly on the just, because The unjust steals the just's umbrella. - Paul van Dongen wrote: Hi all, I have a customer who is thinking about migrating their Windows TSM Server to a Linux x86-64 install. I have already checked the availability of the TSM server for this platform, but couldn't verify if the ISC/AC runs on it. I saw the ISC/AC for Linux x86, but saw nothing about 64bit. Customer said that 64bit is the driving force of this migration, so if they must use Linux x86-32, they will rather stay on Windows. Anyone saw something about it? Thanks, Paul
