Active/inactive backup versions are processed the same, whether they came from an incremental or from a selective backup.
So yes, if you normally keep only 2 versions, and do: March 1 selective March 2 incremental March 3 selective Assuming the file changed and the March 2 backup DOES send a backup version to the server: after the backup on March 3, you have ONLY the versions from March 2 and March 3. If the file didn't change after the backup on March 2, then you have two identical copies. -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 4:27 PM To: [EMAIL PROTECTED] Subject: Re: DataBase File Spaces and Selective Backups Actually, the question is, if the include is not there will an incremental backup expire our selective backups that specified what is on the include? Inclexcl contents: exclude /fsmountpout/.../* DSMC Commands: incr /fsmountpoint selective /fsmountpoint/flatfilepath/flatfile.backup Will the above expire the inactive backup revisions? And if it does will the selective reinstate them? I know this sounds crazy but we have a very good reason for doing this. Occasionally, the modified dates on files are not changed. The way we want do our DR media rotations of database files requires everything to get backed up. A Selective guarantees this. -----Original Message----- From: Alex Paschal [mailto:[EMAIL PROTECTED]] Sent: Monday, February 25, 2002 2:21 PM To: [EMAIL PROTECTED] Subject: Re: DataBase File Spaces and Selective Backups Paul, exclude /fsmountpoint/.../* include /fsmountpoint/flatfilepath/flatfile.backup Ah, in NT-ese, exclude f:\...\* include f:\flatfilepath\flatfile.backup This way you'll be doing an incremental of the filesystem, but the only thing you should actually backup are your flat file backups. Would that accomplish your objectives? Alex Paschal Storage Administrator Freightliner, LLC (503) 745-6850 phone/vmail -----Original Message----- From: Seay, Paul [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 24, 2002 7:20 PM To: [EMAIL PROTECTED] Subject: DataBase File Spaces and Selective Backups Right now we do a lot of our database backups offline without a TDP. Many of these will stay that way because they are very small databases and setting up the TDP is just too much work and cost. However, we are concerned about what this means from a filespace and backups point of view. First of all, because we never perform an incremental against these filespaces we have no filespace statistics. Second, it is very difficult to monitor selective backups because you have to search the backups table for the entire filespace name and pick the last backup from it to get something similar. We have excepted these restrictions but we started thinking about what does this mean if an incremental accidentally got run so we are considering another approach. We believe we should be doing an incremental on every database filespace no matter what except do an exclude of every file, not directory, but file, ie. do not use the exclude.dir. However, we are concerned that this may expire all the selective backups. Before we tried it we thought we would ask what everyone else is doing. The other option would be to do a selective and then an incremental which would backup nothing because it did not change. There are only 150 files max in these filespaces anyway, so it is no big deal. You may wonder why we want to do it this way. Our plan is to segregate the database storage pools here so we can eliminate the reclamation churn. Basically, everything would expire all at once and the tape would be immediately empty. However, to make that happen, we must backup everything every time. 99% of the data files change anyway so incremental would do nothing. Paul D. Seay, Jr. Technical Specialist Naptheon, INC 757-688-8180
