backup files larger than tape cartridge size
Hi, I have some large files and images backed up to disk pool and then migrated to tapes. As the size of images grows gradually, I wonder what happens if the file size exceeds the cartridge capacity. Can TSM split them into multiple cartridges during stg migration? Thanks
Re: backup files larger than tape cartridge size
Yes, if you watch it closely. Sometimes you can see the migration or backup STG ask for a scratch tape during the process. When it reaches the end of tape, TSM will ask for a new tape to place the rest of the file on the new tape(s). I have a single NDMP backup that is over 4 TB that is backup to 4 consecutive LTO4 tapes with no problems. All 4 tapes shows the same last written date and time. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mehdi Salehi Sent: Tuesday, July 20, 2010 7:20 AM To: ADSM-L@VM.MARIST.EDU Subject: backup files larger than tape cartridge size Hi, I have some large files and images backed up to disk pool and then migrated to tapes. As the size of images grows gradually, I wonder what happens if the file size exceeds the cartridge capacity. Can TSM split them into multiple cartridges during stg migration? Thanks
Re: backup files larger than tape cartridge size
I noticed that in the migration process when migrating a 250GB file, the output volume was a 300GB cartridge (with Pct Util=55%). But after some minutes, TSM changed the output volume to a scratch one as if nothing had been copied during those minutes.
Re: backup files larger than tape cartridge size
See Spanning in http://people.bu.edu/rbs/ADSM.QuickFacts On Jul 20, 2010, at 10:19 AM, Mehdi Salehi wrote: Hi, I have some large files and images backed up to disk pool and then migrated to tapes. As the size of images grows gradually, I wonder what happens if the file size exceeds the cartridge capacity. Can TSM split them into multiple cartridges during stg migration? Thanks
Re: backup files larger than tape cartridge size
Thanks Richard, Found the concept of segment. Regards
Re: Excessive memory consumption by 5.5 Linux client on SLES 10.3 x86_64
Grigori Solonovitch wrote: I think there is a mistake in version. If you mention 6.2.1.0, try to install 6.2.1.1. There are some bugs related to memory allocation which are fixed in 6.2.1.1. At least, client 6.2.1.1 helped to fix my problems with memory allocation. Sorry for the typo. 6.2.1.1 is my current version. My fault: [...] OTOH, do you have evidence that dsmc (meanwhile upgraded to 6.6.2.1, should_have_been:_6.2.1.1 without a noticable diffence in behaviour) still might contain such weird bugs? After all, TSM backup ought not follow symlinks at all. [...] Best regards, Wolfgang J. Moeller moel...@gwdg.de Tel. +49 551 201-1516 ... not representing ... GWDG, Goettingen, Germany
Thank you Del!
Del, I just wanted to thank you again for all your help and for being so generous with your time and patience. I know that responding to questions on ADSM-L is not your primary job, but you are an invaluable resource for us! Wanda Prather | Senior Technical Specialist | wprat...@icfi.commailto:wprat...@icfi.com | www.jasi.comwww.jasi.com%20 ICF Jacob Sundstrom | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135
Re: TDP for Exchange 2010 and Mailbox Restore
Thanks so much! -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Del Hoobler Sent: Monday, July 19, 2010 4:57 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TDP for Exchange 2010 and Mailbox Restore Wanda, Answers embedded below. Thanks, Del ADSM: Dist Stor Manager ADSM-L@vm.marist.edu wrote on 07/19/2010 04:15:36 PM: From: Prather, Wanda wprat...@icfi.com To: ADSM-L@vm.marist.edu Date: 07/19/2010 04:18 PM Subject: Re: TDP for Exchange 2010 and Mailbox Restore Sent by: ADSM: Dist Stor Manager ADSM-L@vm.marist.edu Hi Del, Thanks SO MUCH for responding. That is the doc I am using (the -01 version of the book), and I have to admit I'm struggling with it! (There are now so many combinations of Exchange 200x, VSS-software, and VSS-hardware that I'm finding it very difficult to figure out which options apply to which combination.) On this Exchange2010 server, there's just Exchange 2010, the TSM BA client 6.2.1, the TDP 6.1.2, Microsoft Win2K8 64, and me. No SVC, Copy Services, or VSS hardware assist. 1) On P. 87 of the book, under use VSS as the default backup method option, it says This parameter is unavailable if the Microsoft Exchange VSS Integration Module is not installed. That's the module I'm asking about - is it Copy Services only? The book is written generically for all versions of Exchange, so whenever the writers try to generalize, some of the exceptions are missed. Since Exchange 2010 only supports VSS, TSM does not require this additional module if you only want to perform backups to the TSM Server. Otherwise you would be charged twice (once for Copy Services and once for DP/Exchange). It is only if you want to create and manage local (persistent) snapshots that you need Copy Services. 2) I figure we MUST be getting VSS backups - we can run fulls and incrs from the GUI, and restore a DB. So if VSS is the only option for 2010, well... must be getting it. However: Correct. It only supports VSS. :-) (Microsoft dropped legacy, aka streaming, backups with Exchange 2010.) I have exec.cfg set to location BOTH, and VSSPOLICY set to keep 3 versions local. However, when we click restore, all the fulls and incrs show up with backup location : TSM server. When we try to run a restore, we have no place to select the VSS local copy (which would be great for mailbox-level restores). In order to store snapshots locally, i.e. create persistent VSS snapshots, you need to install the TSM for Copy Services modules as described (FYI... Copy Services was replaced last year by FlashCopy Manager, which has an MMC front-end, configuration wizards, and more). P. 8 in the book says: Backups can be stored on local shadow volumes, Tivoli Storage Manager server storage, or both locations, and nowhere in the VSS planning section does it say a hardware provider is required. You do not need a hardware provider to store snapshots locally. You can simply use the in-box VSS Provider that Windows ships in the shrink-wrap Windows box. A VSS hardware provider can give you much better performance and help offload the tracking of snapshots vs. the in-box VSS Provider. As I mentioned above, in order to be able to create and storage local snapshots, you need to install TSM for Copy Services or FlashCopy Manager. The glossary says VSS Fast Restore: A function that uses a Microsoft Volume Shadow Copy Service (VSS) software provider to restore VSS Backups (IBM Data Protection for Exchange database files and log files) that reside on local shadow volumes.) So, am I supposed to be able to keep BOTH local VSS and TSM copies? That's the problem I'm having now. Right. You need to purchase and install FlashCopy Manager in order to manage local (persistent) snapshots.
Re: Export server error - RESOLVED
Hi David, I´d like to thank you for your help. The problem was not a TSM problem after alleverything was configured correctly thanks to you guys.it was a network issue and once the network guys solved their problem, everything worked fine. Best regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Sun, July 18, 2010 4:00:44 PM Subject: Re: Export server error Very puzzling - there's something either really obvious or pretty discrete afoot here preventing this from working. Just out of curiosity, can your TSM BA Client connect from the source to the target server (and vice versa)? And the admin client as well? Cheers, //DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 18 July 2010 17:52 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, Everything u guys told me is in place - both source and target servers ping each other from the OS (the HLAddress configured with the DEFINE SERVER) - the admin user exists on both machines and have the same password - the admin I´ve registered and use also exists on both TSM Servers and have the same password - the LLAddress, TCP Port, is 1500 on both TSM Servers, which are installed on separate physical machines - the TCP Port 1500 is in LISTENING state on both machines (netstat -an)...both servers are Windows 2003 Servers - both hostnames are declared on each others HOSTS file - there is NO FIREWALL or anything between these TSM Servers - telnet on localhost on TCP Port 1500 accepts the connection on both machines Butthe PING SERVER command fail on both TSM Servers tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. tsm: TSM_TARGETping server tsm_source ANR1705W Ping for server 'TSM_SOURCE' was not able to establish a connection. ANS8001I Return code 4. Everything seems to be properly configuredwhat could be wrong or missing? Any help is aprreciated. Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 9:27:00 PM Subject: Re: Export server error Hi Mario, Looks like some detailed double-checking of the config is required - here goes! O - As Marcel points out, first you'll need to have an administrative user registered with the same password upon the source and target TSM Server instances. O - Next, the High Level Address (HLA) of the target server needs (visible in Q SERVER) to be resolvable/pingable from your shell/OS prompt on the source server. O - Finally, the Low Level Address (LLA) of the target server (visible in Q SERVER) needs to be set to the TCPPort upon which the target server is listening (e.g. visible from Q OPT output on target server). What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? Your source and target TSM Server instances can run on the same TCPPORT if they're running on different physical servers. If all of these are in place and there aren't any other factors getting in the way, PING SERVER commands should work and you'll have a platform for TSM Server to Server operations. HTH - let us know how you get on. //DMc London, UK - going to bed. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Mario Behring Sent: 17 July 2010 00:59 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export server error Hi David, No...it is not successful...check the output below...I am calling the servers TSM_SOURCE and TSM_TARGET to make this easier: tsm: TSM_SOURCEping server tsm_target ANR1705W Ping for server 'TSM_TARGET' was not able to establish a connection. ANS8001I Return code 4. The same happens the other way around. What about the TCP Port (lladdress)? I´ve configured different tcp ports in each serveris that correct? tsm: TSM_SOURCEq server Server Comm. High-level Low-level Days Server Name Method Address AddressSince Password -- - - -- TSM_TARGET TCPIP xx.xx.xx.xx 1919 1Yes tsm: TSM_TARGETq server ServerComm. High-levelLow-level Days Server Name Method Address AddressSince Password -- - - -- TSM_SOURCE TCPIP xx.xx.xx.xx 15001 Yes Regards, Mario From: David McClelland t...@networkc.co.uk To: ADSM-L@VM.MARIST.EDU Sent: Fri, July 16, 2010 7:56:06 PM Subject: Re: Export server error Hi Mario, What does a `PING SERVER
Re: Thank you Del!
I agreed ! Rober OuzenI -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Prather, Wanda Sent: Tuesday, July 20, 2010 9:31 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Thank you Del! Del, I just wanted to thank you again for all your help and for being so generous with your time and patience. I know that responding to questions on ADSM-L is not your primary job, but you are an invaluable resource for us! Wanda Prather | Senior Technical Specialist | wprat...@icfi.commailto:wprat...@icfi.com | www.jasi.comwww.jasi.com%20 ICF Jacob Sundstrom | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 410.539.1135
partial VM images.
Hi All I have a VMware windows VM that I do daily VCB incrementals and Monthly VCB fulls on. It is thin-provisioned and now the real disk usage has expanded to the point where it exceeds the capacity of my proxy server's landing area. This particular VM runs SQL Server which is backed-up by dump to disk, and thence to TSM via VCB. There is no point in backing up the disk containing the databases, so I'm looking to exclude those disks from the monthly image and just backup C: and the dump disk. I can see no way to do this. The BACKUP VM command has no option to specify particular volumes. I tried -DOMAIN.IMAGE but that option was rejected. 6.2 has DOMAIN.VMFULL but that specifies which machines to back up not which disks. Does anyone know how it can be done? TSM Server is 5.5.3.0 Solaris X86_64 client is Windows 2008 and TSM 6.1.3.0, but could go to 6.2.1.x if this will solve the problem. Thanks Steve Steven Harris TSM Admin Paraparaumu, New Zealand
