Re: Linux GFS File system backup using SAN Agent
Kelly, We've got a few GPFS clusters (Suse Linux) where a LAN-free backup is taken with the storage agent. A virtualnodename is used for the backup of the GPFS file systems so that it doesn't matter on which node the backup is started. The backups (and restores if required) are load-balanced manually across the GPFS nodes. It is ashame that TSM does not truly understand the concept of a GPFS file system. Regards, Kurt -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] Namens Kelly Lipp Verzonden: maandag 12 januari 2009 21:29 Aan: ADSM-L@VM.MARIST.EDU Onderwerp: [ADSM-L] Linux GFS File system backup using SAN Agent Folks, Anybody tried this? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com *** Disclaimer *** Vlaamse Radio- en Televisieomroep Auguste Reyerslaan 52, 1043 Brussel nv van publiek recht BTW BE 0244.142.664 RPR Brussel http://www.vrt.be/disclaimer
TSM 6 announcement date?
On 15 jan 2009, at 05:30, Mark Scott wrote: Afternoon all morning ;-) Does anyone know when TSM 6 is to be released? I heard that some folks at IBM have ideas about an announcement date. But you know with IBM, they'll only announce when they're 100% sure that they'll make the date (usually because the date is that same day). Regards Bunnings Legal Disclaimer: snip nonsense about confidentiality, this is a public mailing list -- Remco Post r.p...@plcs.nl +31 6 24821 622
Re: How to delete offsite copy version only of data ?
Thanks a lot for your help Wanda !
I'll work it around this way.
Cheers.
Norman
Wanda Prather wprat...@jasi.com
Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
13/01/2009 22:38
Please respond to
ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: [ADSM-L] How to delete offsite copy version only of data ?
So I assume you have multiple primary pools, including that dead Netware
pool, that back up into one copy pool? And you want to delete just SOME
of
the nodes out of the Copy Pool?
Only good way I can think of, is to run MOVE NODEDATA on those Netware
servers.
Start with empty scratch volumes; run MOVE NODEDATA to get the data from
those boxes onto new tapes.
Run: select distinct node_name from volumeusage where
volume_name='000XXX'
to verify FER SURE that there is no other data on the volume
Then:
delete volume 000XXX discarddata=yes
That will purge the data from THOSE volumes out of the copy pool. And if
you never run backup stgpool on the Netware copy pool again, you should be
OK.
On Tue, Jan 13, 2009 at 9:09 AM, Norman Bloch
norman_bl...@readersdigest.tm.fr wrote:
Hello everyone,
TSM server 5.4.3 on Windows 2003 server.
I have decommissioned all client Netware servers ; since their data were
on a specific storage pool, only for netware files, I was able to move
the
related tapes out of the library ('move media ...' commands), because
I'm
running out of available storage space.
I'm happy keeping that set of tapes in a safe, just in case I need to
restore some data and I'd like to remove all references to those netware
client nodes that are on the copy pool.
The main reason is I'm expecting to get into trouble when space
reclamation will run on the copy pool, with volumes turned as
unavailable
and so on.
Of course, I could just delete the copy pool and re-create it from
scratch
by re-backing up all primary pools but it will take maybe a week or two
and I'd like to avoid it.
Any idea ?
Thanks in advance for your help.
Norman
Re: Open File Support -Win2k3 32bit vs 64bit
Jason, Before you go further down the OFS rabbit hole: On Windows, it is rare to use OFS for backups of MS apps like SQL. Those files are in use by MS SQL. Backing them up via OFS just gives you a copy of a possibly unstable/inconsistent file that may not be usable on restore. When you see those skipped files on the daily report, your response should be: 1) Find out what those files are 2) If they belong to a DB app, make sure the DB is being backed up through an application-appropriate method. For SQL, you can a) use the SQL manager to dump the files into the \backups directory on the box. Those are flat files that are never locked, and TSM can back them up just fine. b) If the DB's are too large to dump to flat files, implement the TSM for SQL agent. 3) Once the DB files are backed up elsewhere appropriately, put an EXCLUDE statement in the dsm.opt file (or a client option set on the server) so that you don't get the skipped files msgs from the backup/archive client in your daily report anymore. W On Wed, Jan 14, 2009 at 6:00 PM, Jason Clarke j...@gwsc.vic.edu.au wrote: Hi list, First post, new admin, thrown in the deep end :-) 5.4 server, 5.4 clients. New installs everywhere. Win2k3 64bit server, mixture of Win2k3,2k,XP,Linux clients. Going through the nightly Operational Report, I'm noticing that various files are not backed up due to being in use. They're all 64bit machines. When I did the client installs I made sure that Open File Support was installed. However, the 64bit installer appears to not have it. Funnily enough, the 64bit machines are the more important servers. SQL/FSMO Roles etc. Where do I look for more info regarding Open File support for 2k3 64bit, either enabling it, using it or installing it? Regards, Jason Clarke -- Network Manager Glen Waverley S.C. p 03 8805 6750 m 0418 145 318 e j...@gwsc.vic.edu.au Please consider the environment before printing this email.
How do I request to be removed from the list?
The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
2 Windows 2003 clients with huge # of files consistently failing
I have two separate Windows 2003 boxes both running running v5.5.1.10 client that are both failing their incrementals every night. Both of these boxes have hundreds of thousand of files all spread into multiple directories. In fact, each day, a new directory is created and then multiple subdirectories are created under it and thousand of files in each of those subdirectories. The reason I say this is because I don't think it is a candidate for multiple virtual nodes because of the new directories that are created every day. I do have journaling turned on although it doesn't seem to help with the large number of files either as when I run an incremental manually,it takes forever and never seems to finish. I thought about doing image backups of the drive where the thousands of files live but when I tried it, it backed up about 14g and then just hung and never continued. I had to cancel it after waiting for an hour or so. What is my best strategy for dealing with these two boxes that are generating thousands of new files in new directories every day? The huge number of objects in the TSM DB are starting to cause quite a few problems with daily processing also as expiration is running longer and longer since I think it is choking on the number of objects. And to make it even weirder, they both fail incrementals at night and the only error I can find is: ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) I'm starting to think that TSM is just not the backup solution for either of these boxes.
Re: 2 Windows 2003 clients with huge # of files consistently failing
On 15 jan 2009, at 15:26, John C Dury wrote: I have two separate Windows 2003 boxes both running running v5.5.1.10 client that are both failing their incrementals every night. Both of these boxes have hundreds of thousand of files all spread into multiple directories. In fact, each day, a new directory is created and then multiple subdirectories are created under it and thousand of files in each of those subdirectories. The reason I say this is because I don't think it is a candidate for multiple virtual nodes because of the new directories that are created every day. I do have journaling turned on although it doesn't seem to help with the large number of files either as when I run an incremental manually,it takes forever and never seems to finish. are you sure that the journal is running and has enough space? In these cases, having the journals on a separate filesystem might be a very good idea. I have the feeling that there is not enough space for the TSM journal database... I thought about doing image backups of the drive where the thousands of files live but when I tried it, it backed up about 14g and then just hung and never continued. I had to cancel it after waiting for an hour or so. and to what type of storage do these images go? I'd think that in case of an image backup you'd want a management class that makes them go directly to tape. My guess is that these were going to disk volumes? What is my best strategy for dealing with these two boxes that are generating thousands of new files in new directories every day? The huge number of objects in the TSM DB are starting to cause quite a few problems with daily processing also as expiration is running longer and longer since I think it is choking on the number of objects. I'd say that image backups are a good idea in cases of very active filesystems. Filesystems on windows with huge numbers of files are always a cause of problems, not only with TSM. And to make it even weirder, they both fail incrementals at night and the only error I can find is: ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) meaning that indeed the client is indeed choking on the size of the directories. I'm starting to think that TSM is just not the backup solution for either of these boxes. I'm also thinking that if you have a piece of software creating 1000's of files per day in a filesystem, that this is a very big workload. I'm very sure that with VSS snapshots and image backups, you are on the right track and no other product could do a better job of backing up these filesystems. -- Remco Post r.p...@plcs.nl +31 6 24821 622
Re: How do I request to be removed from the list?
Send an email to lists...@vm.marist.edu with SIGNOFF ADSM-L in the body of the message David Browne dbro...@humana.com Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 01/15/2009 09:02 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] How do I request to be removed from the list? The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
Re: 2 Windows 2003 clients with huge # of files consistently failing
On Jan 15, 2009, at 9:26 AM, John C Dury wrote: ANR0481W Session 16603 for node SERVERNAME (WinNT) terminated - client did not respond within 9000 seconds. (SESSION: 16603) If TSM is struggling to get through the directories, then applications associated with the data may be suffering the same problem. This may be the result of indifferent directory layout (far too many files in directories) or disk hardware issue or contention or file system issue (where chkdsk or equivalent might be run). The hardware may simply be underpowered for the amount of data involved (e.g., 5400 rpm disks or perhaps older ATA pathing). Or the file system type may be an inefficient choice. Large-scale data deployments cry out for a knowledgeable data architect in order to be successful and to scale - and that skill is often absent. The owners of the data should be strongly advised to regard the backup problem as a proportional indication of how very painful a file- oriented restoral would be, where reconstructing Windows directory entries is notoriously time-consuming. Richard Sims
Re: Open File Support -Win2k3 32bit vs 64bit
I think you should treat all skipped open files the same way. Unless you know for sure that taking a backup of an open file is OK, I think OFS just gives you a false warm and fuzzy feeling. Just because you get a backup doesn't necessarily mean it's a GOOD backup. So now you're at D/R and that critical file for the application that you've been successfully backing up with OFS proves to be unusable after the restore. Plus according to the latest client manual: There are two snapshot providers that can be used for open file support: LVSA and VSS (VSS is not supported on WindowsR XP). VSS is the recommended solution, since it utilizes Microsoft's strategic snapshot solution. The LVSA is provided for customers migrating from prior versions of TivoliR Storage Manager, where LVSA was utilized, and as an alternative to VSS if there are issues with using VSS. The option is: Snapshotproviderfs LVSA | VSS | NONE. Bill Boyer -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Wanda Prather Sent: Thursday, January 15, 2009 8:32 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Open File Support -Win2k3 32bit vs 64bit Jason, Before you go further down the OFS rabbit hole: On Windows, it is rare to use OFS for backups of MS apps like SQL. Those files are in use by MS SQL. Backing them up via OFS just gives you a copy of a possibly unstable/inconsistent file that may not be usable on restore. When you see those skipped files on the daily report, your response should be: 1) Find out what those files are 2) If they belong to a DB app, make sure the DB is being backed up through an application-appropriate method. For SQL, you can a) use the SQL manager to dump the files into the \backups directory on the box. Those are flat files that are never locked, and TSM can back them up just fine. b) If the DB's are too large to dump to flat files, implement the TSM for SQL agent. 3) Once the DB files are backed up elsewhere appropriately, put an EXCLUDE statement in the dsm.opt file (or a client option set on the server) so that you don't get the skipped files msgs from the backup/archive client in your daily report anymore. W On Wed, Jan 14, 2009 at 6:00 PM, Jason Clarke j...@gwsc.vic.edu.au wrote: Hi list, First post, new admin, thrown in the deep end :-) 5.4 server, 5.4 clients. New installs everywhere. Win2k3 64bit server, mixture of Win2k3,2k,XP,Linux clients. Going through the nightly Operational Report, I'm noticing that various files are not backed up due to being in use. They're all 64bit machines. When I did the client installs I made sure that Open File Support was installed. However, the 64bit installer appears to not have it. Funnily enough, the 64bit machines are the more important servers. SQL/FSMO Roles etc. Where do I look for more info regarding Open File support for 2k3 64bit, either enabling it, using it or installing it? Regards, Jason Clarke -- Network Manager Glen Waverley S.C. p 03 8805 6750 m 0418 145 318 e j...@gwsc.vic.edu.au Please consider the environment before printing this email.
SQL Server backups with mirrors
I have a client with 2 SQLServer boxes: CL01 and CL02. Each has its own set of databases, but there are 3 databases on CL01 that are mirrored over to CL02. The TDP backup on CL02 fails on those 3 databases because they are used in a mirror. The owner doesn't want to exclude those databases on CL02 in case of a failover. Then the databases will get backed up without having to change the exclude list. Is there a way to have the TDP agent skip those files if they are actively in a mirror? The backup schedule event fails-402 every night and we need to look at the log to verify that it's just those 3 mirrors. Maybe there's a script or something we could run before the backup? Any ideas are appreciated. Bill Boyer Hang in there, retirement is only thirty years away! - ??
Re: Version
Hello Everyone, What are the latest version are for the ISC and AdminCenter Thank you James --- Confidentiality Notice: The information in this e-mail and any attachments thereto is intended for the named recipient(s) only. This e-mail, including any attachments, may contain information that is privileged and confidential and subject to legal restrictions and penalties regarding its unauthorized disclosure or other use. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action or inaction in reliance on the contents of this e-mail and any of its attachments is STRICTLY PROHIBITED. If you have received this e-mail in error, please immediately notify the sender via return e-mail; delete this e-mail and all attachments from your e-mail system and your computer system and network; and destroy any paper copies you may have in your possession. Thank you for your cooperation.
How I find out how often and how has accessed a storagepool with restore requests
How I find out how often and how has accessed a storagepool with restore requests
How to figure collocation overhead
Is there a guide or rule of thumb for determining what collocation will do to library space? It is being considered for improving restore speeds. I'm backing up 80TB in 30 volumes(filespaces) on a solaris server. Currently there is no collocation set, all data goes to a long-term management class, single onsite and off-site tape pools, data churn averages 1TB/night. Using a 650 slot L700 library, LTO3, TSM 5.5, AIX 5.3. The library is 80% full, so, I'm concerned that starting collocation for the volumes will consume the rest of the library. Each filespace collocation may end up with one tape not full (or 30 in this case). Thanks, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER
Re: How to figure collocation overhead
You can easily determine how many lines of tapes you will initially break out into, based upon which of the multiple types of collocation you ultimately decide upon and how many nodes or filespaces are active, sending data to TSM storage. I would double that number to account for tape leak, based upon historic experience. And if there are Windows clients, think more about DIRMc in that context. I think most of us implement collocation judiciously, based partly upon library cell impact, but probably more so on realities of tape drive contention. A big arrival disk pool facilitates more realistic collocation. Richard Sims
Re: How to figure collocation overhead
Collocation consumes as much of the library as you tell it to. When you set MAXSCRATCH on a storage pool, TSM will confine the pool to that number of tapes. If you have less tapes available than you have clients, you get a do the best you can collocation. There are plenty of sites who have more clients than slots in their library. If you have 100 clients and set MAXSCRATCH for the pool to 50 tapes, TSM will put each client on a different tape until it hits 50, then it will double up. You still get a decent amount of collocation; it's a lot faster for a restore to skip over another clients data on the same tape, than it is to rewind, dismount, mount, and reposition to a different tape. What you have to remember if you are collocating, is that you have to check your pools periodically and reevaluate maxscratch for the pool. If your total amount of data is growing, you will need to up the maxscratch periodically so that you maintain enough available free tapes in the pool to provide a reasonable level of collocation. W On Thu, Jan 15, 2009 at 1:34 PM, Evans, Bill bev...@fhcrc.org wrote: Is there a guide or rule of thumb for determining what collocation will do to library space? It is being considered for improving restore speeds. I'm backing up 80TB in 30 volumes(filespaces) on a solaris server. Currently there is no collocation set, all data goes to a long-term management class, single onsite and off-site tape pools, data churn averages 1TB/night. Using a 650 slot L700 library, LTO3, TSM 5.5, AIX 5.3. The library is 80% full, so, I'm concerned that starting collocation for the volumes will consume the rest of the library. Each filespace collocation may end up with one tape not full (or 30 in this case). Thanks, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER
Rebuild of TSM on a fresh Windows server OS installation
Hello Everyone, I have a few questions. I have a TSM server 5.3.6 that the Windows server 2003 OS is really dragging something in the OS is corrupt and I am unable to repair it or correct the non responsiveness. TSM through the dsmadmc command line is fast and TSM is functioning as I would expect it. I would like to format the OS and start on a fresh Windows server 2003 install and go to the version of TSM 5.5.0. Is there anything I need to backup before I do this besides the DB and log Volumes? Will I have to install 5.3.6 first then upgrade? The OS is almost nonresponsive so upgrading before hand is out of the question. DB Volumes C:\TSMDATA\SERVER1\DB1.DSM C:\TSMDATA\SERVER1\DB2.DSM C:\TSMDATA\SERVER1\DB3.DSM C:\TSMDATA\SERVER1\DB4.DSM Log Volumes C:\TSMDATA\SERVER1\LOG1.DSM C:\TSMDATA\SERVER1\LOG1.DSM What if we didn't care to keep the old data but want to keep the config? Could we go straight to 5.5.0 then on the fresh install? Any and all help is much appreciated! Thank You, Dan Lane
Re: Version
Hi James, I believe TSM 5.5 uses ISC 6.0.1 and AdminCenter 5.5 On Thu, Jan 15, 2009 at 10:05 AM, Lepre, James jle...@solixinc.com wrote: Hello Everyone, What are the latest version are for the ISC and AdminCenter Thank you James --- Confidentiality Notice: The information in this e-mail and any attachments thereto is intended for the named recipient(s) only. This e-mail, including any attachments, may contain information that is privileged and confidential and subject to legal restrictions and penalties regarding its unauthorized disclosure or other use. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action or inaction in reliance on the contents of this e-mail and any of its attachments is STRICTLY PROHIBITED. If you have received this e-mail in error, please immediately notify the sender via return e-mail; delete this e-mail and all attachments from your e-mail system and your computer system and network; and destroy any paper copies you may have in your possession. Thank you for your cooperation. -- Sam Rawlins
Re: How to figure collocation overhead
Hi Bill, I like Wanda's point. MAXSCRatch is the best way to control tape usage. You can probably write a fun select to see how many nodes have data on the average tape. In Wanda's example, there are about 2 nodes per tape. If you see that that number gets too high, you can increase MAXSCRatch. On Thu, Jan 15, 2009 at 11:53 AM, Wanda Prather wanda.prat...@jasi.comwrote: Collocation consumes as much of the library as you tell it to. When you set MAXSCRATCH on a storage pool, TSM will confine the pool to that number of tapes. If you have less tapes available than you have clients, you get a do the best you can collocation. There are plenty of sites who have more clients than slots in their library. If you have 100 clients and set MAXSCRATCH for the pool to 50 tapes, TSM will put each client on a different tape until it hits 50, then it will double up. You still get a decent amount of collocation; it's a lot faster for a restore to skip over another clients data on the same tape, than it is to rewind, dismount, mount, and reposition to a different tape. What you have to remember if you are collocating, is that you have to check your pools periodically and reevaluate maxscratch for the pool. If your total amount of data is growing, you will need to up the maxscratch periodically so that you maintain enough available free tapes in the pool to provide a reasonable level of collocation. W On Thu, Jan 15, 2009 at 1:34 PM, Evans, Bill bev...@fhcrc.org wrote: Is there a guide or rule of thumb for determining what collocation will do to library space? It is being considered for improving restore speeds. I'm backing up 80TB in 30 volumes(filespaces) on a solaris server. Currently there is no collocation set, all data goes to a long-term management class, single onsite and off-site tape pools, data churn averages 1TB/night. Using a 650 slot L700 library, LTO3, TSM 5.5, AIX 5.3. The library is 80% full, so, I'm concerned that starting collocation for the volumes will consume the rest of the library. Each filespace collocation may end up with one tape not full (or 30 in this case). Thanks, Bill Evans Research Computing Support FRED HUTCHINSON CANCER RESEARCH CENTER -- Sam Rawlins
Re: Inactive Version
Hello Everyone, Is there a select statement that will tell me how many active and inactive versions of files are on the nodes that are backing up. Thank you James Lepre Senior Server Specialist Solix, Inc. 100 S. Jefferson Road Whippany, NJ 07981 Phone: 973-581-5362 Cell: 973-223-1921 --- Confidentiality Notice: The information in this e-mail and any attachments thereto is intended for the named recipient(s) only. This e-mail, including any attachments, may contain information that is privileged and confidential and subject to legal restrictions and penalties regarding its unauthorized disclosure or other use. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action or inaction in reliance on the contents of this e-mail and any of its attachments is STRICTLY PROHIBITED. If you have received this e-mail in error, please immediately notify the sender via return e-mail; delete this e-mail and all attachments from your e-mail system and your computer system and network; and destroy any paper copies you may have in your possession. Thank you for your cooperation.
Re: Inactive Version
select count(*) from backups where state='INACTIVE_VERSION' and node_name='YOUR_NODENAME' warning that trolling through the backups table can be very time consuming and expensive. John At 03:33 PM 1/15/2009, you wrote: Hello Everyone, Is there a select statement that will tell me how many active and inactive versions of files are on the nodes that are backing up. Thank you James Lepre Senior Server Specialist Solix, Inc. 100 S. Jefferson Road Whippany, NJ 07981 Phone: 973-581-5362 Cell: 973-223-1921 --- Confidentiality Notice: The information in this e-mail and any attachments thereto is intended for the named recipient(s) only. This e-mail, including any attachments, may contain information that is privileged and confidential and subject to legal restrictions and penalties regarding its unauthorized disclosure or other use. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action or inaction in reliance on the contents of this e-mail and any of its attachments is STRICTLY PROHIBITED. If you have received this e-mail in error, please immediately notify the sender via return e-mail; delete this e-mail and all attachments from your e-mail system and your computer system and network; and destroy any paper copies you may have in your possession. Thank you for your cooperation.
Re: How to delete Volhistory...
The below command is not working for me.Iam using TSM Server 5.5.0 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Robben Leaf Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... Not entirely true. The product doesn't provide a DOCUMENTED way to do this. There are some undocumented parameters for the DELETE VOLHIST command. Specifically, you can add vol=VOLNAME force=yes to the command to remove the volume forcibly from the volhistory. We have found this command necessary when our library manager thinks another TSM server instance still owns a tape, when that instance has forgotten all about it. Robben Leaf From: Richard Sims r...@bu.edu To: ADSM-L@VM.MARIST.EDU Date: 01/08/2009 06:14 AM Subject: Re: [ADSM-L] How to delete Volhistory... Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote: Please let me know how to delete volume history of a particular Volume. The product does not provide a way to do this. Richard Sims U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address
Re: How to delete Volhistory...
We need detail Kiran, if we are to help. Please post the command you are using and the output when it doesn't work. also the output of a select * from volhistory where volume_name='XYZ000L3' - with your volume of interest substituted Thanks Steve Steven Harris TSM Administrator, Sydney Australia KIRAN-SYSTEMS ki...@dqentertai NMENT.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] How to delete Volhistory... 16/01/2009 04:12 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The below command is not working for me.Iam using TSM Server 5.5.0 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Robben Leaf Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... Not entirely true. The product doesn't provide a DOCUMENTED way to do this. There are some undocumented parameters for the DELETE VOLHIST command. Specifically, you can add vol=VOLNAME force=yes to the command to remove the volume forcibly from the volhistory. We have found this command necessary when our library manager thinks another TSM server instance still owns a tape, when that instance has forgotten all about it. Robben Leaf From: Richard Sims r...@bu.edu To: ADSM-L@VM.MARIST.EDU Date: 01/08/2009 06:14 AM Subject: Re: [ADSM-L] How to delete Volhistory... Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote: Please let me know how to delete volume history of a particular Volume. The product does not provide a way to do this. Richard Sims U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address
Re: How to delete Volhistory...
I am using the below command to delete volhis of a library client server from library manager server Del volhis vol=volume name force=yes -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Steven Harris Sent: Friday, January 16, 2009 11:24 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... We need detail Kiran, if we are to help. Please post the command you are using and the output when it doesn't work. also the output of a select * from volhistory where volume_name='XYZ000L3' - with your volume of interest substituted Thanks Steve Steven Harris TSM Administrator, Sydney Australia KIRAN-SYSTEMS ki...@dqentertai NMENT.COM To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] How to delete Volhistory... 16/01/2009 04:12 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The below command is not working for me.Iam using TSM Server 5.5.0 -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Robben Leaf Sent: Friday, January 09, 2009 1:02 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] How to delete Volhistory... Not entirely true. The product doesn't provide a DOCUMENTED way to do this. There are some undocumented parameters for the DELETE VOLHIST command. Specifically, you can add vol=VOLNAME force=yes to the command to remove the volume forcibly from the volhistory. We have found this command necessary when our library manager thinks another TSM server instance still owns a tape, when that instance has forgotten all about it. Robben Leaf From: Richard Sims r...@bu.edu To: ADSM-L@VM.MARIST.EDU Date: 01/08/2009 06:14 AM Subject: Re: [ADSM-L] How to delete Volhistory... Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU On Jan 8, 2009, at 12:27 AM, KIRAN-SYSTEMS wrote: Please let me know how to delete volume history of a particular Volume. The product does not provide a way to do this. Richard Sims U.S. BANCORP made the following annotations - Electronic Privacy Notice. This e-mail, and any attachments, contains information that is, or may be, covered by electronic communications privacy laws, and is also confidential and proprietary in nature. If you are not the intended recipient, please be advised that you are legally prohibited from retaining, using, copying, distributing, or otherwise disclosing this information in any manner. Instead, please reply to the sender that you have received this communication in error, and then immediately delete it. Thank you in advance for your cooperation. - Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any virus in this e-mail. DQE shall not be liable for the views expressed in the e-mail. DQE reserves the right to monitor and review the content of all messages sent to or from this e-mail address Disclaimer: This email message (including attachments if any) may contain privileged, proprietary, confidential information, which may be exempt from any kind of disclosure whatsoever and is intended solely for the use of addressee (s). If you are not the intended recipient, kindly inform us by return e-mail and also kindly disregard the contents of the e-mail, delete the original message and destroy any copies thereof immediately. You are notified that any dissemination, distribution or copying of this communication is strictly prohibited unless approved by the sender. DQ Entertainment (DQE) has taken every reasonable precaution to minimize the risk of transmission of computer viruses with this e-mail; DQE is not liable for any damage you may sustain as a result of any
