Another approach to my problem...
All, Thanks for your help on migration strategies. I think it's doable by us (me, really) with only a few things to be ironed out. However, I've also been asked to look at moving to a different solution entirely. Has anyone here been asked to do this? The new solution is yet to be determined, though Ultrabac and Retrospect are high on my list. My concern is that I don't want orphan the data I have on tape and disk in TSM - including my archives and inactive data. Any pointers to documentation on how I could get the data out of TSM into another product? Kurt
Migration for Windows-based installation
All, We have a TSM server that's running out of steam, and nearing the end of its expected reliable life. We have Version 5, Release 3, Level 4.6 installed, with various levels of clients installed on our servers. The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow PATA, and the OS is Win2k Pro. Definitely not ideal. The tape robot is a Spectralogic T50, with two LTO3 drives and 25 slots, out of which we expect to get much more life. We expect to replace the server with a new Dell server with 3tb of SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. I'd like to get to the newest in the 5.x series on the new server, since the talk on this list about moving to 6.x indicates to me that we'd be better off staying at 5.x for now. I've been casting about, and can't seem to find documentation on how to migrate the setup to the new machine. Does anyone have a pointer to good documentation on doing this? Frankly, we've been given a quote by a VAR, and though the number of hours they are quoting seem reasonable, the price they're asking to work with us on this is beyond our budget. Thanks Kurt
Re: Migration for Windows-based installation
I'd prefer to be able to migrate server data as much as possible, including the diskpool, but if it it would be an incredibly difficult maneuver (or take inordinate amounts of time, say on the order of more than a 4-day weekend) and/or the downside of losing the diskpool is relatively minor, I could potentially live without it. I would also contemplate keeping the current TSM server version on the new machine and upgrading immediately after implementation if that would be of benefit. We back up fewer than 10 servers, but one is our Exchange 2003 server at roughly 200gb and is a full backup every night, and the other is our file server at over 2tb, though on a nightly basis it normally does around 25-50gb. Does that answer your question? Kurt On Mon, Oct 12, 2009 at 11:18, David McClelland t...@networkc.co.uk wrote: Are you looking purely at a lift and shift hardware change here, or at a clean installation of TSM Server (at 5.5.3 for example) and migrating clients into the new instance? Cheers, /David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: 12 October 2009 18:54 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Migration for Windows-based installation All, We have a TSM server that's running out of steam, and nearing the end of its expected reliable life. We have Version 5, Release 3, Level 4.6 installed, with various levels of clients installed on our servers. The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow PATA, and the OS is Win2k Pro. Definitely not ideal. The tape robot is a Spectralogic T50, with two LTO3 drives and 25 slots, out of which we expect to get much more life. We expect to replace the server with a new Dell server with 3tb of SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. I'd like to get to the newest in the 5.x series on the new server, since the talk on this list about moving to 6.x indicates to me that we'd be better off staying at 5.x for now. I've been casting about, and can't seem to find documentation on how to migrate the setup to the new machine. Does anyone have a pointer to good documentation on doing this? Frankly, we've been given a quote by a VAR, and though the number of hours they are quoting seem reasonable, the price they're asking to work with us on this is beyond our budget. Thanks Kurt No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.421 / Virus Database: 270.14.3/2415 - Release Date: 10/12/09 04:01:00
Re: Migration for Windows-based installation
So, what happens to all the tapes I have offsite at Iron Mountain, and the archives I have stored in my basement vault, etc. I'll be perusing the archives as you suggest, but this isn't exactly crystalline to me just yet. A complicating factor that I hadn't realized until I did a bit of digging just now is that the current database holds references to a *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we migrated from some years ago. Would the procedure you're suggesting clean that up? Kurt On Mon, Oct 12, 2009 at 12:10, Kelly Lipp l...@storserver.com wrote: Start from scratch. Install TSM at the level you would like, move and configure the library. Point the clients at the new server and go. That first backup will necessarily be a full. Will take longer than usual, but easy. This method allows you go clean up your database. Keep the old server around until the data expires. Clearly, there are more details, especially since you are going to re-use the library on the new STORServer (oops, I mean TSM Server). The overall concept is sound. For sites of your size I like this method as it is simple and gets me a brand new, pristine database. This will become important next year when you migrate to TSM 6.2. Besides, a clean start is always a good thing. This topic has been covered earlier and in much more detail. You might peruse the archives to see what you can find. My name will show up along with others like Wanda who have been through this many times. Thanks, Kelly Lipp Chief Technical Officer www.storserver.com 719-266-8777 x7105 STORServer solves your data backup challenges. Once and for all. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 1:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation I'd prefer to be able to migrate server data as much as possible, including the diskpool, but if it it would be an incredibly difficult maneuver (or take inordinate amounts of time, say on the order of more than a 4-day weekend) and/or the downside of losing the diskpool is relatively minor, I could potentially live without it. I would also contemplate keeping the current TSM server version on the new machine and upgrading immediately after implementation if that would be of benefit. We back up fewer than 10 servers, but one is our Exchange 2003 server at roughly 200gb and is a full backup every night, and the other is our file server at over 2tb, though on a nightly basis it normally does around 25-50gb. Does that answer your question? Kurt On Mon, Oct 12, 2009 at 11:18, David McClelland t...@networkc.co.uk wrote: Are you looking purely at a lift and shift hardware change here, or at a clean installation of TSM Server (at 5.5.3 for example) and migrating clients into the new instance? Cheers, /David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: 12 October 2009 18:54 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Migration for Windows-based installation All, We have a TSM server that's running out of steam, and nearing the end of its expected reliable life. We have Version 5, Release 3, Level 4.6 installed, with various levels of clients installed on our servers. The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow PATA, and the OS is Win2k Pro. Definitely not ideal. The tape robot is a Spectralogic T50, with two LTO3 drives and 25 slots, out of which we expect to get much more life. We expect to replace the server with a new Dell server with 3tb of SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. I'd like to get to the newest in the 5.x series on the new server, since the talk on this list about moving to 6.x indicates to me that we'd be better off staying at 5.x for now. I've been casting about, and can't seem to find documentation on how to migrate the setup to the new machine. Does anyone have a pointer to good documentation on doing this? Frankly, we've been given a quote by a VAR, and though the number of hours they are quoting seem reasonable, the price they're asking to work with us on this is beyond our budget. Thanks Kurt No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.421 / Virus Database: 270.14.3/2415 - Release Date: 10/12/09 04:01:00
Re: Migration for Windows-based installation
Disk for the current TSM server is IDE/PATA in a RAID5 array internal to the machine - though the OS is on a (eep!) single IDE/PATA drive connected to the motherboard. Kurt On Mon, Oct 12, 2009 at 13:19, David McClelland t...@networkc.co.uk wrote: Okay, another fun question for you Kurt, investigating some alternative lines of simply migrating your current TSM server instance to new hardware: is the disk upon which your current TSM database/recovery log/storage pool live internal to your old server, or is it instead hosted upon external disk and thus (potentially) relatively feasible to 'introduce' to your new hardware? /DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: 12 October 2009 21:09 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation So, what happens to all the tapes I have offsite at Iron Mountain, and the archives I have stored in my basement vault, etc. I'll be perusing the archives as you suggest, but this isn't exactly crystalline to me just yet. A complicating factor that I hadn't realized until I did a bit of digging just now is that the current database holds references to a *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we migrated from some years ago. Would the procedure you're suggesting clean that up? Kurt On Mon, Oct 12, 2009 at 12:10, Kelly Lipp l...@storserver.com wrote: Start from scratch. Install TSM at the level you would like, move and configure the library. Point the clients at the new server and go. That first backup will necessarily be a full. Will take longer than usual, but easy. This method allows you go clean up your database. Keep the old server around until the data expires. Clearly, there are more details, especially since you are going to re-use the library on the new STORServer (oops, I mean TSM Server). The overall concept is sound. For sites of your size I like this method as it is simple and gets me a brand new, pristine database. This will become important next year when you migrate to TSM 6.2. Besides, a clean start is always a good thing. This topic has been covered earlier and in much more detail. You might peruse the archives to see what you can find. My name will show up along with others like Wanda who have been through this many times. Thanks, Kelly Lipp Chief Technical Officer www.storserver.com 719-266-8777 x7105 STORServer solves your data backup challenges. Once and for all. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 1:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation I'd prefer to be able to migrate server data as much as possible, including the diskpool, but if it it would be an incredibly difficult maneuver (or take inordinate amounts of time, say on the order of more than a 4-day weekend) and/or the downside of losing the diskpool is relatively minor, I could potentially live without it. I would also contemplate keeping the current TSM server version on the new machine and upgrading immediately after implementation if that would be of benefit. We back up fewer than 10 servers, but one is our Exchange 2003 server at roughly 200gb and is a full backup every night, and the other is our file server at over 2tb, though on a nightly basis it normally does around 25-50gb. Does that answer your question? Kurt On Mon, Oct 12, 2009 at 11:18, David McClelland t...@networkc.co.uk wrote: Are you looking purely at a lift and shift hardware change here, or at a clean installation of TSM Server (at 5.5.3 for example) and migrating clients into the new instance? Cheers, /David Mc London, UK -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: 12 October 2009 18:54 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Migration for Windows-based installation All, We have a TSM server that's running out of steam, and nearing the end of its expected reliable life. We have Version 5, Release 3, Level 4.6 installed, with various levels of clients installed on our servers. The server has 1gb RAM, roughly 2tb of disk storage, but it's old/slow PATA, and the OS is Win2k Pro. Definitely not ideal. The tape robot is a Spectralogic T50, with two LTO3 drives and 25 slots, out of which we expect to get much more life. We expect to replace the server with a new Dell server with 3tb of SATA disk, 3gb RAM, Win2k3 (32bit), and use the current tape robot. I'd like to get to the newest in the 5.x series on the new server, since the talk on this list about moving to 6.x indicates to me that we'd be better off staying at 5.x for now. I've been casting about, and can't seem to find documentation on how to migrate
Re: Migration for Windows-based installation
Yeah, as I dig into this it becomes more complicated. We have a number of pools: Disk Pools: diskpool Sequential Access Storage Pools: ltopool 8mmpool1 (which needs to die) archivepool ltoarchive reclaimpool Copy Storage pools: copypool ltocopy We have several devclasses, too: Disk Device Class Disk File Device Class ReclaimClass 8MM Device Clases 8mmclass1 LTO Device Class LTO The 8mm stuff really needs to go away, I think, especially since Treefrog we had was traded in to get the T50. We also have data that is archived on the LTO tapes, and that we'll need for at least 4 more years - financial stuff, doncha know. Kurt On Mon, Oct 12, 2009 at 13:24, Bob Levad ble...@winnebagoind.com wrote: When we migrated to a new server and LTO4 from LTO1, we installed all of the new stuff and tested the hardware with the TSM version we were running. When that was working well, we drained all of the disk pools, backed up the database from the existing server, shut it down, attached the old tape drives to the new server, restored the database, brought it up, deleted all of the old disk pools, defined new disk pools for the new hardware, defined the new tape drives, set up new devclasses and storage pools, changed the domains to point to the new devices and migration hierarchy, tested backups and restores, and set up move data jobs to move data from the LTO1's back to disk pools where it would then migrate to the new LTO4s. Once the LTO1's were empty, we detached the library and recycled the old tapes. The upgrade to a newer TSM could occur on the old server or the new, but best probably not at the same time as the hardware cutover. Starting from scratch was not an option for us as we have files with multi-year retentions. Bob. PS - If you have references to tapes that no longer exist, there are methods (google is your friend) to delete references to them. The method of deletion may depend on how the data was stored (primary/copypool/backupset/db backup/other). Once the references are gone, you should delete the storage pools and device classes that are obsolete. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 3:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation So, what happens to all the tapes I have offsite at Iron Mountain, and the archives I have stored in my basement vault, etc. I'll be perusing the archives as you suggest, but this isn't exactly crystalline to me just yet. A complicating factor that I hadn't realized until I did a bit of digging just now is that the current database holds references to a *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we migrated from some years ago. Would the procedure you're suggesting clean that up? Kurt On Mon, Oct 12, 2009 at 12:10, Kelly Lipp l...@storserver.com wrote: Start from scratch. Install TSM at the level you would like, move and configure the library. Point the clients at the new server and go. That first backup will necessarily be a full. Will take longer than usual, but easy. This method allows you go clean up your database. Keep the old server around until the data expires. Clearly, there are more details, especially since you are going to re-use the library on the new STORServer (oops, I mean TSM Server). The overall concept is sound. For sites of your size I like this method as it is simple and gets me a brand new, pristine database. This will become important next year when you migrate to TSM 6.2. Besides, a clean start is always a good thing. This topic has been covered earlier and in much more detail. You might peruse the archives to see what you can find. My name will show up along with others like Wanda who have been through this many times. Thanks, Kelly Lipp Chief Technical Officer www.storserver.com 719-266-8777 x7105 STORServer solves your data backup challenges. Once and for all. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 1:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation I'd prefer to be able to migrate server data as much as possible, including the diskpool, but if it it would be an incredibly difficult maneuver (or take inordinate amounts of time, say on the order of more than a 4-day weekend) and/or the downside of losing the diskpool is relatively minor, I could potentially live without it. I would also contemplate keeping the current TSM server version on the new machine and upgrading immediately after implementation if that would be of benefit. We back up fewer than 10 servers
Re: Migration for Windows-based installation
I'll have to work through a fair amount to understand what you've outlined, but it seems doable. I think pruning volhist and devconfig first might be a good idea, if for no other reason than to cut down on the confusion. Thanks for the input. I'll most likely be back for more information. Kurt On Mon, Oct 12, 2009 at 14:03, Ochs, Duane duane.o...@qg.com wrote: For my last migration to new hardware I built a new system and used export/import server to server. Worked very well. Doesn’t work if you have only one library though. However, you are looking for an alternate method. I'd recommend upgrading to TSM 5.5 first. Especially if you run into problems and have to call IBM for support. This is a really simplified step by step. Build your new system: Install the same version of TSm that you have on the old system. On old server: Perform a DB backup to a blank tape. Two for redundancy. Backup volhist. Backup devconfig Take down TSM on your old TSM server Document all tape drive/library information and drivers. Copy db files to the new system, reclog volumes and diskpool volumes. If you are really familiar with TSM you can minimize the amount of diskpool volumes to be copied first. Copy the contents of your server directory to the new system. Verify that your copied dsmserv.dsk file reflects the new location of the DB files and log files. If everything was done correctly and verified properly you should be able to start up your TSM database. Then you will have to redefine your library and drives. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 3:37 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Migration for Windows-based installation Disk for the current TSM server is IDE/PATA in a RAID5 array internal to the machine - though the OS is on a (eep!) single IDE/PATA drive connected to the motherboard. Kurt On Mon, Oct 12, 2009 at 13:19, David McClelland t...@networkc.co.uk wrote: Okay, another fun question for you Kurt, investigating some alternative lines of simply migrating your current TSM server instance to new hardware: is the disk upon which your current TSM database/recovery log/storage pool live internal to your old server, or is it instead hosted upon external disk and thus (potentially) relatively feasible to 'introduce' to your new hardware? /DMc -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: 12 October 2009 21:09 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation So, what happens to all the tapes I have offsite at Iron Mountain, and the archives I have stored in my basement vault, etc. I'll be perusing the archives as you suggest, but this isn't exactly crystalline to me just yet. A complicating factor that I hadn't realized until I did a bit of digging just now is that the current database holds references to a *really* old set of 8mm (AIT2) tapes from a Spectralogic Treefrog that we migrated from some years ago. Would the procedure you're suggesting clean that up? Kurt On Mon, Oct 12, 2009 at 12:10, Kelly Lipp l...@storserver.com wrote: Start from scratch. Install TSM at the level you would like, move and configure the library. Point the clients at the new server and go. That first backup will necessarily be a full. Will take longer than usual, but easy. This method allows you go clean up your database. Keep the old server around until the data expires. Clearly, there are more details, especially since you are going to re-use the library on the new STORServer (oops, I mean TSM Server). The overall concept is sound. For sites of your size I like this method as it is simple and gets me a brand new, pristine database. This will become important next year when you migrate to TSM 6.2. Besides, a clean start is always a good thing. This topic has been covered earlier and in much more detail. You might peruse the archives to see what you can find. My name will show up along with others like Wanda who have been through this many times. Thanks, Kelly Lipp Chief Technical Officer www.storserver.com 719-266-8777 x7105 STORServer solves your data backup challenges. Once and for all. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Kurt Buff Sent: Monday, October 12, 2009 1:02 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Migration for Windows-based installation I'd prefer to be able to migrate server data as much as possible, including the diskpool, but if it it would be an incredibly difficult maneuver (or take inordinate amounts of time, say on the order of more than a 4-day weekend) and/or the downside of losing the diskpool is relatively minor, I could potentially live without it. I would also contemplate
Sunbelt File Archiver Experience?
All, We're contemplating purchasing this product, which seems to be an HSM, along with some data deduplication. Link here: http://www.sunbeltsoftware.com/Business/Sunbelt-File-Archiver/ Does anyone on this list have experience with it, especially how it integrates (or doesn't!) with TSM? I'm going to be talking to their support engineers to see what they have to say, but any knowledge I can gain here would be appreciated. Thanks, Kurt
Re: Backup Windows Eventlog / Systemlog for 2 years
I suggest psloglist.exe - it's a free MSFT utility, from the Sysinternals guys. The whole suite of tools is nearly mandatory for inclusion in a Windows administration toolkit. http://www.microsoft.com/sysinternals Kurt -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Wanda Prather Sent: Tuesday, November 18, 2008 06:23 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Backup Windows Eventlog / Systemlog for 2 years There is a Windows utility (unfortunately I forget the name; I think it's from one of the older Windows resource kits) that lets you extract the event log to a flat file. I'd run that every day, then have TSM archive the flat file and delete from the hard drive. On Tue, Nov 18, 2008 at 3:31 AM, Herrmann, Boris [EMAIL PROTECTED]wrote: Hello all, today we got the request to daily backup the windows event and windows system log and keep them for 2 years (from Windows 2003 Server). Is there a way to do this with the TSM Client to only backup this part from Systemstate / Systemservices and bound this to a special ManagementClass? Any help is appreciate, Boris
Re: Forecasting Windows client workloads
http://gnuwin32.sf.net - you'll find good tools there, including wc and other core unix utils. To find the number of files, a better incantation for your dir command is dir /s /b | wc -l This will give a better line/file count. You could also pipe this to an output file, and put together a batch file or perl script to give you the size of each file and sum them. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Thomas Denier Sent: Friday, February 29, 2008 13:16 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Forecasting Windows client workloads People who want TSM coverage for new systems at our site are asked to provide reasonably accurate estimates for the following: 1.Aggregate size of files on the system 2.Number of files on the system 3.Aggregate size of files that will be backed up each day 3.Number of files that will be backed up each day Nobody has a problem with number 1, but Windows administrators are constantly complaining about how difficult it is to obtain the other three. Some of them insist that it is impossible to obtain this information. So far, the least ugly option I have found for counting files on a volume is to open a command line window, change to the root folder, and execute the following command: dir /s | find File(s) The Search facility on the Start menu can search for files modified within a day, which should give a reasonable idea of what daily backups will look like. The result windows lists the modified files and reports the number of files. Size information is shown for each file listed, but the sum of the sizes is not calculated automatically, and the window seems to have been designed so that it is impossible to transfer the size information to another program. Are there better ways for Windows administrators to get the information we are asking for?
Re: Windows Client question...
I would suggest not backing up PST files, if the environment is running Exchange. Exchange is the proper store for email in that case, as PST files are much more fragile than the Exchange store. If the environment is so small that they are not using Exchange, then IMHO TSM is probably not a good fit for their environment anyway. On a semi-related note, this MSFT KB article http://support.microsoft.com/kb/297019 and especially this blog post http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx explain why PST storage on file servers is a bad idea. Kurt -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Elana Samuels Sent: Thursday, January 17, 2008 17:28 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows Client question... So how would you recommend to backup open PST files? Unfortunately in the SMB space, most desktops are running Outlook and the users typically leave their mail open at night. Elana Samuels Tier 1 Data Solutions Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Wanda Prather Sent: Thursday, January 17, 2008 7:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Windows Client question... Agreed. I tell my customers NOT to install OFS unless they have a reason, and only on systems where they know what the reason is. It triggers a LOT of unncessary and pretty unintelligible VSS errors, and is usually doing nothing worthwhile. Look at your TSM daily reporter output on clients without OFS installed, check the missed file details. You'll find that 90% of the files that are missed are in the category of usual suspects. You may want to sit down with a Windows admin and get them to help you identify the missed files. Many will be ntuser.dat or ntuser.log files, or other parts of the user profile. You rarely need backups of these unless you are backing up desktops, and then the profiles are included in teh backup of System State. Most of the rest will be files that are clearly identifiable as DB parts belonging to apps like SQL or Oracle. OFS support does not necessarily give you good backups of a data base, because there is no interface with the DB journal/logs. So even if people THINK they are getting backups this way, you probably shouldn't count on using them - the appropriate solution for DB's is using a TDP client. Once you identify the missed files, you'll usually find there is nothing on the client that needs the OFS support - exception would be a locally developed application. But I still wouldn't count on OFS being the answer, until somebody explains to me how the app works and what kind of backups will give you appropriate restore and DR capability. (ANd then TEST to make sure the restored version is viable.) On 1/16/08, Zoltan Forray/AC/VCU [EMAIL PROTECTED] wrote: FWIW, I don't think it has ever been installed on any of our 200 Windows systems we backup. FYI, installing either of these WILL REQUIRE a reboot since it installs a service/low-level driver. Zoltan Forray Virginia Commonwealth University Office of Technology Services University Computing Center e-mail: [EMAIL PROTECTED] voice: 804-828-4807 Ben Bullock [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 01/16/2008 12:15 PM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject [ADSM-L] Windows Client question... Howdy, I recently switched jobs and now am managing TSM in a mostly Windows environment (instead of the Unix world where I am comfortable). A new challenge... anyways On the Windows TSM client, there is the option to install the Open file support and the Image Backup support. Does everyone install these? Does it depend on what kind of DR you might have to do on the windows host? Forgive my Windows ignorance, I've read the manuals and it looks like the upside is the ability to backup open files, but the downside I am seeing is that there seems to be a lot of errors with the way it interfaces with the Windows native VSS service. It also looks like if these are installed and you want to upgrade the TSM client, it requires a reboot of the Windows client to get it done. Nobody wants to reboot a production server to upgrade its backup software. So what is everyone's opinion?: - The Open file support is worth the hassle and should be installed on all TSM clients - The Open file support should be installed on certain systems (if so, what is your criteria). - The open file support is to much pain and should not be installed. Thanks, Ben The Blue Cross of Idaho Email Firewall
Re: HELP NEEDED ASAP!!
This won't help you now, but it may help someone else before crisis hits 1) As part of the documentation of the server, use either the natvie 'net share' command, or rmtshare.exe from the Windows Resource Kit to document your shares. Create a batch file that creates the shares and copy it off somewhere. 2) Potentially, periodically use the native xcopy command (xcopy /t /e) to create your (empty) directory structure elsewhere and then zip it down into a single file and back that up. Should take minimal space, and when unzipped, voila. 3) If permissions are important, my favorite tool is fileacl.exe - google for it, it's truly wonderful. The most wonderful thing about it is that it can create its own batch file to document and reapply permissions to a directory structure. Kurt | -Original Message- | From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] | Behalf Of | Dearman, Richard | Sent: Thursday, December 07, 2006 10:53 | To: ADSM-L@VM.MARIST.EDU | Subject: [ADSM-L] HELP NEEDED ASAP!! | | | One of oour main windows 2003 server crahsed today and the san disk it | turs out is corrupted and we need to restore 2TB of user | files to a new | server. | | The users cannot login to their workstations because this | server is used | in our login process and each user maps a home directory to a share on | that server when they login. I am in the process of creating | a backupset | so the restore can go quickly but our management needs the users to at | least be able to login even if there data is not restored yet. | | So if I start a restore will TSM recreate all the folders | with permissions | first then start putting the data back last? If we can get the folder | structure back first we can at least let people login. | | Does anyone know if TSM will put the folder structure back first with | permissions? | | Thanks |
Errors moving file from disk to tape
All, Running TSM 5.3.x on our Win2k machine, which is backing up data from our Win2k3 file serer. I've recently started dumping a database to the file server that's around 61gb in size, and the Win2k box seems to be choking while moving the file from disk to tape internally. The disk array for the Win2k box is not quite 2tb, on a 3ware array of 8 PATA drives. The database file is a full dump each night, given the same name each time. I'm not seeing errors in the event log that look interesting or relevant to this problem. Any thoughts? More info available if needed. Here are the error messages we're seeing: --Begin Log Snippet-- ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 8F0DA670 hdr version 37816 hdr length 62476 sequence number 101823309 data length 370C5960 server id 1536713424 segment id 532075705290595 crc C6B42145. ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 00148128 server id segment id 53513180. ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic 66371DED hdr version 31706 hdr length 48550 sequence number -1501832601 data length 7BDA67BD server id -630735450 segment id 13665746297275917947 crc A67BDA67. ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 0077 server id segment id 53517615. ANR1330E The server has detected possible corruption in an object being restored or moved. The actual values for the incorrect frame are: magic A4ECEAA6 hdr version 29637 hdr length 22108 sequence number 2145482599 data length D29CEB93 server id 426614096 segment id 15022471743897101349 crc 96D9D54C. ANR1331E Invalid frame detected. Expected magic 53454652 sequence number 0112 server id segment id 53600878. ANR1001I Migration process 27 ended for storage pool DISKPOOL. ANR0986I Process 27 for MIGRATION running in the BACKGROUND processed 124562 items for a total of 22,930,460,672 bytes with a completion state of FAILURE at 13:04:18. --End Log Snippet-- Thanks, Kurt Buff Lead Network Administrator Zetron, Inc. 425.820.6363 x463 [EMAIL PROTECTED] PO Box 97004 Redmond, WA 98073
Re: How to calculate the thoughput on the network
This will mostly be a function of the [avg latency/hop in WAN] and [# of hops in WAN] and [max throughput of slowest link in WAN] and [efforts made to tune packet size to avoid fragmentation - that is, adjusting packet MTU size to match WAN limitations]. For the last factor, if you're using Windows, or just for general information, see web pages that discuss DRTCP, a free Windows utility that allows easy access to various Windows settings in the Registry that control the TCP stack. Here's the fun part: Latency of any given hop in WAN will vary depending on load. If you have a exclusive link (like a point-to-point T1 or fiber link), then you have a much better chance of getting that reliable stats on latency than if you've got an IPSec VPN going over an Internet connection, because over the Internet you have no way of predicting load, unless you have an SLA with each entity between you and your destination. If your link is over an IPSec (or other) VPN over the Internet, I'd suggest multiple traceroutes over a period of time (days to weeks) to determine most likely route, including number and latency of hops. There's a tool called smokeping to automate and graph this, if you care to work with Open Source tools. Murugan, Palani said: | Hi | | I need to configure a node for backup through WAN. | | And they want to know the throughput on the network | | The data on the node = 20GB | | Could any of you tell how to calculate the throughput on the network ?
Re: Batch script in Windows to create filelist
| -Original Message-
| From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
| Behalf Of
| Richard Mochnaczewski
| Sent: Friday, August 18, 2006 08:07
| To: ADSM-L@VM.MARIST.EDU
| Subject: [ADSM-L] Batch script in Windows to create filelist
|
|
| Hi,
|
| I need to create a filelist of files that exist in a
| directory that have been updated in the past 7 days and have
| the list of files backed up by TSM. Does anyone know how tis
| can be done be commands native to Windows without requiring
| any third party software ?
|
| Rich
|
This will get you most of the way there, though something in vbscript might
be better.
Also, check the delimiters in the 'for' statement - I assume that you're
using -mm-dd for the regional seetings for your date format - it may not
be compatible with the input needed for the xcopy command.
-Begin Batch File-
@echo off
for /F tokens=1-4 delims=- %%i in ('date /t') do (
set DayOfWeek=%%i
set Year=%%j
set Month=%%k
set Day=%%l
set Date=%%i %%j-%%k-%%l
)
cd %%mydirectory%%
xcopy *.* /l /e /d:%%k-%%l-%%j c:\output.txt
-End Batch File-
Re: Power saving and TSM backups
Any way to integrate Wake-on-LAN to boot/shutdown systems? | -Original Message- | From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] | Behalf Of | Paul Zarnowski | Sent: Wednesday, August 16, 2006 19:02 | To: ADSM-L@VM.MARIST.EDU | Subject: [ADSM-L] Power saving and TSM backups | | | One way we are looking to save energy is to turn computers off at | night. As we typically run backups at night, this presents a | problem. We | would like to see a way that users could initiate a | backup/auto-shutdown as | they leave work for the day so that their computers aren't left on all | night. We estimate that the energy savings would be | substantial. Some | other backup products provide this capability. | | Has anyone else figured out a way to do this with TSM on | Windows, MacOS, | and Linux? | | Has anyone else wished that TSM had a way to do this? | | ..Paul |
Re: Keeping files in diskpools
Wanda Prather said... Well, the straightforward TSM way to keep files in a diskpool, is to remove the NEXTSTGPOOL value from the definition of the storage pool (so that the files have no place to migrate to), or set the HIGHMIG stgpool pool property to 100%, so that migration will never start. That's a possible but unlikely strategy, unless I can arrange to get that data to tape in an alternate fashion for offsite storage. The most practical way to do that, is to split your storage pools so that the client data you want to stay to disk all goes to one disk pool, and the other clients go to another pool that DOES migrate. Seems like segregating the storage pools by client is a good thing to do regardless. You can split the clients up by putting them in different domains, or by using management classes. Something to learn - I'll peruse the docs for that. I don't believe that we're doing anything like that at the moment. If you don't want to do that, but you want to know when your disk pool is getting full, you can use TSM Operational Reporter. You can add a line to the custom summary to tell you the disk pool utilization, based on a select statement: select pct_utilized from stgpools where stgpool_name='BACKUPDISK' And you can set a threshold for that value so that TOR runs every nn minutes, and sends you an email if pct_utilized is greater than, say, 90%. This does sound promising - more docs to read! Hope some of that is what you are looking for... Definitely Wanda Prather I/O, I/O, It's all about I/O -(me) Thanks very much for taking the time. I'm sure I'll have more questions later Kurt
Keeping files in diskpools
All, First time poster, fairly new to the whole thing, so help much appreciated. We've got a TSM server on which we've just upgraded the disk array, from 1TB to 2TB. It also has a Spectralogic Treefrog unit with two AIT2 drives and a 15-slot robot. We're looking to keep the current generation of files from our main file server in the diskpools, so that we (in the event of a meltdown of the fileserver) won't have to resort to tape. The amount of storage on the file server is roughly 1TB - the other servers are only a small fraction of that. We've kept the old diskpools, and created new ones to catch new data. The file server currently has its storage divided into two partitions. I'm reconfiguring the array on the file server to add space, and I'm going to switch to a single large partition, and change the drive letter so that the TSM server will pick up all of the files on the reconfigured array as new. (I've got a copy of the data on a test machine, done with robocopy, to retain all of the ACL information, and will be copying the data back after the production file server is reconfigured.) Is there some way 1) to fix those files in their diskpools, or 2) get notification if they start to migrate to tape and/or 3) get notification if space in the diskpools is such that files from the file server are likely to migrate to tape? The version for TSM shown at the CLI interface is Version 5, Release 1, Level 5.0. Thanks, Kurt Buff Sr. Network Administrator Zetron, Inc. [EMAIL PROTECTED]
