Hi Dirk, the backup node admin command has a mgmtclas parameter. You could put the full backups to a separate mgmtclass which keeps it long enough.
For scheduling fulls I suggest you prefix the vfs mapping name with some indicator of a cycle like cycle01/filespace. the a script could check the date and run a full when the cycle comes around. Regards, bill Colwell > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf > Of Dirk Kastens > Sent: Thursday, October 04, 2007 8:53 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: backup nasnode questions > > Larry, > > thanks for your reply, but: > > > Per the TSM 5.4 Admin reference: If you backup up at an attached > library > > you > > need to create a copypool with the same NDMP data format...in your > case > > NETAPPDUMP. In other situations, the format needs to be NATIVE. > > I backup directly to the TSM server. There is no library or drive > attached to the filers. > > > verexists refers to active copies. What is your retain extra set for? > The > > full may still exist as an inactive file. If you want a full and two > > incrementals active you'll have to change your verexists value. Do a > query > > with inact=yes to see if the full is still available for restore. > > The "q nasbackup" command doesn't have an "inactive" option. When I set > the verexists=2 option, after the first backup, the full image is the > active version. After the second backup, the full image changes to > inactive and the differential is the active version. After the third > backup, the first differential changes to inactive and the second > differential is active. The full backup has disappeared from the list, > although it must be there because the differential depends on the full > backup. I don't see a command that can list the expired full backup. > On the other hand, I don't want to keep 14 differential backups until I > make the next full backup. I just want to keep (and see) the full > backup > and the last two differentials. > > > Scheduling full backups every two weeks: Use a separate schedule for > full > > backups with a perunits=weeks period=2 > > Yes, but I don't want to backup the whole filer once every two weeks. I > want to backup vol1 on Monday, vol2 on Tuesday, and so on, what means, > that I had to define a single schedule for each filesystem. My idea was > to set an options on a filespace that automatically arranges a full > backup after a defined number of days. So I only need one schedule with > the "backup node" command, TSM looks up the date of the last full > backup > of each filesystem and handles the next full backup dependent on the > defined option. > > -- > Regards, > > Dirk Kastens > Universitaet Osnabrueck, Rechenzentrum (Computer Center) > Albrechtstr. 28, 49069 Osnabrueck, Germany > Tel.: +49-541-969-2347, FAX: -2470
