I can see your point about the Qtrees and binding the different management classes, etc. As for our TOC, even at 30mins I find it painfully slow. Thank fully our TSM backup of the NAS is really only for DR purposes, nearly 99% of data restore requests are fullfilled through Snapshots, so it's no(I hope)going to be often I have to sit and wait for the TOC to load. It's on a RAID 5 array at present and I was considering moving it onto it's own RAID 0 array to see if that speeded it up any.
Regards, Iain Barnetson IT Systems Administrator UKN Infrastructure Operations -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: 22 March 2005 16:40 To: [email protected] Subject: Re: [ADSM-L] TSM 5.3 new goody Iain, 30 minutes for your largest TOC to load? That seems better than what we have seen in testing. I've sat for 2 hours waiting for one to load that never did. Perhaps it is the number of files, type of hardware, etc. Yes, there would be more TOCs but the overall size should be the same, as there is the same number of files, no matter how you slice it. The other thing I think that q-tree level backups will let us do is keep some qtree's data for longer/shorter than other data. It looks like I could bind different q-trees to different management classes and not have to keep all the data on the volume for the same time period. In fact, we have some q-trees that are temporary areas that change all the time that we do not want to backup at all, but they are on the same volume as some data we do want backed up. A q-tree backup is the only way we can get around this one. In our case, the Q-tree backup ability is a requirement if we want to move to NDMP. My 2-cents. Thanks, Ben -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Iain Barnetson Sent: Tuesday, March 22, 2005 8:59 AM To: [email protected] Subject: Re: TSM 5.3 new goody Yeah, you're not alone with the amount of data or size of volumes. But we don't as yet have an issue with the time it takes to backup, We've approx 6Tb of data to backup, which we do a full on a Sunday and Diff's weekdays. A monthly full on a Saturday with a separate TOC. I'm already having a bit of an issue with our TOC, approx 30 mins to load for our largest volume of 1Tb. Our main TOC pool is a disk based 25Gb STG which is 25% full. So, if you have a separate TOC's for all your Qtree backups that must be a lot of TOC's. Although I can see what you're saying about the speed of TOC being better by more smaller backups, at present it wouldn't be enough for me to go to a Qtree level backup. Unless there's some other reason? Regards, Iain Barnetson IT Systems Administrator UKN Infrastructure Operations -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: 22 March 2005 15:49 To: [email protected] Subject: Re: [ADSM-L] TSM 5.3 new goody Iain, We have some very large volumes (1TB+) that have 10s of millions of files. If we were to back them up using NDMP at the volume level, it would take a long time and create a HUGE table of contents. TOCs for NDMP are not kept in the database, but in a special disk pool. When you want to restore an individual file from an NDMP, TSM has to read in that TOC, which could take a long long time with these very large volumes. By being able to go down to the q-tree level, we divide the large volume into more reasonable chunks so that the NDMP backups don't take as long and the TOCs may actually load in a reasonable time. Ben -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Iain Barnetson Sent: Tuesday, March 22, 2005 2:07 AM To: [email protected] Subject: Re: TSM 5.3 new goody Ben, I'm kinda new to TSM & NetApp and I'm wondering what the advantages of doing Qtree level backups are? I do a NDMP backup of the filers complete which still allows me restore right down to specific files. Regards, Iain Barnetson IT Systems Administrator UKN Infrastructure Operations -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Ben Bullock Sent: 21 March 2005 16:30 To: [email protected] Subject: Re: [ADSM-L] TSM 5.3 new goody FYI... I'm currently testing this new feature. The 'virtualfsmapping' works great on normal NetApp qtrees. It's really the feature we have been waiting for to go to NDMP with our filers and in testing we can get NDMP backups at the qtree level or even lower. The issue we are currently working through with support is that this feature does not seem to work on our Snapmirrored volumes. i.e. We have 11 NetApp filers that we snapmirror to a monster R200 offsite for DR purposes. We are attempting to do NDMP backups off of the snapmirrored volumes (using the virtualfsmapping to get Q-tree level backups). We would much rather run the backups off the R200 than the production filers. TSM seems to be able to get the qtree backed up, but it fails to get a TOC, which we really need. We are still not sure it is a TSM or a NetApp problem, but I am getting proficient in running both TSM and NetApp traces. ;-) Ben -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stapleton, Mark Sent: Monday, March 21, 2005 9:17 AM To: [email protected] Subject: TSM 5.3 new goody (from the Windows Administrator's Guide, page 87) Directory-Level Backup and Restore If you have a large NAS file system, initiating a backup on a directory level will reduce backup and restore times and provide more flexibility in configuring your NAS backups. By defining virtual file spaces, a file system backup can be partitioned among several NDMP backup operations and multiple tape drives. You can also use different backup schedules to back up sub-trees of a file system. The virtual file space name cannot be identical to any file system on the NAS node. If a file system is created on the NAS device with the same name as a virtual file system, a name conflict will occur on the Tivoli Storage Manager server when the new file space is backed up. See the Administrator's Reference for more information about virtual file space mapping commands. Note: Virtual file space mappings are only supported for NAS nodes. -- Mark Stapleton ([EMAIL PROTECTED]) Office 262.521.5627
