Bill, From what I read on your thread you are only keeping 30 days worth of backups. You may already know this, but the fromdate and todate on the export pertain to when the backup was taken, not the timestamp of the file. I'm sure you know this, but I want to be sure.
That said, your current command will not really export much, because it is trying to export everything older than 30 days. I don't suspect that you will get much, if anything, exported with a retention of 30 days. To be fair, I can't remember if it was 30 days, or 30 versions, but either way, I would set the export to run for something like 20 days ago vs 30 to be sure that you capture the range that you are looking for. Also, you don't have to specify a fromdate. By default it will get everything. Therefore, I would do just todate=-20. Are you actively restoring data, or is this just data on hold for future restores? The reason I ask, is that it might make sense to go ahead and restore this data somewhere if it is going to be recalled anyway. Hope this helps, Gary Itrus Technologies On Aug 19, 2009, at 11:49 AM, Bill Boyer wrote:
What I came up with was to EXPORT the data. Since their original retention was 30-days, I figure that if I exported all the nodes' data > 30- days I would be covered. This is the EXPORT I came up with: export node * filespace=* domain=nobel filedata=all dev=lto fromdate=12/17/2007 todate=-30 preview=no The FROMDATE is the day the TSM server was installed. Don't know when we started backing up data for this client, but that date should cover any time period. Basically from inception of the TSM server instance to 30- days ago. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ochs, Duane Sent: Tuesday, August 18, 2009 4:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Need some how-to assistance please You only had a 30 day retention policy... If the data was deleted you could only go back 30 days. This doesn't seem to difficult an issue. For that much data and that many nodes just run an archive on each system. If they "must" have the data that is already saved... I'd say best bet is backups sets. I don't think backupsets can be created for SQL TDP clients though. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bill Boyer Sent: Tuesday, August 18, 2009 3:26 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Need some how-to assistance please Current primary storagepool occupancy is 8.9TB. 32 nodes in the domain with 8 of them being TDP SQL agent nodenames. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Ochs, Duane Sent: Tuesday, August 18, 2009 3:32 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: Need some how-to assistance please How much data are you talking about ? -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Bill Boyer Sent: Tuesday, August 18, 2009 2:29 PM To: ADSM-L@VM.MARIST.EDU Subject: Need some how-to assistance please History.have a client backing up with a 30-day retention policy (vere=nolimit rete=30) and last week they came as requested that the retention be change to No Limit across the board. Keep everything. Lawyers involved. Now they feel that the resource requirements for doing that for an indefinite period are more than they want to take on. So they asked that the retention be set back to 30-days , but..and here's the fun part.they want to tapes with the oldest backup data to be kept. You can see they have to concept of TSM and are thinking of keeping the oldest full backup tapes around so they could be re-cataloged if a restore is needed. So my problem/question is how do I accomplish the same thing? Was thinking EXPORT NODES, but what date range to use. Backupsets (no, I'm not 6.1! J) isn't what I want either. Any suggestions? Bill Boyer "He who laughs last probably made a back-up." Murphy's law of computing