Message ANR0481W, ANS1809W, ANS1810E: Session lost
Hello *SM*ers, since we changed our network interface on the tsm server (IBM P630, AIX5.3) to Gigabit Eth, we get very often the error ANR0481W, Session lost. On the Client Error Log we get the message ANS1809W, ANS1810E very often. On the server side the option for commtimeout is 3600 and idletimeout is 60. Has anyone an idea what the problem my be? Can I increase commtimeout to 7200 and idletimeout to 120? Best regards gerd w. becker, emprise
Re: Message ANR0481W, ANS1809W, ANS1810E: Session lost
On Apr 13, 2007, at 5:11 AM, Gerd Becker wrote: Hello *SM*ers, since we changed our network interface on the tsm server (IBM P630, AIX5.3) to Gigabit Eth, we get very often the error ANR0481W, Session lost. On the Client Error Log we get the message ANS1809W, ANS1810E very often. On the server side the option for commtimeout is 3600 and idletimeout is 60. Has anyone an idea what the problem my be? Can I increase commtimeout to 7200 and idletimeout to 120? Best regards gerd w. becker, emprise Gerd - Your timeout values look sufficient to me - and if they were good for processing before this change, then they probably are still good, unto themselves. I would suspect the network change, which may have been introduced into the environment without adequate testing or configuration guidance to those using it. I would pursue TCP load testing outside of TSM, looking for anomalies in operation, as well as conferring with your networking people. Note that the TSM Messages manual says of ANS1809W: Frequent occurrences of the ANS1809W message can indicate a problem with the network. If this message is repeatedly found in the dsmerror.log, investigate possible networking trouble, such as a failing network interface card or router problem. One common problem is the media speed of the network adaptors: If the network adaptors are set to ′′auto-negotiate′′, try changing them to ′′100% fullduplex ′′. [Note that with gige, you may be forced to use autonegotiation rather than fixed settings; but perform quality assurance tests nonetheless.] Richard Sims
Re: Message ANR0481W, ANS1809W, ANS1810E: Session lost
On Apr 13, 2007, at 5:11 AM, Gerd Becker wrote: Hello *SM*ers, since we changed our network interface on the tsm server (IBM P630, AIX5.3) to Gigabit Eth, we get very often the error ANR0481W, Session lost. On the Client Error Log we get the message ANS1809W, ANS1810E very often. On the server side the option for commtimeout is 3600 and idletimeout is 60. Has anyone an idea what the problem my be? Can I increase commtimeout to 7200 and idletimeout to 120? Some further thoughts on this... We don't know what networking you had before, but probably 100 Mbps: Did the introduction of gige substantially improve the elapsed time of your backups - or are they actually taking longer now? Taking longer definitely points to networking problems. Also, where backups take longer, the RESOURceutilization value which is in effect may result in Producer sessions timing out while Consumer sessions struggle over a longer period of time to pump data through the problematic pipe. The termination of a Producer session is not inherently bad, as the TSM client will start one afresh (ANS1810E) when the Consumer session has concluded its backup work, when session summary statistics need to be conveyed to the TSM server for it to log as ANE messages in the Activity Log. If you perform Query SEssion through the backups period and continue to see viable client sessions continually feeding data to the server, then you have good Consumer sessions going on; and you may also see companion Producer sessions for that node, and possibly see them disappear over time, as they idle timeout. You can do 'Query Node F=D' to inspect session values and get a quick sense of where delays were in the last backup session, or run a report on your TSM accounting records for before the gige change and then after, to see if any dramatic wait time changes. Richard Sims
Re: New personal best.
I will try it !! but the main problem of migrating from disk to tape using only one tape drive will remain here... due to GPFS expectative to continuously growth (millions of files // 10 versions) and not lose the centralized point of view of one node. The other option is to do move datas from disk to tape to use more tape drives but I think I am losing stgpools functionality :-( Regards, Ibán. Skylar Thompson wrote: Ibán Bernaldo de Quirós Márquez wrote: I have tried virtualmountpoint without chance (or without experience)... I meant that I have one TSM for one FS (8.000.000- today, 16.000.000 of files- future // 10 versions) This FS is represented by one node... the first stage is disk... so when I migrate to tape, I only have one process... :'( :'( And creating more than one node with virtual mount points seems to me so tedious to restore... do you disk at first stage ¿? Or are you backing up to tape directly ¿? My solution has been to force big files (1GB at our site) to tape, but spool small files on disk. You can do this with the MAXSIZE parameter on your disk storage pool.
Follow-up on: Problems with Imation ultrium-2 (LTO-2) tapes?
Just for what it's worth - an observation. I run about 2.4 TB of data through my 3584 on a daily process, between archives, backups, and off-site copies. I've had the same 4 cleaning tapes in place since my first 3584, with LTO-1 drives, just over 5 years now - and one tape has had a count of 11 uses. All from early days, using the tape to verify drives after maintenance. The count is now at 35; I've done 24 cleaning cycles this week on 16 drives. I have an RMA number. Tom - Is there any particular firmware I should be running in my IBM drives to work with Imation tapes? We've been running Fuji and IBM with no issues for years, but we put a group of new Imation tapes in Friday - and I've had write errors on 4 of them so far, and a read error on one that caused the drive to go not-ready to the point it won't soft-reset. I am back-level on drive firmware (I don't usaually fix anything that's working) so I thought I'd check that before I get an RMA from the vendor for the tapes. TIA Tom Kauffman NIBCO Inc. CONFIDENTIALITY NOTICE: This email and any attachments are for the exclusive and confidential use of the intended recipient. If you are not the intended recipient, please do not read, distribute or take action in reliance upon this message. If you have received this in error, please notify us immediately by return email and promptly delete this message and its attachments from your computer system. We do not waive attorney-client or work product privilege by the transmission of this message.
ANS1469E Error processing filexyz, invalid encription key
Hi, Several years ago I included encryption on our Payroll Server node name FS4 - TSM Backup client V5.2 This TSM client has now been rebuilt with new OS Windows 2003, previously it was Windows 2000. Before I installed the TSM Backup client (V5.3) today, I renamed the old filespaces to OLD_xxx. I have not introduced encryption as yet ( no enteries in dsm.opt to indicate encryption) on the new setup. When I try to restore files from the the old filespaces (only as a test) it fails :- ANS1469E Error processing filexxyz , invalid encryption key Then it asks for the encryption password and confirmation, but it still fails . I am sure that I am entering the correct encryption password. Is there any way round this ? Also 4 weeks ago we upgraded the TSM Server(Windows)from V5.2.2.1 to V5.3.4.0 It's not critical if I can't restore these old files, but it would be nice to know a fix if there is any ? Thanks Bill ** This electronic mail message, including any attachments, is a confidential communication exclusively between Babcock International Group PLC or its subsidiary company and the intended recipient(s) indicated as the addressee(s). It contains information which is private and may be proprietary or covered by legal professional privilege. If you receive this message in any form and you are not the intended recipient you must not review, use, disclose or disseminate it. We would be grateful if you could contact the sender upon receipt and in any event you should destroy this message without delay. Anything contained in this message that is not connected with the business of Babcock International Group PLC is neither endorsed by nor is the liability of this company. Babcock International Group PLC Company number 2342138 Registered in England 2 Cavendish Square London W1G 0PX Telephone: +44(0)20 7291 5000 Fax: +44(0)20 7291 5055 Website: www.babcock.co.uk **
Re: Follow-up on: Problems with Imation ultrium-2 (LTO-2) tapes?
When we first install our first 3584 three years ago, we bought around 200 Imation LTO2 tapes. They lasted about a month and we also RMA'd them all... We've been on Maxell's for the last three years with maybe 10 tapes, at the most, that have been bad from hundreds of tapes. (And we're not sure it was the tape that was bad, but maybe a bad drive causing it to fail.) We have a volume of about 1.2TB/day. We've heard several similar stories as ours. But, another local company uses Imation in their 3584 (although 3494, not LTO2) with no problems. Troy Barnhart, Sr. Systems Programmer [EMAIL PROTECTED] Regional Health, Inc. 353 Fairmont Boulevard Rapid City, South Dakota 57701 PH: 605-716-8352 / FAX: 605-716-8302 -Original Message- From: Kauffman, Tom [mailto:[EMAIL PROTECTED] Sent: Friday, April 13, 2007 7:04 AM To: [EMAIL PROTECTED] Subject: [ADSM-L] Follow-up on: Problems with Imation ultrium-2 (LTO-2) tapes? Just for what it's worth - an observation. I run about 2.4 TB of data through my 3584 on a daily process, between archives, backups, and off-site copies. I've had the same 4 cleaning tapes in place since my first 3584, with LTO-1 drives, just over 5 years now - and one tape has had a count of 11 uses. All from early days, using the tape to verify drives after maintenance. The count is now at 35; I've done 24 cleaning cycles this week on 16 drives. I have an RMA number. Tom - Is there any particular firmware I should be running in my IBM drives to work with Imation tapes? We've been running Fuji and IBM with no issues for years, but we put a group of new Imation tapes in Friday - and I've had write errors on 4 of them so far, and a read error on one that caused the drive to go not-ready to the point it won't soft-reset. I am back-level on drive firmware (I don't usually fix anything that's working) so I thought I'd check that before I get an RMA from the vendor for the tapes. TIA Tom Kauffman NIBCO Inc. ***Note: The information contained in this message, including any attachments, may be privileged, confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the Sender immediately by a reply to sender only message and destroy all electronic or paper copies of the communication, including any attachments.
RESOURCEUTILIZATION for EXCHANGE TDP?
Is it possible to set RESOURCEUTILIZATION as an option for EXCHANGE? I can't find it in the online documentation. Fred Johanson
Re: RESOURCEUTILIZATION for EXCHANGE TDP?
On Apr 13, 2007, at 12:02 PM, Fred Johanson wrote: Is it possible to set RESOURCEUTILIZATION as an option for EXCHANGE? I can't find it in the online documentation. The TDPs are based upon the TSM API. RESOURceutilization is not available in the API: the option is used to funnel data at the file level, and the TSM API does not perform any file I/O. Richard Sims
Re: RESOURCEUTILIZATION for EXCHANGE TDP?
I thought the answer was something like that. But I'd like to know if there's a way to have the different storage groups back up simultaneously instead of seriatim. Original message Date: Fri, 13 Apr 2007 12:09:27 -0400 From: Richard Sims [EMAIL PROTECTED] Subject: Re: [ADSM-L] RESOURCEUTILIZATION for EXCHANGE TDP? To: [EMAIL PROTECTED] On Apr 13, 2007, at 12:02 PM, Fred Johanson wrote: Is it possible to set RESOURCEUTILIZATION as an option for EXCHANGE? I can't find it in the online documentation. The TDPs are based upon the TSM API. RESOURceutilization is not available in the API: the option is used to funnel data at the file level, and the TSM API does not perform any file I/O. Richard Sims Fred Johanson
LTO Tape Encryption Ideas
Folks, I've looked at the Redbook highlighting TS1120 tape encryption to get the overall idea. In the more general case of LTO3 and LTO4 drives, which can encrypt data, how are folks implementing this? Thanks, Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED]
Re: LTO Tape Encryption Ideas
LTO4 will include the encryption capabilities. http://www.ultrium.com/newsite/html/news_4_17_06.html : : Greg Yuzik : : -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Lipp Sent: Friday, April 13, 2007 12:32 PM To: [EMAIL PROTECTED] Subject: [ADSM-L] LTO Tape Encryption Ideas Folks, I've looked at the Redbook highlighting TS1120 tape encryption to get the overall idea. In the more general case of LTO3 and LTO4 drives, which can encrypt data, how are folks implementing this? Thanks, Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED]
Re: LTO Tape Encryption Ideas
Just saw this announcement: HP AND IBM PASS MECHANISM COMPLIANCE TESTING FOR LTO ULTRIUM FORMAT GENERATION 4 TAPE DRIVES Brings New Generation of Tape Hardware with Drive-Level Encryption, WORM, Capacity and Performance Enhancements SILICON VALLEY, CALIF. - (April 11, 2007) - HP, IBM and Quantum, the three technology provider companies (TPCs) for the Linear Tape-Open (LTO) Program, today announced that HP and IBM have completed the LTO Ultrium format generation 4 compliance and data interchangeability testing process. With this qualification, HP and IBM will be authorized to display the LTO Ultrium format generation 4 logo on their tape drives. In adherence to its compliance testing, the LTO Program requires that all licensees pass a series of compliance verification tests, which call for data interchangeability testing before being issued a license and the right to display the LTO Ultrium trademark. Compliance testing of all Ultrium products is completed annually to help ensure that all manufacturers adhere to the LTO Ultrium format specifications. Buyers seeking Ultrium format-compliant products should look for the LTO Ultrium format trademark logo on both tape drives and data cartridges. LTO Ultrium generation 4 delivers the features that storage customers require, including 256-Bit encryption for added security of offsite media, and higher capacities to support their ever-growing data storage needs. This is another key milestone to have successfully passed the LTO Program's compliance verification tests, said Bob Wilson, vice president, Nearline Storage Division, HP. The ability to introduce products that fully comply with the LTO Ultrium specification and support data security with tape drive encryption allows our customers to take advantage of the open format flexibility, total cost of ownership and investment protection benefits of LTO generation 4 technology, said Cindy Grossman, vice president, IBM Tape Systems. The LTO Ultrium format generation 4 specification, announced in January of this year, allows for licensees to deliver a doubling of storage capacity over generation 3, with the LTO Ultrium format generation 4 cartridges storing up to 1.6TB of data compared to 800GB on the previous generation*. Transfer rates of the new generation are also improved, with backup and archiving performance reaching speeds up to 240MB per second in generation 4 versus up to 160MB per second in generation 3*. As with generation 3, the LTO Ultrium format generation 4 continues to offer WORM (Write-Once, Read-Many) functionality that provides a cost-effective means for storing data in a non-rewriteable format to help address compliance requirements. For additional security, generation 4 supports 256-Bit AES-GCM encryption capabilities at the tape drive level that are designed to enable the writing of encrypted data to the LTO Ultrium tape cartridge, helping to protect the storage and transport of sensitive information. LTO Ultrium generation 4 also delivers investment protection for business, providing for drives with backwards-compatible read-and-write capability to store and retrieve non-encrypted data with the Ultrium format generation 3 cartridges, and backward-read capabilities with generation 2 cartridges. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Greg Yuzik Sent: Friday, April 13, 2007 4:07 PM To: [EMAIL PROTECTED] Subject: Re: LTO Tape Encryption Ideas LTO4 will include the encryption capabilities. http://www.ultrium.com/newsite/html/news_4_17_06.html : : Greg Yuzik : : -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Lipp Sent: Friday, April 13, 2007 12:32 PM To: [EMAIL PROTECTED] Subject: [ADSM-L] LTO Tape Encryption Ideas Folks, I've looked at the Redbook highlighting TS1120 tape encryption to get the overall idea. In the more general case of LTO3 and LTO4 drives, which can encrypt data, how are folks implementing this? Thanks, Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED]
Re: LTO Tape Encryption Ideas
Hello Kelly, We are not doing encryption with tape drives, but have been asking the questions. My understanding is that lto-3's do not do encryption, have you heard something different. The encryption of the lto-4's is listed on the web site www.lto.org. http://www.lto.org/newsite/html/news_4_11_07.html For additional security, generation 4 supports 256-Bit AES-GCM encryption capabilities at the tape drive level that are designed to enable the writing of encrypted data to the LTO Ultrium tape cartridge, helping to protect the storage and transport of sensitive information. I do not know how true it is, but I heard that the lto-4's might use the same method's as the TS1120. len -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Lipp Sent: Friday, April 13, 2007 2:32 PM To: [EMAIL PROTECTED] Subject: [ADSM-L] LTO Tape Encryption Ideas Folks, I've looked at the Redbook highlighting TS1120 tape encryption to get the overall idea. In the more general case of LTO3 and LTO4 drives, which can encrypt data, how are folks implementing this? Thanks, Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED]
Best Business Practice for upgrading LTO2 drives in IBM 3584 Library
Hi. I am looking for the Best Business Practice for upgrading LTO2 drives in IBM 3584 Library. We have fourteen LTO2 in the library and about thousand or so LTO2 tapes. Would it be best to upgrade the some day the LTO2 drives to LTO3 and replace the LTO2 tapes as they become bad or on a quarterly basis replace the LTO2 scratch tapes that come from off-site to LTO3 tapes?? Or is there something better?? What does others have in their future years budget plans for tape drive 3584 library L32/D32s upgrades (LTO3, LTO4, etc.)??
Remove unwanted files
Hello, I am asked to exclude backing these filespace, but because they were backed up all these time until now, is there a way to remove the backed up ones off TSM to save some space? Thank you. e:\data\*.dbf e:\index\*.dbf e:\system\*.dbf d:\undo_temp\*.dbf Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
Remove unwanted files
Hello, I am asked to exclude backing these filespace, but because they were already backed up previously, is there a way to remove them off TSM to save some space? Thank you. e:\data\*.dbf e:\index\*.dbf e:\system\*.dbf d:\undo_temp\*.dbf Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
Re: Remove unwanted files
The next backup will delete all versions from TSM. -- Phillip (901)320-4462 (901)320-4856 FAX (901)652-6337 Cell (901)384-6337 Home -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, April 13, 2007 04:17 PM To: [EMAIL PROTECTED] Subject: [ADSM-L] Remove unwanted files Hello, I am asked to exclude backing these filespace, but because they were already backed up previously, is there a way to remove them off TSM to save some space? Thank you. e:\data\*.dbf e:\index\*.dbf e:\system\*.dbf d:\undo_temp\*.dbf Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.
Re: FW: [ADSM-L] DR of a VmWare logical server question
You cant, the machine name must match exactly in order for the systemstate restore option to even be available. Steve Schaub Systems Engineer, WNI BlueCross BlueShield of Tennessee 423-535-6574 (desk) 423-785-7347 (cell) -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lamb, Charles P. Sent: Wednesday, April 11, 2007 3:54 PM To: [EMAIL PROTECTED] Subject: Re: [ADSM-L] FW: [ADSM-L] DR of a VmWare logical server question Kelly Laura. OK. That worked. Step #1 thru 10 using restore command -- restore -fromnode=cgotst32 \\cgotst32\c$\* c:\ -replace=all -subdir=yes How do you restore systemservices and systemstate from cgotst32 to cgotst32b?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Kelly Lipp Sent: Wednesday, April 11, 2007 2:01 PM To: [EMAIL PROTECTED] Subject: [ADSM-L] FW: [ADSM-L] DR of a VmWare logical server question Laura Buckley has some ideas to solve this one... Give this a try and report back... Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED] From: Laura Buckley Sent: Wednesday, April 11, 2007 11:54 AM To: Kelly Lipp Subject: RE: [ADSM-L] DR of a VmWare logical server question Sounds like maybe he didn't set access on cgotst32 for cgotst32b. You have to do the following steps on cgotst32b To authorize another node to restore or retrieve your files: 1. Click Utilities - Node Access List from the main window. The Node Access List window appears. 2. Click the Add button. The Add Access Rule window appears. 3. In the Add Access Rule window, select an item in the Permit Access to field to specify the type of data that the other user can access. You can select either Backed up Objects or Archived Objects. 4. Type the node name of the user in the Grant Access to Node field. Type the node name of the user's host machine in the Grant Access to Node field. 5. Type the name of a user on the host machine in the User field. 6. In the Filespace and Directory field, select the file space and the directory that the user can access. You can select one file space and one directory at a time. If you want to give the user access to another file space or directory, you must create another access rule. 7. If you want to limit the user to specific files in the directory, type the name or pattern of the files on the server that the other user can access in the Filename field. You can make only one entry in the Filename field. It can either be a single file name or a pattern which matches one or more files. You can use a wildcard character as part of the pattern. Your entry must match files that have been stored on the server. 8. If you want to give access to all files that match the file name specification within the selected directory including its subdirectories, click Include subdirectories 9. Click the OK button to save the access rule and close the Add Access Rule window. 10. The access rule that you created is displayed in the list box in the Node Access List window. When you have finished working with the Node Access List window, click the OK button. If you do not want to save your changes, click Cancel or close the window. Then to do the restore on cgotst32b If you are using commands, use the fromnode option to indicate the node. You must also use the file space name, rather than the drive letter, to select the restore-retrieve drive you want to access. Include the file space name in braces and use it like a drive letter. For example, to restore cougar's files from the \projx directory on the d-disk file space to your own \projx directory, enter: dsmc restore -fromnode=cougar \\cougar\d$\projx\* d:\projx\ Use the query filespace command to display a list of file spaces. For example, to display a list of cougar's file spaces, enter: dsmc query filespace -fromnode=cougar -Original Message- From: Kelly Lipp Sent: Wednesday, April 11, 2007 11:37 AM To: Laura Buckley Subject: FW: [ADSM-L] DR of a VmWare logical server question Some folks struggling with this! Kelly J. Lipp VP Manufacturing CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 [EMAIL PROTECTED] -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Lamb, Charles P. Sent: Wednesday, April 11, 2007 10:32 AM To: [EMAIL PROTECTED] Subject: [ADSM-L] DR of a VmWare logical server question Hi... I am having problems with restoring a VmWare logical server (cgotst32) to another VmWare logical server (cgotst32b). It just will not restore. Any help from the TSM group which is smarter then myself?? TSM server v5.2.7.3 TSM client V5.4.0.2 MS W2K3 R2 VmWare logical server I changed TSM password on cgotst32 to allow cgotst32b to see
Re: Remove unwanted files
On Apr 13, 2007, at 5:17 PM, Avy Wong wrote: I am asked to exclude backing these filespace, but because they were already backed up previously, is there a way to remove them off TSM to save some space? Thank you. The most straightforward way to exclude a filesystem/drive is not do have it participate in Domain statements. Use Exclude statements for files or directories, where basic exclusion inherently causes inactivation of those Active files on the server, and begins the age-out process, per prevailing retention policies. Modern clients also provide Expire and Delete Backup commands to hasten the process. Obsolete filespaces are removed via 'dsmc delete filespace' from the client, or Delete Filespace ... from the server. Always be absolutely certain that supposedly obsolete filespaces really are. Richard Sims
Re: Remove unwanted files
If you do that, then the next backup will EXPIRE the backup copies on the TSM server. They will then be managed by the Versions Deleted, Retain Extra and Retain Only parameters. They will not be deleted immediately! There is a technique that has been discussed on this list and I've used on several occassions: 1. Define a new management class (I always call is ZERO) with VERE=1 VERD=0 RETE=0 RETO=0. 2. The first night change your include/exclude to Include e:\data\*.dbf ZERO Include e:\index\*.dbf ZERO Include e:\system\*.dbf ZERO Include d:\undo_temp\*.dbf ZERO 3. Now you will be left with only a single copy of the files in TSM server once the backup and expire inventory completes 4. Change your DSM.OPT for the next night's backup to: Exclude e:\data\*.dbf Exclude e:\index\*.dbf Exclude e:\system\*.dbf Exclude d:\undo_temp\*.dbf 5. After this backup all versions of the file will be deleted from TSM storage. I know this takes 2 days/cycles of backups to complete, but you are able to remove the files from TSM storage without having to wait for them to roll off. Bill Boyer A life? Cool! Where can I download one of those? - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ford, Phillip Sent: Friday, April 13, 2007 5:40 PM To: [EMAIL PROTECTED] Subject: Re: Remove unwanted files The next backup will delete all versions from TSM. -- Phillip (901)320-4462 (901)320-4856 FAX (901)652-6337 Cell (901)384-6337 Home -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, April 13, 2007 04:17 PM To: [EMAIL PROTECTED] Subject: [ADSM-L] Remove unwanted files Hello, I am asked to exclude backing these filespace, but because they were already backed up previously, is there a way to remove them off TSM to save some space? Thank you. e:\data\*.dbf e:\index\*.dbf e:\system\*.dbf d:\undo_temp\*.dbf Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete.
Re: Remove unwanted files
Thank you fellas... great information !! Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 William Boyer [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 04/13/2007 06:31 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: [ADSM-L] Remove unwanted files If you do that, then the next backup will EXPIRE the backup copies on the TSM server. They will then be managed by the Versions Deleted, Retain Extra and Retain Only parameters. They will not be deleted immediately! There is a technique that has been discussed on this list and I've used on several occassions: 1. Define a new management class (I always call is ZERO) with VERE=1 VERD=0 RETE=0 RETO=0. 2. The first night change your include/exclude to Include e:\data\*.dbf ZERO Include e:\index\*.dbf ZERO Include e:\system\*.dbf ZERO Include d:\undo_temp\*.dbf ZERO 3. Now you will be left with only a single copy of the files in TSM server once the backup and expire inventory completes 4. Change your DSM.OPT for the next night's backup to: Exclude e:\data\*.dbf Exclude e:\index\*.dbf Exclude e:\system\*.dbf Exclude d:\undo_temp\*.dbf 5. After this backup all versions of the file will be deleted from TSM storage. I know this takes 2 days/cycles of backups to complete, but you are able to remove the files from TSM storage without having to wait for them to roll off. Bill Boyer A life? Cool! Where can I download one of those? - ?? -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ford, Phillip Sent: Friday, April 13, 2007 5:40 PM To: [EMAIL PROTECTED] Subject: Re: Remove unwanted files The next backup will delete all versions from TSM. -- Phillip (901)320-4462 (901)320-4856 FAX (901)652-6337 Cell (901)384-6337 Home -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Avy Wong Sent: Friday, April 13, 2007 04:17 PM To: [EMAIL PROTECTED] Subject: [ADSM-L] Remove unwanted files Hello, I am asked to exclude backing these filespace, but because they were already backed up previously, is there a way to remove them off TSM to save some space? Thank you. e:\data\*.dbf e:\index\*.dbf e:\system\*.dbf d:\undo_temp\*.dbf Avy Wong Business Continuity Administrator Mohegan Sun 1 Mohegan Sun Blvd Uncasville, CT 06382 (860) 862-8164 cell (860) 961-6976 ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. ** * This message and any attachments are solely for the intended recipient. If you are not the intended recipient, disclosure, copying, use or distribution of the information included in this message is prohibited -- Please immediately and permanently delete. ** The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, or copy of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer. **
