Re: TSM 6.1 deduplication is invalid option for disk primary pools
Thank you very much Colin. I will configure storage pools with device class FILE. Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.com Please consider the environment before printing this Email -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Colin Dawson Sent: Wednesday, April 29, 2009 6:48 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM 6.1 deduplication is invalid option for disk primary pools Grigori, The primary decision for limiting deduplication to device classes of DEVTYPE=FILE has to do with the deduplication processing itself. Once a data chunk has been identified as being a duplicate of an existing data chunk, the TSM server leverages the reclamation and aggregate reconstruction algorithms. These algorithms are only available for device classes that exploit a device type of sequential media. So, the design decision or rational was to do this for DEVTYPE=FILE because the necessary infrastructure was more readily in place then what was available for DEVTYPE=DISK. Thanks, Colin - Colin Dawson TSM Server Development col...@us.ibm.com From: Grigori Solonovitch g.solonovi...@bkme.com To: ADSM-L@VM.MARIST.EDU Date: 04/29/2009 05:38 AM Subject:[ADSM-L] TSM 6.1 deduplication is invalid option for disk primary pools Hello Everybody, I am testing TSM 6.1 under AIX. I have tried to enable de-duplication for primary disk pool: tsm: BKMEupd stg daily_1 dedup=y ANR2344E UPDATE STGPOOL: The DEDUPLICATE option is not valid for device class DISK. ANS8001I Return code 3. tsm: BKME I have been affected too much by this message, because most of our primary pools are on FATA disks. Could somebody explain me why IBM is not able to use de-duplication for device class DISK? What is behind this? I understand I was reading all available before documentation not enough carefully, because I was sure that it is much easier to de-duplicate data on disks in comparison with tape drives. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Information Technology Bank of Kuwait and Middle East http://www.bkme.com Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: g.solonovi...@bkme.commailto:g.solonovi...@bkme.com Please consider the environment before printing this Email Please consider the environment before printing this Email. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME. This email message and any attachments transmitted with it may contain confidential and proprietary information, intended only for the named recipient(s). If you have received this message in error, or if you are not the named recipient(s), please delete this email after notifying the sender immediately. BKME cannot guarantee the integrity of this communication and accepts no liability for any damage caused by this email or its attachments due to viruses, any other defects, interception or unauthorized modification. The information, views, opinions and comments of this message are those of the individual and not necessarily endorsed by BKME.
Re: best backup method for millions of small files?
Hi, the best option to save millions of file under NTFS is using TSM for Fastback. 1.- you can run backups incremental for ever. 2.- you don't have backup windows. 3.- you can integrate TSM for FB with TSM 4.- you can give service very quickly in case of disaster. - Mensaje original De: Mehdi Salehi iranian.aix.supp...@gmail.com Para: ADSM-L@VM.MARIST.EDU Enviado: jueves, 30 de abril, 2009 7:48:47 Asunto: Re: best backup method for millions of small files? Richard, The total nightly delta size is about 300MB (less than 20,000 of 20k files) I am trying to test the journal to verify whether it works with incremental-by-date for image backups or not. If you have any other solution, it is welcomed. Mehdi Salehi
Re: best backup method for millions of small files?
Hi, I enabled the journal service for drive F: of a test windows-based TSM client. Here is the interesting test results: 1- total filesystem size:14GB 2- used space: 370MB (pdf, doc, exe and ... other ordinary files) 3- I enabled journal 4- snapshot image backup was successful 5- the .jbbdb file in journal directory got populated 6- I copies a directory from c: for f: 7- the size of .jbbdb file changed (means journal service is working) 8- I performed a incremental-by-date for image backup 9- NOTHING was backuped! Do you have any explanation for this? Regards, Mehdi
Re: best backup method for millions of small files?
When you 'copied' the directory, did the DATE of the directory change?? Thats probably why it didn't back anything new up.. And thats why incrbydates shouldnt be relied upon always - should always do normal incremental backups as well -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Thursday, 30 April 2009 5:30 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] best backup method for millions of small files? Hi, I enabled the journal service for drive F: of a test windows-based TSM client. Here is the interesting test results: 1- total filesystem size:14GB 2- used space: 370MB (pdf, doc, exe and ... other ordinary files) 3- I enabled journal 4- snapshot image backup was successful 5- the .jbbdb file in journal directory got populated 6- I copies a directory from c: for f: 7- the size of .jbbdb file changed (means journal service is working) 8- I performed a incremental-by-date for image backup 9- NOTHING was backuped! Do you have any explanation for this? Regards, Mehdi html body font face=arial color=#808080 size=-2img alt=Santos Logo src=http://www.santos.com/library/logo.gif; brSantos Ltd A.B.N. 80 007 550 923br Disclaimer: The information contained in this email is intended only for the use of the person(s) to whom it is addressed and may be confidential or contain privileged information. If you are not the intended recipient you are hereby notified that any perusal, use, distribution, copying or disclosure is strictly prohibited. If you have received this email in error please immediately advise us by return email and delete the email without making a copy./font font face=arial color=#008000 size=-2Please consider the environment before printing this email/font /body /html
Re: best backup method for millions of small files?
I added a new directory with 40MB of files in it. This directory is a new one that was not present when the image backup was performed. I think the most rudimentary task that is expected from an incremental backup is to understand newly added files and directories.
Re: best backup method for millions of small files?
If you want to save millions of files in the same directory. Or you change your application in order to create a different directory structure or use FastBack. - Mensaje original De: Mehdi Salehi iranian.aix.supp...@gmail.com Para: ADSM-L@VM.MARIST.EDU Enviado: jueves, 30 de abril, 2009 10:10:38 Asunto: Re: best backup method for millions of small files? I added a new directory with 40MB of files in it. This directory is a new one that was not present when the image backup was performed. I think the most rudimentary task that is expected from an incremental backup is to understand newly added files and directories.
Re: best backup method for millions of small files?
Francisco, Thanks for the hint. What is the mechanism used by FastBack that is helpful for my case? Thanks so much, Mehdi
TSM V6 Documentation
Hi All, Where to get TSM V6 Documentation. I've done with installation and did minimal configuration wizard but don't know where to access the ISC. Previous version the link was https://servername:8421/ibm/console. How about now ? BR, Martin Backup Solution Consultant @MII
Re: best backup method for millions of small files?
Fastback uses incremental for ever disk block backup and saves all info in a disk repository and you can integrate FastBack with TSM. From point of view of fastback is the same if you directory have one or one million files becasue the backup is a disk block level. When you have to restore you have two posibilities amoung several one is replace the whole volume with an instant restore and you could give service when it begins to restore or the second posibility is, for example, if your data is locate in the K: directory you can mount from backup unit K: like unit X: and move files from X: to K: Regards, Fran - Mensaje original De: Mehdi Salehi iranian.aix.supp...@gmail.com Para: ADSM-L@VM.MARIST.EDU Enviado: jueves, 30 de abril, 2009 10:15:37 Asunto: Re: best backup method for millions of small files? Francisco, Thanks for the hint. What is the mechanism used by FastBack that is helpful for my case? Thanks so much, Mehdi
Re: TSM V6 Documentation
http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp https://Admin_center_ip:9043/ibm/console/ - Mensaje original De: Sabar Martin Hasiholan Panggabean sabar.hasiho...@metrodata.co.id Para: ADSM-L@VM.MARIST.EDU Enviado: jueves, 30 de abril, 2009 10:26:06 Asunto: TSM V6 Documentation Hi All, Where to get TSM V6 Documentation. I've done with installation and did minimal configuration wizard but don't know where to access the ISC. Previous version the link was https://servername:8421/ibm/console. How about now ? BR, Martin Backup Solution Consultant @MII
SV: best backup method for millions of small files?
Hi Mehdi, FastBack don't scan each file that TSM does. FastBack do Incremental backups based on Block-Level and in that case FastBack don't care if it is million of small files or 1 large file. It will only backup the blocks that is change and always backup the entire partition. FastBack is a good software and you can run a CDP backup that is also good. But the problem with FastBack is that you can only backup from DISK-TO-DISK. And to get the data in to TSM do you need to backup the FastBack Server with TSM. Or more correct way to say it. You let TSM mount a FastBack snapshot and backup that snapshot and you will still have the slow backup to tape. But that will be in a offline/off-site mode from the server so no files will change during the backup. Another thing with FastBack, that is still missing is that, you can only restore a single file from every snapshot and not from a CDP area if you don't want to restore the entire volume to another disk first. One good thing that I think TSM should have, is that FB is recovering all Icons stubs for each file and as soon that is done the users will see his files without any problem but in the background will FB restore File A, B, C, D and so on. But if a user want to open file M, FB will priorities that file and restore that file before he continue with file E, F and H. I would like to have this function in TSM in the future. I will bring this up on the TSM Symposium in Germany in Sept. :) Because you have DIRMC in TSM today, why not have FILE_STUB_MC also? Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r Mehdi Salehi [iranian.aix.supp...@gmail.com] Skickat: den 30 april 2009 10:15 Till: ADSM-L@VM.MARIST.EDU Ämne: Re: best backup method for millions of small files? Francisco, Thanks for the hint. What is the mechanism used by FastBack that is helpful for my case? Thanks so much, Mehdi
Re: TSM V6 Documentation
Thanks .. BR, Martin -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Francisco Molero Sent: 30 April 2009 15:39 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM V6 Documentation http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp https://Admin_center_ip:9043/ibm/console/ - Mensaje original De: Sabar Martin Hasiholan Panggabean sabar.hasiho...@metrodata.co.id Para: ADSM-L@VM.MARIST.EDU Enviado: jueves, 30 de abril, 2009 10:26:06 Asunto: TSM V6 Documentation Hi All, Where to get TSM V6 Documentation. I've done with installation and did minimal configuration wizard but don't know where to access the ISC. Previous version the link was https://servername:8421/ibm/console. How about now ? BR, Martin Backup Solution Consultant @MII Internal Virus Database is out of date. Checked by AVG - www.avg.com Version: 8.5.287 / Virus Database: 270.12.3/2076 - Release Date: 04/23/09 06:30:00
Re: TDP for Exchange VSS backup destination issue
Hi Steve, I can't 100% tell from the information below... ... but your conclusions look correct... i.e. when you do a backup to BOTH... it is almost like creating two backups... ... one stored locally and bound to your VSS_DISKONLY management class and another one stored on the TSM Server and bound to your 7_DAYS management class. It sounds like the copy destination is getting set incorrectly in this case. Can you please open a PMR with IBM? The service team can examine the traces and find out if the incorrect COPYDEST is being assigned. Thanks, Del ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU wrote on 04/30/2009 01:26:26 AM: [image removed] TDP for Exchange VSS backup destination issue Steven Harris to: ADSM-L 04/30/2009 01:37 AM Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU Please respond to ADSM: Dist Stor Manager Hi All I have a corner case in the configuration of a TSM for Mail Exchange client TSM server 5.5.0.2 on AIX, Client OS Windows 2008 X64, BA Client 5.5.1.10, Exchange 2007, TDP for Mail 5.5.1 This is a CCR Cluster and I'm attempting a VSS backup, on the Inactive side of the cluster, going to both local disk and TSM. The VSS provider is the standard windows system provider, hardware snapshots are not involved. The config file has * VSS Backups VSSPOLICY * * FULL TSM 7_DAYS VSSPOLICY * * COPY TSM 4_WEEKS VSSPOLICY * * * LOCAL VSS_DISKONLY The relevant management classes are tsm: CV04q co XCH_PROD ACTIVE 7_days type=backup f=d Policy Domain Name: XCH_PROD Policy Set Name: ACTIVE Mgmt Class Name: 7_DAYS Copy Group Name: STANDARD Copy Group Type: Backup Versions Data Exists: No Limit Versions Data Deleted: No Limit Retain Extra Versions: 7 Retain Only Version: 7 Copy Mode: Modified Copy Serialization: Shared Dynamic Copy Frequency: 0 Copy Destination: VTLP11 Table of Contents (TOC) Destination: Last Update by (administrator): $$CONFIG_MANAGER$$ tsm: CV04q co XCH_PROD ACTIVE vss_diskonly type=backup f=d Policy Domain Name: XCH_PROD Policy Set Name: ACTIVE Mgmt Class Name: VSS_DISKONLY Copy Group Name: STANDARD Copy Group Type: Backup Versions Data Exists: 7 Versions Data Deleted: 7 Retain Extra Versions: 7 Retain Only Version: 7 Copy Mode: Modified Copy Serialization: Shared Static Copy Frequency: 0 Copy Destination: TAPEP4 Table of Contents (TOC) Destination: What I expect is that when a FULL backup is done with /BACKUPMETHOD=VSS and /BACKUPDEST=LOCAL the VSSPOLICY statements will be looked at from the bottom up, the retention periods in the VSS_DISKONLY copygroup will be applied and the destination ignored. For the case of /BACKUPMETHOD=VSS and /BACKUPDEST=TSM the 7_DAY class will be applied and the data sent to the VTLP11pool. These two cases seem to work correctly Now consider the case of /BACKUPMETHOD=VSS and /BACKUPDEST=BOTH. What I expect is that the local copy will be retained on disk and have the VSS_DISKONLY retentions applied. The TSM copy should have the 7_DAY retentions applied and be sent to the VTLP11 Pool. However what I observe is that while the managenment class attributions are correct the TSM copy is being sent to the destination described in the VSS_DISKONLY pool. I've been through the manual carefully, but there is nothing explicit there. I my expectation incorrect? or is the product not working correctly? Any input gladly appreciated. Thanks Steve Steven Harris, TSM Admin, Sydney Australia
Re: best backup method for millions of small files?
It isn't the backup that will kill you, it is the restore... Trust me... if you have over 1.5 Million files in a mount point, expect weeks or months to perform a full restore. Remember, just because you can put 20 million files in a mount point doesn't mean it is a good idea... discourage that at all costs. Also warn the end user that their data is, for all practical purposes, unrecoverable. Let's face it, a business couldn't endure a critical business function outage of 6 or 8 weeks. If they insist on that configuration (20M files per mount point) you'll have to protect that by something such as Image backup. If they can't endure the outage to do that, you'll need to utilize SAN disk on the back end to create a duplicate copy of the mount point and then back that up with image backup. Period... Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Wednesday, April 29, 2009 11:28 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] best backup method for millions of small files? Hi, There is an NTFS filesystem in windows with 20 millions of small files less than 20 KB each. The total size of the filesystem is less than 300GB. I have not tried incremental backup, because that would be a nightmare. Again, inc backup is not a good choice because the long restoration time is not acceptable us. I tested the snapshot image backup and satisfied with backup time. Now the problem is how to perform the incremental for this image backup. Unfortunately incremental-by-date of last image scans the whole files to filter which files must be in the backup list and would take a tremendous amount of time. This is not acceptable as well. The ideal behavior that I expect from TSM is journal based incremental backup for image which is apparently not supported by TSM 5.3. more info: -the change rate for this filesystem is about 20 thousands of files per day -TSM version is 5.3 What do you recommend for this case? Please include TSM 6.1 featues if exist. Regards, Mehdi Salehi
Re: best backup method for millions of small files?
Dwight, We tried our best to convince the application side to change the big mount point, but it is another story. It is a product, and probably one day they will be abliged to change it. What I need today is the best way to protect the volume and keep the service highly available. We do have protection layers such as a standby server and mirrored volumes using Hitachi TrueCopy to another disk subsystem. Although it is possible to dodge this problem, you can think of my question as a conceptual one. At least I understood that FastBack has a feature that TSM lacks. Who knows? perhaps we will see this in the next version of TSM, 6.2 :) Regards, Mehdi Salehi
Re: best backup method for millions of small files?
Mehdi I do not think you understand. If you are running a journal service you do not need to use incrbydate. To do what you are trying to do you need two separate backups. The first is a periodic image backup, maybe once per week or once every two weeks. The second is a normal incremental backup, which you run daily. Because of the journal service this should not take very long after the first time. Now the advantage is that when you come to restore the whole disk, TSM can restore the most recent image, and then using the incremental backup restore those files which changed after the image was taken. This is much faster than restoring each file individually from the incremental backup. To run your test, you need to run an incremental backup. This will set up the journal database ready for changes. Then run an Image backup. Next make some changes and finally run a second incremental backup. Format your test disk. Run the image restore using the gui and select the Image plus incremental directories and files option. See page 107 of the 5.3 Windows BA Client manual for details. The image will be restored and the changes applied from the subsequent incremental. Try it and let us know how it works! Regards Steve Steven Harris TSM Admin, Sydney Australia Mehdi Salehi iranian.aix.supp o...@gmail.com To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] best backup method for millions of small files? 30/04/2009 06:10 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU I added a new directory with 40MB of files in it. This directory is a new one that was not present when the image backup was performed. I think the most rudimentary task that is expected from an incremental backup is to understand newly added files and directories.
Backup set protection
Guyes, Any idea about how to protect/encrypt the backup set ? Requirement :- Need some kind of protection/authentication at the time of restoring backup set data, so that even if backup set media lost, no one can restore that data. Currently using LTO2 drives. Appreciate your inputs.. Thanks, Sachin C.
Re: Backup set protection
Simply activate client encryption. The data will be encrypted at the client before it is sent to the server; from that point forward, it will be encrypted no matter where it resides in TSM server storage / media. If you generate a backup set on portable media readable to the client, the data will be in its encrypted format. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sachin V Chaudhari1 Sent: Thursday, April 30, 2009 8:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Backup set protection Guyes, Any idea about how to protect/encrypt the backup set ? Requirement :- Need some kind of protection/authentication at the time of restoring backup set data, so that even if backup set media lost, no one can restore that data. Currently using LTO2 drives. Appreciate your inputs.. Thanks, Sachin C.
Re: best backup method for millions of small files?
Hi, None the two methods that you mean in the user's guide are suitable for my case. Image+normal incremental that you emphasized in your post means getting full image backups for example every week. For the incremental part, one file-based full backup is needed which is a nightmare for 20 millions. OK, if I accept the initial incremental backup time (that might take for days), what happens in restoration? Naturally, last image backup should be restored first and it will take A minutes. Provided that image backups are weekly, the progressive incremental backups of the week is about 6*20MB=120MB. Now imagine 120MB of 15-20K files are to be restored in filesystem with an incredibly big file address table and system should create an inode-like entry for each. If this step takes B minutes, the total restoration time would be A+B. (A+B/A) ratio is important and I will try to measure and share it with the group. Steven, your solution is excellent for ordinary filesystems with a limited number of files. But I think for millions of files, only backup/restore method that do not care how many files exist in the volume are feasible. Somehing like pure image backup (like Acronis image incremental backup) or the method that FastBack exploites. Your points are welcomed. Regards, Mehdi Salehi
Re: Tape Drive SN issue
Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04:30:41 ANR8963E Unable to find path to match the serial number defined for drive L1R3DR1 in library IBM3494A . (SESSION: 139365) 03/30/2009 04:30:41 ANR8873E The path from source TSMSERVER1 to destination L1R3DR1 (/dev/rmt13) is taken offline. (SESSION: 139365) These are 3590-E drives; the other 21 do not have this problem. The 24 drives are in one 3494 library, the library is shared by 2 TSM servers, 1 TSM server is the library manager. There are also 8 AS/400 LPARs that use the library. There have not been any problems reported by the AS/400. The problem started a few months ago with no known changes. The AIX error logs do not show any problems, the fiber switch also does not show any errors. IBM has checked the drives and they do not show any errors. These drives are on different HBA's and different FC switches, both of which have working drives. AIX has been restarted, due to other reasons, and that did not fix the problem. The drives have been reset and power cycled. We are running AIX 5.3 TSM 5.4.2.0. What have we missed, what could be looked at next? Does ANR8963E have a hidden meaning? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Tape Drive SN issue
You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04:30:41 ANR8963E Unable to find path to match the serial number defined for drive L1R3DR1 in library IBM3494A . (SESSION: 139365) 03/30/2009 04:30:41 ANR8873E The path from source TSMSERVER1 to destination L1R3DR1 (/dev/rmt13) is taken offline. (SESSION: 139365) These are 3590-E drives; the other 21 do not have this problem. The 24 drives are in one 3494 library, the library is shared by 2 TSM servers, 1 TSM server is the library manager. There are also 8 AS/400 LPARs that use the library. There have not been any problems reported by the AS/400. The problem started a few months ago with no known changes. The AIX error logs do not show any problems, the fiber switch also does not show any errors. IBM has checked the drives and they do not show any errors. These drives are on different HBA's and different FC switches, both of which have working drives. AIX has been restarted, due to other reasons, and that did not fix the problem. The drives have been reset and power cycled. We are running AIX 5.3 TSM 5.4.2.0. What have we missed, what could be looked at next? Does ANR8963E have a hidden meaning? Andy Huebner This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you. This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or
Re: best backup method for millions of small files?
You have a disk array copy of the data, is that located close or far? Have you considered a disk array snap shot also? If you perform a journaled file system backup and an image backup then you should be able to restore the image and then update the image with the file system restore. This might take a long time, I have never tried it. What failure are you trying to protect against? In our case we use the disk arrays to protect against a data center loss and a corrupt file system and a TSM file system backup to protect against the loss of a file. Our big ones are in the 10 million file range. Using a 64bit Windows server we can backup the file system in about 6 - 8 hours without journaling. We suspect we could get the time down to around 4 hours if the TSM server was not busy backing up 500 other nodes. To me the important thing is to figure out what you are protecting against with each thing you do. Also be sure and ask what the Recovery Point Objective (RPO) is. If it is less than 24 hours then array based solutions may be the best choice. Over 24 hours then TSM may be the best choice. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Thursday, April 30, 2009 9:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] best backup method for millions of small files? Hi, None the two methods that you mean in the user's guide are suitable for my case. Image+normal incremental that you emphasized in your post means getting full image backups for example every week. For the incremental part, one file-based full backup is needed which is a nightmare for 20 millions. OK, if I accept the initial incremental backup time (that might take for days), what happens in restoration? Naturally, last image backup should be restored first and it will take A minutes. Provided that image backups are weekly, the progressive incremental backups of the week is about 6*20MB=120MB. Now imagine 120MB of 15-20K files are to be restored in filesystem with an incredibly big file address table and system should create an inode-like entry for each. If this step takes B minutes, the total restoration time would be A+B. (A+B/A) ratio is important and I will try to measure and share it with the group. Steven, your solution is excellent for ordinary filesystems with a limited number of files. But I think for millions of files, only backup/restore method that do not care how many files exist in the volume are feasible. Somehing like pure image backup (like Acronis image incremental backup) or the method that FastBack exploites. Your points are welcomed. Regards, Mehdi Salehi This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Tape Drive SN issue
The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04:30:41 ANR8963E Unable to find path to match the serial number defined for drive L1R3DR1 in library IBM3494A . (SESSION: 139365) 03/30/2009 04:30:41 ANR8873E The path from source TSMSERVER1 to destination L1R3DR1 (/dev/rmt13) is taken offline. (SESSION: 139365) These are 3590-E drives; the other 21 do not have this problem. The 24 drives are in one 3494 library, the library is shared by 2 TSM servers, 1 TSM server is the library manager. There are also 8 AS/400 LPARs that use the library. There have not been any problems reported by the AS/400. The problem started a few months ago with no known changes. The AIX error logs do not show any problems, the fiber switch also does not show any errors. IBM has checked the drives and they do not show any errors. These drives are on different HBA's and different FC switches, both of which have working drives. AIX has been restarted, due to other reasons, and that did not fix the problem. The drives have been reset and power cycled. We are running AIX 5.3 TSM 5.4.2.0. What have we missed, what could be looked at next? Does ANR8963E have a hidden meaning? Andy Huebner This e-mail (including any attachments) is confidential and may be legally
Re: Tape Drive SN issue
Andy, Do you have TSM SAN Discovery turned on? If you do, you can perform q SAN and look for the drive serial number in the output of q san. If you have ran cfgmgr after you changed GBIC, TSM SAN Discovery function should be able to get the new path for these drives using serial number to match the new san map. If you have TSM SAN Discovery turned on AND you have used cfgmgr AND you still have the ANR8963E, you should report this problem. We can get a TSM server trace when TSM tries to mount the tape to see what is going on. The trace for TSM: trace enable PVR MMS NA Regards, Jo Lay Tivoli Storage Products, IBM Software Group jo...@us.ibm.com Phone: 408-997-7999 Huebner,Andy,FOR T WORTH,IT andy.hueb...@alc To ONLABS.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist Re: [ADSM-L] Tape Drive SN issue .EDU 04/30/2009 08:21 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To:
Re: Tape Drive SN issue
We had to turn off SAN discovery due to other issues. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jo Lay Sent: Thursday, April 30, 2009 10:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Andy, Do you have TSM SAN Discovery turned on? If you do, you can perform q SAN and look for the drive serial number in the output of q san. If you have ran cfgmgr after you changed GBIC, TSM SAN Discovery function should be able to get the new path for these drives using serial number to match the new san map. If you have TSM SAN Discovery turned on AND you have used cfgmgr AND you still have the ANR8963E, you should report this problem. We can get a TSM server trace when TSM tries to mount the tape to see what is going on. The trace for TSM: trace enable PVR MMS NA Regards, Jo Lay Tivoli Storage Products, IBM Software Group jo...@us.ibm.com Phone: 408-997-7999 Huebner,Andy,FOR T WORTH,IT andy.hueb...@alc To ONLABS.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist Re: [ADSM-L] Tape Drive SN issue .EDU 04/30/2009 08:21 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have
Re: Backup set protection
HI Thx for your inputs. But if I enable client encryption for taking flat file backup, then how will I restore the backup set data. At the time of backup set restoration will it ask me to put the same passport which I used it for flatfile backup. As I know it will prompt us to enter the password for normal restore process, but I am not sure whether it will for backup set restoration if encryption is enable for file system backup.? Sachin C. Dwight Cook coo...@cox.net Sent by: ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager cc ads...@vm.marist .EDU Subject Re: [ADSM-L] Backup set protection 30/04/2009 08:03 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU Simply activate client encryption. The data will be encrypted at the client before it is sent to the server; from that point forward, it will be encrypted no matter where it resides in TSM server storage / media. If you generate a backup set on portable media readable to the client, the data will be in its encrypted format. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sachin V Chaudhari1 Sent: Thursday, April 30, 2009 8:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Backup set protection Guyes, Any idea about how to protect/encrypt the backup set ? Requirement :- Need some kind of protection/authentication at the time of restoring backup set data, so that even if backup set media lost, no one can restore that data. Currently using LTO2 drives. Appreciate your inputs.. Thanks, Sachin C.
Re: Tape Drive SN issue
Ok, you might want to resolve the SAN Discovery issue on your machine. This will save you time in the long run. BTW, what is the issue for SAN discovery? Regards, Jo Lay Tivoli Storage Products, IBM Software Group jo...@us.ibm.com Huebner,Andy,FOR T WORTH,IT andy.hueb...@alc To ONLABS.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist Re: [ADSM-L] Tape Drive SN issue .EDU 04/30/2009 08:49 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU We had to turn off SAN discovery due to other issues. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jo Lay Sent: Thursday, April 30, 2009 10:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Andy, Do you have TSM SAN Discovery turned on? If you do, you can perform q SAN and look for the drive serial number in the output of q san. If you have ran cfgmgr after you changed GBIC, TSM SAN Discovery function should be able to get the new path for these drives using serial number to match the new san map. If you have TSM SAN Discovery turned on AND you have used cfgmgr AND you still have the ANR8963E, you should report this problem. We can get a TSM server trace when TSM tries to mount the tape to see what is going on. The trace for TSM: trace enable PVR MMS NA Regards, Jo Lay Tivoli Storage Products, IBM Software Group jo...@us.ibm.com Phone: 408-997-7999 Huebner,Andy,FOR T WORTH,IT andy.hueb...@alc To ONLABS.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist Re: [ADSM-L] Tape Drive SN issue .EDU 04/30/2009 08:21 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight
Re: TSM 6.1 - can I do a X server platform database restore?
Joerg (and all), I don't see a response from TSM development in this chain so I'm not sure if it had been responded to or not... If it had and I missed it - I apologize for any duplication or rehashing of previously covered information... With TSM V6.1, some of the challenges associated with restoring a server database across platforms have been eliminated or mitigated. That being said, there are still some embedded data structures that TSM stores that may have architecture, platform, or endianess issues if a database was restored to a different architecture and operating system then it was originally running on... From the discussion in the responses to this post, it is correct that much of the concern or issue with this is the device support and in particular the representation of device specific attributes such as positioning information of data on volumes. Thanks, Colin - Colin Dawson TSM Server Development col...@us.ibm.com From: Don France dfrance-...@att.net To: ADSM-L@VM.MARIST.EDU Date: 04/29/2009 08:17 PM Subject:Re: [ADSM-L] TSM 6.1 - can I do a X server platform database restore? Clearly, this is not exactly the case; LAN-free data is written to tape in a format that *any* hosting TSM server can read/restore/migrate/etc. It's the DATABASE data (and metadata) that is stored in formats consistent with the hosting TSM server's OS-platform --- one issue has been the bigindian-littleindian issue, mostly (though there are some other issues, too -- such as LBA's and other such OS-filesystem-dependent things). There were rumors that some x86-based OS's might be able to handle some items in a x-platform kinda way, but it's not been reported the degree of success. -Don -- Original message from Paul Zarnowski p...@cornell.edu: -- Tapes are written in different formats on different platforms, so the answer to your question is no. You would have to export all of the data from Windows and import to AIX, not just the database. No, I'm not from development, but I did sleep at a Holiday Inn Express last night! ..Paul At 05:41 PM 3/11/2009, Joerg Pohlmann wrote: Could someone from development please comment - since the database for TSM 6.1 is DB2, can I move from a TSM server on for example, Windows to a TSM server on for example, AIX by restoring the database and then updating any tape device names in the path definitions? Joerg Pohlmann 250-245-9863 -- Paul ZarnowskiPh: 607-255-4757 Manager, Storage Services Fx: 607-255-8521 719 Rhodes Hall, Ithaca, NY 14853-3801Em: p...@cornell.edu
Re: Backup set protection
I have not personally run with encrypted data and restoring from a backup set but knowing in all other situations if the data is encrypted and the encryption key isn't present it will prompt for it, I would imagine it would function the same way here. Validate through testing though... Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sachin V Chaudhari1 Sent: Thursday, April 30, 2009 10:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backup set protection HI Thx for your inputs. But if I enable client encryption for taking flat file backup, then how will I restore the backup set data. At the time of backup set restoration will it ask me to put the same passport which I used it for flatfile backup. As I know it will prompt us to enter the password for normal restore process, but I am not sure whether it will for backup set restoration if encryption is enable for file system backup.? Sachin C. Dwight Cook coo...@cox.net Sent by: ADSM:To Dist Stor ADSM-L@VM.MARIST.EDU Manager cc ads...@vm.marist .EDU Subject Re: [ADSM-L] Backup set protection 30/04/2009 08:03 PM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU Simply activate client encryption. The data will be encrypted at the client before it is sent to the server; from that point forward, it will be encrypted no matter where it resides in TSM server storage / media. If you generate a backup set on portable media readable to the client, the data will be in its encrypted format. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Sachin V Chaudhari1 Sent: Thursday, April 30, 2009 8:36 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Backup set protection Guyes, Any idea about how to protect/encrypt the backup set ? Requirement :- Need some kind of protection/authentication at the time of restoring backup set data, so that even if backup set media lost, no one can restore that data. Currently using LTO2 drives. Appreciate your inputs.. Thanks, Sachin C.
Re: SV: VTL and Dedup ( TS7569G)
Does anyone use TS7569G with TSM 5.4 running on AIX 5.2. This devices works fine on HPUX 11 v3 with TSM 5.5 by emulating ATL P300. But we are trying to test on AIX server the cfgmgr created all the devices files for the tape drives but not able to get the device file for media changer. We tried from smitty using Tivoli Storage Manager Devices and still not able to define it TSM Define Methods didnt/couldnt define any devices Thanks Pawlos -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Thursday, March 19, 2009 10:34 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: VTL and Dedup ( TS7569G) As many say your mileage may vary You can positively impact the Dedupe factor by ... 1) No Client Side Compressions (Compressed files always have unique Sig) 2) No Client Side Encryption (TSM or OS) - Encrypted Data is always unique like compressed data. 3) If you have more than one VTL each with its own repository - do your best to keep like data together (i.e. all Unix / Oracle data to one VTL, all Windows based Data on 2nd VTL etc If would have 200+ Windows OS's you'll see some Deduping... 4) Of course the Dedup for full DB backups gets much higher (21 Versions of Fulls we avg 15:1) Our challenge has become I/O not space. 5) According to our VTL vendor the RMAN Files per set option should be @ 1(Files perset allows Oracle to mix data backup streams there by creating unique data... Good luck on your venture looks like the TS7569G (IBM Protectier?) same we are using... The most challenging aspect of any VTL is capacity planning assuming you have solid retention policies that are followed ... Regards Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Christian Svensson Sent: Thursday, March 19, 2009 7:42 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: VTL and Dedup ( TS7569G) Hi Martin, The 1st Backup will probably don't do any major save for you. It always depend on what kind of data you backup. What we normally see is saving on Archive Data and TDP Data. Everything else is most of the time unique data and you will not see any saving. Dedup is a major saving for other backup software such Legato and NBU not for TSM because you are using Incremental forever. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r Sabar Martin Hasiholan Panggabean [sabar.hasiho...@metrodata.co.id] Skickat: den 19 mars 2009 13:09 Till: ADSM-L@VM.MARIST.EDU Ämne: VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: Tape Drive SN issue
Here are some things to do . . . Check that the tape drive is logged into the switch port, and you see the wwn on the switch port. Check the tape drive that it sees the san - usually a light indicating a connection to the san by the cable port (3592's have this, not sure about 3590E's) Check that the wwn on the switch port is the same as was there previously (ie: the wwn didn't change) Check that the zone is correct (you didn't change it . . .but . . .). Check the wwn on the AIX RMT device matches what you see on the switch port (lsattr -El rmtX) (do this for all RMT paths to the tape drive) Check what atape thinks about the paths (tapeutil -f /dev/rmtX path) Check that the tsm tape device (wwm, s/n) matches the AIX rmt devices, which matches the actual tape device. Try the cable in a different drive that you know works. Try the drive with a cable from a working drive. Stick a tape in the drive and try and tar some data onto it (ie: bypass TSM). Try bypass cable straight from the tape drive direct to another server with a open hba, and see if it drive comes in and is usable (tar stuff onto a tape). Rick T Huebner,Andy,FOR T WORTH,IT andy.hueb...@alc To ONLABS.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist Re: Tape Drive SN issue .EDU 04/30/2009 10:40 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04:30:41 ANR8963E Unable to find path to match the serial number defined for drive L1R3DR1 in library IBM3494A . (SESSION: 139365) 03/30/2009 04:30:41 ANR8873E The path from source TSMSERVER1 to destination L1R3DR1 (/dev/rmt13) is taken offline. (SESSION: 139365) These are 3590-E drives; the other 21 do not have this problem. The 24 drives are in one 3494 library, the library is shared by 2 TSM servers, 1 TSM server is the library manager. There are also 8 AS/400 LPARs that use the library. There have not been any problems reported by the AS/400. The problem started a few months ago with no known changes. The AIX error logs do not show any problems, the fiber switch also does not show any errors. IBM has checked the drives and they do not show any errors. These drives are on different HBA's and different FC switches, both of which have working drives. AIX has been restarted, due to other reasons, and that did not fix the problem. The drives have been reset and power cycled. We are running AIX 5.3 TSM 5.4.2.0. What have we missed, what could be looked at next? Does ANR8963E have a hidden meaning? Andy Huebner This e-mail (including any
Re: Tape Drive SN issue
Hi, Andy. Going back to simple, in addition to deleting the paths, did you also delete and redefine your drives? I'm just double-checking because I don't see it explicitly mentioned in the thread and it seems to me that the only place TSM knows about the S/N is in the drive definition. Alex Paschal Storage Solutions Engineer MSI Systems Integrators (503) 943-6919 - Office Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04:30:41 ANR8963E Unable to find path to match the serial number defined for drive L1R3DR1 in library IBM3494A . (SESSION: 139365) 03/30/2009 04:30:41 ANR8873E The path from source TSMSERVER1 to destination L1R3DR1 (/dev/rmt13) is taken offline. (SESSION: 139365) These are 3590-E drives; the other 21 do not have this problem. The 24 drives are in one 3494 library, the library is shared by 2 TSM servers, 1 TSM server is the library manager. There are also 8 AS/400 LPARs that use the library. There have not been
Re: Tape Drive SN issue
You can issue a show library command from a TSM prompt. For detailed info that is not always represented in TSM. I've used this to see if tapes are stuck in older DLT drives. But it shows WWN and serial number. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Thursday, April 30, 2009 11:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Tape Drive SN issue Hi, Andy. Going back to simple, in addition to deleting the paths, did you also delete and redefine your drives? I'm just double-checking because I don't see it explicitly mentioned in the thread and it seems to me that the only place TSM knows about the S/N is in the drive definition. Alex Paschal Storage Solutions Engineer MSI Systems Integrators (503) 943-6919 - Office Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04:30:41 ANR8963E Unable to find path to match the serial number defined for drive L1R3DR1 in library IBM3494A . (SESSION:
Re: Tape Drive SN issue
OH, are only 3590's having problems??? We did a switch upgrade and the short story is that the switches we migrated to would not function with 3590's / 3590's would not function with the switch... I can't remember all the specifics currently. The switch upgrade was more critical than the 3590 drives so we moved back to the old switch, retrieved all 3590 data, migrated it to 3592 data and then trashed the 3590 drives and all 3590 media. Is this your issue??? Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ochs, Duane Sent: Thursday, April 30, 2009 12:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You can issue a show library command from a TSM prompt. For detailed info that is not always represented in TSM. I've used this to see if tapes are stuck in older DLT drives. But it shows WWN and serial number. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Thursday, April 30, 2009 11:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: Tape Drive SN issue Hi, Andy. Going back to simple, in addition to deleting the paths, did you also delete and redefine your drives? I'm just double-checking because I don't see it explicitly mentioned in the thread and it seems to me that the only place TSM knows about the S/N is in the drive definition. Alex Paschal Storage Solutions Engineer MSI Systems Integrators (503) 943-6919 - Office Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO
Re: SV: VTL and Dedup ( TS7569G)
What tape drive are you emulating? Do you have a current version of the atape driver on your AIX server? TSM server on AIX uses the atape driver rather than the TSM drivers. David Ehresman Pawlos Gizaw pawlos.gi...@sanofi-aventis.com 4/30/2009 12:39 PM Does anyone use TS7569G with TSM 5.4 running on AIX 5.2. This devices works fine on HPUX 11 v3 with TSM 5.5 by emulating ATL P300. But we are trying to test on AIX server the cfgmgr created all the devices files for the tape drives but not able to get the device file for media changer. We tried from smitty using Tivoli Storage Manager Devices and still not able to define it TSM Define Methods didnt/couldnt define any devices Thanks Pawlos -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Thursday, March 19, 2009 10:34 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: VTL and Dedup ( TS7569G) As many say your mileage may vary You can positively impact the Dedupe factor by ... 1) No Client Side Compressions (Compressed files always have unique Sig) 2) No Client Side Encryption (TSM or OS) - Encrypted Data is always unique like compressed data. 3) If you have more than one VTL each with its own repository - do your best to keep like data together (i.e. all Unix / Oracle data to one VTL, all Windows based Data on 2nd VTL etc If would have 200+ Windows OS's you'll see some Deduping... 4) Of course the Dedup for full DB backups gets much higher (21 Versions of Fulls we avg 15:1) Our challenge has become I/O not space. 5) According to our VTL vendor the RMAN Files per set option should be @ 1(Files perset allows Oracle to mix data backup streams there by creating unique data... Good luck on your venture looks like the TS7569G (IBM Protectier?) same we are using... The most challenging aspect of any VTL is capacity planning assuming you have solid retention policies that are followed ... Regards Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Christian Svensson Sent: Thursday, March 19, 2009 7:42 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: VTL and Dedup ( TS7569G) Hi Martin, The 1st Backup will probably don't do any major save for you. It always depend on what kind of data you backup. What we normally see is saving on Archive Data and TDP Data. Everything else is most of the time unique data and you will not see any saving. Dedup is a major saving for other backup software such Legato and NBU not for TSM because you are using Incremental forever. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r Sabar Martin Hasiholan Panggabean [sabar.hasiho...@metrodata.co.id] Skickat: den 19 mars 2009 13:09 Till: ADSM-L@VM.MARIST.EDU Ämne: VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: SV: VTL and Dedup ( TS7569G)
It will depend on the Protectier version installed on the Gateway appliance, v2.1 = uses a TSM Smitty Sudo Device for the Changer and LTO ATAPE friendly devices for the drives. (so you still have to use smitty to scan for the changer device down the FCS adapter) v2.2.1 supports a Atape based medium changer (robot) and LTO tape devices. Your IBM rep should know this Hope this helps Regards, Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Pawlos Gizaw Sent: Thursday, April 30, 2009 11:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: VTL and Dedup ( TS7569G) Does anyone use TS7569G with TSM 5.4 running on AIX 5.2. This devices works fine on HPUX 11 v3 with TSM 5.5 by emulating ATL P300. But we are trying to test on AIX server the cfgmgr created all the devices files for the tape drives but not able to get the device file for media changer. We tried from smitty using Tivoli Storage Manager Devices and still not able to define it TSM Define Methods didnt/couldnt define any devices Thanks Pawlos -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Thursday, March 19, 2009 10:34 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: VTL and Dedup ( TS7569G) As many say your mileage may vary You can positively impact the Dedupe factor by ... 1) No Client Side Compressions (Compressed files always have unique Sig) 2) No Client Side Encryption (TSM or OS) - Encrypted Data is always unique like compressed data. 3) If you have more than one VTL each with its own repository - do your best to keep like data together (i.e. all Unix / Oracle data to one VTL, all Windows based Data on 2nd VTL etc If would have 200+ Windows OS's you'll see some Deduping... 4) Of course the Dedup for full DB backups gets much higher (21 Versions of Fulls we avg 15:1) Our challenge has become I/O not space. 5) According to our VTL vendor the RMAN Files per set option should be @ 1(Files perset allows Oracle to mix data backup streams there by creating unique data... Good luck on your venture looks like the TS7569G (IBM Protectier?) same we are using... The most challenging aspect of any VTL is capacity planning assuming you have solid retention policies that are followed ... Regards Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Christian Svensson Sent: Thursday, March 19, 2009 7:42 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: VTL and Dedup ( TS7569G) Hi Martin, The 1st Backup will probably don't do any major save for you. It always depend on what kind of data you backup. What we normally see is saving on Archive Data and TDP Data. Everything else is most of the time unique data and you will not see any saving. Dedup is a major saving for other backup software such Legato and NBU not for TSM because you are using Incremental forever. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r Sabar Martin Hasiholan Panggabean [sabar.hasiho...@metrodata.co.id] Skickat: den 19 mars 2009 13:09 Till: ADSM-L@VM.MARIST.EDU Ämne: VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
backup performance on intel server
Hi, I have a non-TSM related question, but I think it is the same for all backup software. We need to backup 28 TB for a cutsomer with daily changes of appr 8 TB. If you take a backup window of 8 hr, this is 1 TB/hour. This is also 280 MB/s so 3,5 LTO4 tape streamers (if you take 80MB/s per tape streamer). I can not use SAN backup, so all data has to come in over the network, so I need at least 3 x 1 GB network connections. What kind of intel box running windows can handle this workload? Is the PCI bus of a normal x86 server enough or do I need some high end x86 hardware? Stef PS: the backup software Backup Exec from Symantec
Re: Tape Drive SN issue
With SAN discovery on our Clariion disks become inaccessible at a random time. Since we turned on SAN discovery to fix the tape drive thing and it did not, we turned it back off. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jo Lay Sent: Thursday, April 30, 2009 11:07 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Ok, you might want to resolve the SAN Discovery issue on your machine. This will save you time in the long run. BTW, what is the issue for SAN discovery? Regards, Jo Lay Tivoli Storage Products, IBM Software Group jo...@us.ibm.com Huebner,Andy,FOR T WORTH,IT andy.hueb...@alc To ONLABS.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist Re: [ADSM-L] Tape Drive SN issue .EDU 04/30/2009 08:49 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU We had to turn off SAN discovery due to other issues. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Jo Lay Sent: Thursday, April 30, 2009 10:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Andy, Do you have TSM SAN Discovery turned on? If you do, you can perform q SAN and look for the drive serial number in the output of q san. If you have ran cfgmgr after you changed GBIC, TSM SAN Discovery function should be able to get the new path for these drives using serial number to match the new san map. If you have TSM SAN Discovery turned on AND you have used cfgmgr AND you still have the ANR8963E, you should report this problem. We can get a TSM server trace when TSM tries to mount the tape to see what is going on. The trace for TSM: trace enable PVR MMS NA Regards, Jo Lay Tivoli Storage Products, IBM Software Group jo...@us.ibm.com Phone: 408-997-7999 Huebner,Andy,FOR T WORTH,IT andy.hueb...@alc To ONLABS.COM ADSM-L@VM.MARIST.EDU Sent by: ADSM:cc Dist Stor Manager Subject ads...@vm.marist Re: [ADSM-L] Tape Drive SN issue .EDU 04/30/2009 08:21 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run
Re: Tape Drive SN issue
IBM had me delete and recreate the drives in TSM. When we recreated the paths TSM was unable to contact the drive. AIX did not report an error. Since I am down to trying things that won't work I reset the port and the define path worked. I will know the results in the morning. Also, someone asked about the switches. They are the same switches we have been using since 2002. No changes there. The problem drives are on two switches. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Alex Paschal Sent: Thursday, April 30, 2009 11:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Hi, Andy. Going back to simple, in addition to deleting the paths, did you also delete and redefine your drives? I'm just double-checking because I don't see it explicitly mentioned in the thread and it seems to me that the only place TSM knows about the S/N is in the drive definition. Alex Paschal Storage Solutions Engineer MSI Systems Integrators (503) 943-6919 - Office Your Business. Better. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:22 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The drives were verified in AIX after GBic change. Since there was not a port change there was no effect on AIX. The library is aware of all of the drives. I think I mentioned earlier that the AS/400s that share the library have reported no problems with these drives. Thanks for the suggestions, we have looked at so many things it is hard to recall them all, but we may have missed something simple. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 9:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path
Re: backup performance on intel server
1 Gb Ethernet is about 100Mb/sec LTO4 is about 120Mb/sec + compression A good SCSI or FC drive is good for about 100Mb/sec Assuming you can stream 3 threads across the Ethernet, you will not be able to keep the 3 LTO4 drives busy because of the network. The faster tape drives were not intended to take data from the Ethernet. Assuming some sort of RAID and careful selection of file system backup times the disk can keep up with the network if the read is sequential and the backup software can find the data fast enough. Make sure you have multiple busses. Basically I would look for a PCI-Express system with enough slots for the Ethernet and RAID or HBA controllers. I would be stressed about making the window and since you are using a traditional backup solution the fulls will be tough. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Stef Coene Sent: Thursday, April 30, 2009 1:04 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] backup performance on intel server Hi, I have a non-TSM related question, but I think it is the same for all backup software. We need to backup 28 TB for a cutsomer with daily changes of appr 8 TB. If you take a backup window of 8 hr, this is 1 TB/hour. This is also 280 MB/s so 3,5 LTO4 tape streamers (if you take 80MB/s per tape streamer). I can not use SAN backup, so all data has to come in over the network, so I need at least 3 x 1 GB network connections. What kind of intel box running windows can handle this workload? Is the PCI bus of a normal x86 server enough or do I need some high end x86 hardware? Stef PS: the backup software Backup Exec from Symantec This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: Tape Drive SN issue
I am not aware of this problem. Are you putting disk and tape under the same HBA? Regards, Jo Lay Tivoli Storage Products, IBM Software Group jo...@us.ibm.com
Re: Tape Drive SN issue
If you use tapeutil to do an inquiry on a tape drive, the serial number should be recognizable in the output. You can compare this with the results from a lscfg -vl rmt1 or lsattr -El rmt1. I've seen the ODM reporting serial numbers that don't match what the tape drive reports. IIRC the 3590s talked FC-AL, and they negotiate with each other to see who is going to get a particular ALPA. If you move cables from one switch to the other, you can cause all of them to renegotiate, and everyone moves around. The newer drives can do fabric mode, and don't need to LIP as often. [RC] -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Dwight Cook Sent: Thursday, April 30, 2009 7:54 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue You are aware that under AIX if any WWN in the path of a drive changes, then that constitutes an entirely new device as seen by AIX. If you replaced GBics, it possibly could have caused the tape drive to take on a new rmt as seen under AIX unless you performed a rmdev -dl rmt_ on the existing device found down that GBic and then ran cfgmgr afterwards so it would in fact come back as the same device. I take it that you have run cfgmgr and checked to see that there are no new/unexpected rmt's present... if not, please do that and run lscfg -vpl rmt__ against any new rmt's you see to determine if they are the drives that you are having issues with (SR# cross ck) Also from a library point of view... from your AIX host system you performed an mtlib -l/dev/lmcp__ -qD to ck that the library does in fact still see the drives. Dwight -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 9:40 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue Update: We turned on TapeAlertMSG - no new messages We have changed the GBics on the switches - No change We had IBM do a health check on the drives - Last abnormal error was months earlier on one drive. The other two were clean. We have updated the firmware to the same version as a drive not having the issue. The troubled drives were slightly lower version - No change We updated the drives to the current firmware - No change We swapped cables with one of the working drives - No change We verified the cabling on all drives - It was done right We have opened a case - Waiting for call back. We have considered kicking it - Might dent it. We have run out of ideas - Heads are being scratched. The question is what did we miss? Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 11:18 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue The error occurs when TSM attempts to mount a tape. We have had no problems deleting and defining these paths, which I should have included in the first message. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kelly Lipp Sent: Monday, March 30, 2009 10:53 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Tape Drive SN issue I assume these message occur when you try to define the path? Kelly Lipp CTO STORServer, Inc. 485-B Elkton Drive Colorado Springs, CO 80907 719-266-8777 x7105 www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Monday, March 30, 2009 9:50 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Tape Drive SN issue We have a three drives that generate these messages and we are unable to use the drives because the path will not stay on-line. We have not been able to find a solution to this problem. 03/30/2009 04:30:41 ANR8963E Unable to find path to match the serial number defined for drive L1R3DR1 in library IBM3494A . (SESSION: 139365) 03/30/2009 04:30:41 ANR8873E The path from source TSMSERVER1 to destination L1R3DR1 (/dev/rmt13) is taken offline. (SESSION: 139365) These are 3590-E drives; the other 21 do not have this problem. The 24 drives are in one 3494 library, the library is shared by 2 TSM servers, 1 TSM server is the library manager. There are also 8 AS/400 LPARs that use the library. There have not been any problems reported by the AS/400. The problem started a few months ago with no known changes. The AIX error logs do not show any problems, the fiber switch also does not show any errors. IBM has checked the drives and they do not show any errors. These drives are on different HBA's and different FC switches, both of which have working drives. AIX has been restarted, due to other reasons, and that did not fix the problem. The drives have been reset and power cycled. We are running AIX 5.3 TSM 5.4.2.0. What have we missed, what
Re: backup performance on intel server
On Thursday 30 April 2009, Huebner,Andy,FORT WORTH,IT wrote: 1 Gb Ethernet is about 100Mb/sec Maybe nick picking, but for me: 100Mb = 100 Mbit, 100MB is 100 MByte. LTO4 is about 120Mb/sec + compression Mhh, I was counting 80 MB/s up to 160 MB/s with compression ratio 2:1. A good SCSI or FC drive is good for about 100Mb/sec The disk storage fot the client is an n Series from IBM (16 TB), but also 12 TB local (scsi attached) disks. Assuming you can stream 3 threads across the Ethernet, you will not be able to keep the 3 LTO4 drives busy because of the network. The faster tape drives were not intended to take data from the Ethernet. Assuming some sort of RAID and careful selection of file system backup times the disk can keep up with the network if the read is sequential and the backup software can find the data fast enough. Make sure you have multiple busses. Basically I would look for a PCI-Express system with enough slots for the Ethernet and RAID or HBA controllers. I would be stressed about making the window and since you are using a traditional backup solution the fulls will be tough. The customer was counting on a 24hr or even a 48hr backup window on saterday and sunday. And for the stress, this is solution is pushed from the head quarters in America to the customer in Belgium. They wanted a DS48 from IBM + TSM Thanx for the info. Stef
Re: SV: VTL and Dedup ( TS7569G)
I was trying to emulating LTO2. The atape driver was little old it is Atape.driver 8.4.8.0 works fine with 3584 and lot of lto2 tape drives on this AIX server. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of David E Ehresman Sent: Thursday, April 30, 2009 1:43 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: VTL and Dedup ( TS7569G) What tape drive are you emulating? Do you have a current version of the atape driver on your AIX server? TSM server on AIX uses the atape driver rather than the TSM drivers. David Ehresman Pawlos Gizaw pawlos.gi...@sanofi-aventis.com 4/30/2009 12:39 PM Does anyone use TS7569G with TSM 5.4 running on AIX 5.2. This devices works fine on HPUX 11 v3 with TSM 5.5 by emulating ATL P300. But we are trying to test on AIX server the cfgmgr created all the devices files for the tape drives but not able to get the device file for media changer. We tried from smitty using Tivoli Storage Manager Devices and still not able to define it TSM Define Methods didnt/couldnt define any devices Thanks Pawlos -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Thursday, March 19, 2009 10:34 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] SV: VTL and Dedup ( TS7569G) As many say your mileage may vary You can positively impact the Dedupe factor by ... 1) No Client Side Compressions (Compressed files always have unique Sig) 2) No Client Side Encryption (TSM or OS) - Encrypted Data is always unique like compressed data. 3) If you have more than one VTL each with its own repository - do your best to keep like data together (i.e. all Unix / Oracle data to one VTL, all Windows based Data on 2nd VTL etc If would have 200+ Windows OS's you'll see some Deduping... 4) Of course the Dedup for full DB backups gets much higher (21 Versions of Fulls we avg 15:1) Our challenge has become I/O not space. 5) According to our VTL vendor the RMAN Files per set option should be @ 1(Files perset allows Oracle to mix data backup streams there by creating unique data... Good luck on your venture looks like the TS7569G (IBM Protectier?) same we are using... The most challenging aspect of any VTL is capacity planning assuming you have solid retention policies that are followed ... Regards Charles -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Christian Svensson Sent: Thursday, March 19, 2009 7:42 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] SV: VTL and Dedup ( TS7569G) Hi Martin, The 1st Backup will probably don't do any major save for you. It always depend on what kind of data you backup. What we normally see is saving on Archive Data and TDP Data. Everything else is most of the time unique data and you will not see any saving. Dedup is a major saving for other backup software such Legato and NBU not for TSM because you are using Incremental forever. Best Regards Christian Svensson Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Skype: cristie.christian.svensson Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] f#246;r Sabar Martin Hasiholan Panggabean [sabar.hasiho...@metrodata.co.id] Skickat: den 19 mars 2009 13:09 Till: ADSM-L@VM.MARIST.EDU Ämne: VTL and Dedup ( TS7569G) Hi, Does anyone here has been implementing or know how Dedup works in TSM using TS7569G ? Let say I have 100 TB of data and backup to this VTL. On the 1st attempt of backup / full backup, will this data size decrease on the VTL BR, Martin P This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.
Re: best backup method for millions of small files?
What options are there when journaling runs out of memory on a 32 bit Windows server? I have about 10 million files on one server that the journal engine runs out of memory. With memory efficient disk cache method and resource utilization 5, its runs out of memory, resource utilization of 4 runs too long. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: best backup method for millions of small files? You have a disk array copy of the data, is that located close or far? Have you considered a disk array snap shot also? If you perform a journaled file system backup and an image backup then you should be able to restore the image and then update the image with the file system restore. This might take a long time, I have never tried it. What failure are you trying to protect against? In our case we use the disk arrays to protect against a data center loss and a corrupt file system and a TSM file system backup to protect against the loss of a file. Our big ones are in the 10 million file range. Using a 64bit Windows server we can backup the file system in about 6 - 8 hours without journaling. We suspect we could get the time down to around 4 hours if the TSM server was not busy backing up 500 other nodes. To me the important thing is to figure out what you are protecting against with each thing you do. Also be sure and ask what the Recovery Point Objective (RPO) is. If it is less than 24 hours then array based solutions may be the best choice. Over 24 hours then TSM may be the best choice. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Thursday, April 30, 2009 9:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] best backup method for millions of small files? Hi, None the two methods that you mean in the user's guide are suitable for my case. Image+normal incremental that you emphasized in your post means getting full image backups for example every week. For the incremental part, one file-based full backup is needed which is a nightmare for 20 millions. OK, if I accept the initial incremental backup time (that might take for days), what happens in restoration? Naturally, last image backup should be restored first and it will take A minutes. Provided that image backups are weekly, the progressive incremental backups of the week is about 6*20MB=120MB. Now imagine 120MB of 15-20K files are to be restored in filesystem with an incredibly big file address table and system should create an inode-like entry for each. If this step takes B minutes, the total restoration time would be A+B. (A+B/A) ratio is important and I will try to measure and share it with the group. Steven, your solution is excellent for ordinary filesystems with a limited number of files. But I think for millions of files, only backup/restore method that do not care how many files exist in the volume are feasible. Somehing like pure image backup (like Acronis image incremental backup) or the method that FastBack exploites. Your points are welcomed. Regards, Mehdi Salehi This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: best backup method for millions of small files?
Hi Norman Your post worries me, as I'm just implementing an email archive solution that will depend on windows journalling to back up some huge repositories. The particular product fills up containers that once filled never change, so the change rate will be low there, but there are also index files that will change often. Have you determined whether the memory issue is related to number of files or number of changes? Regards Steve Steven Harris TSM Admin, Sydney Australia Gee, Norman norman@lc.ca .GOV To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] best backup method for millions of small files? 01/05/2009 07:12 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU What options are there when journaling runs out of memory on a 32 bit Windows server? I have about 10 million files on one server that the journal engine runs out of memory. With memory efficient disk cache method and resource utilization 5, its runs out of memory, resource utilization of 4 runs too long. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: best backup method for millions of small files? You have a disk array copy of the data, is that located close or far? Have you considered a disk array snap shot also? If you perform a journaled file system backup and an image backup then you should be able to restore the image and then update the image with the file system restore. This might take a long time, I have never tried it. What failure are you trying to protect against? In our case we use the disk arrays to protect against a data center loss and a corrupt file system and a TSM file system backup to protect against the loss of a file. Our big ones are in the 10 million file range. Using a 64bit Windows server we can backup the file system in about 6 - 8 hours without journaling. We suspect we could get the time down to around 4 hours if the TSM server was not busy backing up 500 other nodes. To me the important thing is to figure out what you are protecting against with each thing you do. Also be sure and ask what the Recovery Point Objective (RPO) is. If it is less than 24 hours then array based solutions may be the best choice. Over 24 hours then TSM may be the best choice. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Thursday, April 30, 2009 9:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] best backup method for millions of small files? Hi, None the two methods that you mean in the user's guide are suitable for my case. Image+normal incremental that you emphasized in your post means getting full image backups for example every week. For the incremental part, one file-based full backup is needed which is a nightmare for 20 millions. OK, if I accept the initial incremental backup time (that might take for days), what happens in restoration? Naturally, last image backup should be restored first and it will take A minutes. Provided that image backups are weekly, the progressive incremental backups of the week is about 6*20MB=120MB. Now imagine 120MB of 15-20K files are to be restored in filesystem with an incredibly big file address table and system should create an inode-like entry for each. If this step takes B minutes, the total restoration time would be A+B. (A+B/A) ratio is important and I will try to measure and share it with the group. Steven, your solution is excellent for ordinary filesystems with a limited number of files. But I think for millions of files, only backup/restore method that do not care how many files exist in the volume are feasible. Somehing like pure image backup (like Acronis image incremental backup) or the method that FastBack exploites. Your points are welcomed. Regards, Mehdi Salehi This e-mail (including any attachments) is confidential and may be legally privileged. If you are not an intended recipient or an authorized representative of an intended recipient, you are prohibited from using, copying or distributing the information in this e-mail or its attachments. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete all copies of this message and any attachments. Thank you.
Re: best backup method for millions of small files?
Steve Had this problem last week and found this Microsoft Technet article. Fixed the problem after a reboot http://support.microsoft.com/kb/30401 Regards, Allan Allan Mills Technology Operations 02 8835 8035 0422 208 031 Steven Harris sjhar...@au1.ibm.com Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 01/05/2009 09:39 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] best backup method for millions of small files? Hi Norman Your post worries me, as I'm just implementing an email archive solution that will depend on windows journalling to back up some huge repositories. The particular product fills up containers that once filled never change, so the change rate will be low there, but there are also index files that will change often. Have you determined whether the memory issue is related to number of files or number of changes? Regards Steve Steven Harris TSM Admin, Sydney Australia Gee, Norman norman@lc.ca .GOV To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] best backup method for millions of small files? 01/05/2009 07:12 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU What options are there when journaling runs out of memory on a 32 bit Windows server? I have about 10 million files on one server that the journal engine runs out of memory. With memory efficient disk cache method and resource utilization 5, its runs out of memory, resource utilization of 4 runs too long. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: best backup method for millions of small files? You have a disk array copy of the data, is that located close or far? Have you considered a disk array snap shot also? If you perform a journaled file system backup and an image backup then you should be able to restore the image and then update the image with the file system restore. This might take a long time, I have never tried it. What failure are you trying to protect against? In our case we use the disk arrays to protect against a data center loss and a corrupt file system and a TSM file system backup to protect against the loss of a file. Our big ones are in the 10 million file range. Using a 64bit Windows server we can backup the file system in about 6 - 8 hours without journaling. We suspect we could get the time down to around 4 hours if the TSM server was not busy backing up 500 other nodes. To me the important thing is to figure out what you are protecting against with each thing you do. Also be sure and ask what the Recovery Point Objective (RPO) is. If it is less than 24 hours then array based solutions may be the best choice. Over 24 hours then TSM may be the best choice. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Thursday, April 30, 2009 9:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] best backup method for millions of small files? Hi, None the two methods that you mean in the user's guide are suitable for my case. Image+normal incremental that you emphasized in your post means getting full image backups for example every week. For the incremental part, one file-based full backup is needed which is a nightmare for 20 millions. OK, if I accept the initial incremental backup time (that might take for days), what happens in restoration? Naturally, last image backup should be restored first and it will take A minutes. Provided that image backups are weekly, the progressive incremental backups of the week is about 6*20MB=120MB. Now imagine 120MB of 15-20K files are to be restored in filesystem with an incredibly big file address table and system should create an inode-like entry for each. If this step takes B minutes, the total restoration time would be A+B. (A+B/A) ratio is important and I will try to measure and share it with the group. Steven, your solution is excellent for ordinary filesystems with a limited number of files. But I think for millions of files, only backup/restore method that do not care how many files exist in the volume are feasible. Somehing like pure image backup (like Acronis image incremental backup) or the method that FastBack exploites. Your points are welcomed. Regards, Mehdi Salehi This e-mail (including any attachments) is confidential and may be
ANS1996W The volume mount points enumeration on D:/ volume f
Hi David, I have seen this error during vcb backup. I solved my problem with Microsoft KB934336 hot fix. Regards, Suat ORSLU -- David McClelland wrote: Hi Team, Has anyone seen this one before? From dsmerror.log. 04/29/2009 11:43:20 ANS1996W The volume mount points enumeration on 'D:\' volume failed. Windows system error code: 5; reason: 'Access is denied.'. 04/29/2009 11:43:32 ANS1996W The volume mount points enumeration on 'E:\' volume failed. Windows system error code: 5; reason: 'Access is denied.'. Windows TSM BA Client 5.5.2.0 on a Windows 2003 R2 64-bit system. Nothing in the Windows Application or System Event Log accompanying this. It occurs when browsing the local disks in the BA Client GUI. Nothing for this ANS1996W that Ive seen in Google, on IBM.com or even in the TSM Information Centre messages section. Rgds, /David Mc London, UK No virus found in this outgoing message. Checked by AVG. Version: 7.5.524 / Virus Database: 270.12.4/2082 - Release Date: 27/04/2009 06:19 +-- |This was sent by sor...@msn.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +--
Re: best backup method for millions of small files?
Sorry cannot type today http://support.microsoft.com/kb/304101 Regards, Allan Allan Mills Technology Operations 02 8835 8035 0422 208 031 - Forwarded by Allan Mills/1115388/Staff/NSWPolice on 01/05/2009 11:35 - Allan Mills/1115388/Staff/NSWPolice 01/05/2009 10:03 To ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] best backup method for millions of small files? Steve Had this problem last week and found this Microsoft Technet article. Fixed the problem after a reboot http://support.microsoft.com/kb/30401 Regards, Allan Allan Mills Technology Operations 02 8835 8035 0422 208 031 Steven Harris sjhar...@au1.ibm.com Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 01/05/2009 09:39 Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject Re: [ADSM-L] best backup method for millions of small files? Hi Norman Your post worries me, as I'm just implementing an email archive solution that will depend on windows journalling to back up some huge repositories. The particular product fills up containers that once filled never change, so the change rate will be low there, but there are also index files that will change often. Have you determined whether the memory issue is related to number of files or number of changes? Regards Steve Steven Harris TSM Admin, Sydney Australia Gee, Norman norman@lc.ca .GOV To Sent by: ADSM: ADSM-L@VM.MARIST.EDU Dist Stor cc Manager ads...@vm.marist Subject .EDU Re: [ADSM-L] best backup method for millions of small files? 01/05/2009 07:12 AM Please respond to ADSM: Dist Stor Manager ads...@vm.marist .EDU What options are there when journaling runs out of memory on a 32 bit Windows server? I have about 10 million files on one server that the journal engine runs out of memory. With memory efficient disk cache method and resource utilization 5, its runs out of memory, resource utilization of 4 runs too long. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebner,Andy,FORT WORTH,IT Sent: Thursday, April 30, 2009 8:16 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: best backup method for millions of small files? You have a disk array copy of the data, is that located close or far? Have you considered a disk array snap shot also? If you perform a journaled file system backup and an image backup then you should be able to restore the image and then update the image with the file system restore. This might take a long time, I have never tried it. What failure are you trying to protect against? In our case we use the disk arrays to protect against a data center loss and a corrupt file system and a TSM file system backup to protect against the loss of a file. Our big ones are in the 10 million file range. Using a 64bit Windows server we can backup the file system in about 6 - 8 hours without journaling. We suspect we could get the time down to around 4 hours if the TSM server was not busy backing up 500 other nodes. To me the important thing is to figure out what you are protecting against with each thing you do. Also be sure and ask what the Recovery Point Objective (RPO) is. If it is less than 24 hours then array based solutions may be the best choice. Over 24 hours then TSM may be the best choice. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Thursday, April 30, 2009 9:39 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] best backup method for millions of small files? Hi, None the two methods that you mean in the user's guide are suitable for my case. Image+normal incremental that you emphasized in your post means getting full image backups for example every week. For the incremental part, one file-based full backup is needed which is a nightmare for 20 millions. OK, if I accept the initial incremental backup time (that might take for days), what happens in restoration? Naturally, last image backup should be restored first and it will take A minutes. Provided that image backups are weekly, the progressive incremental backups of the week is about 6*20MB=120MB. Now imagine 120MB of 15-20K files are to be restored in filesystem with an incredibly big file address table and system should create an inode-like entry for each. If this step takes B minutes, the total restoration time would be A+B. (A+B/A) ratio is important and I will try to measure and share it with the group. Steven, your solution is excellent for ordinary
