ISM backups query
Can't seem to find the info anywhere for this one. I'm testing ISM for many obscure reasons; I've got it configured (eventually!) for backup to disk, which will be used as a staging area from whence the resulting files (and the bootstrap files, of course) will be sent to tape. I have actually managed to get some level 0 backups to run using a dbspace list file to define which dbspaces to back up; on completion, there is a file in the DiskData path for each dbspace backed up, the filename for each dbspace having a unique identifier, and I can cross- reference the files to the dbspaces they refer to by checking the bar_act log and the ixbar file. So far so hoopy. But there are always a couple of extra files created after the backup (and numbered consecutively with the dbspace and logfile file numbers) which I assume are necessary for restore purposes that I can't seem to find referred to in any of the log files I mentioned. Any idea what they might be and how I can script something to record their names to ensure they're not left out when I save everything to tape? Cheers
On Jul 26, 2:25 pm, Malc <mal...@googlemail.com> wrote: > Can't seem to find the info anywhere for this one. > I'm testing ISM for many obscure reasons; I've got it configured > (eventually!) for backup to disk, which will be used as a staging area > from whence the resulting files (and the bootstrap files, of course) > will be sent to tape. > > I have actually managed to get some level 0 backups to run using a > dbspace list file to define which dbspaces to back up; on completion, > there is a file in the DiskData path for each dbspace backed up, the > filename for each dbspace having a unique identifier, and I can cross- > reference the files to the dbspaces they refer to by checking the > bar_act log and the ixbar file. So far so hoopy. > > But there are always a couple of extra files created after the backup > (and numbered consecutively with the dbspace and logfile file numbers) > which I assume are necessary for restore purposes that I can't seem to > find referred to in any of the log files I mentioned. > Any idea what they might be and how I can script something to record > their names to ensure they're not left out when I save everything to > tape? > Cheers Oh hang on; one of them's referred to in the bootstrap notification email that comes out (well the email has a number in it that corresponds to one of the file names) but the other one is still a mystery. Still looking...
On 26 July, 14:36, Malc <mal...@googlemail.com> wrote: > On Jul 26, 2:25 pm, Malc <mal...@googlemail.com> wrote: > > > > > Can't seem to find the info anywhere for this one. > > I'm testing ISM for many obscure reasons; I've got it configured > > (eventually!) for backup to disk, which will be used as a staging area > > from whence the resulting files (and the bootstrap files, of course) > > will be sent to tape. > > > I have actually managed to get some level 0 backups to run using a > > dbspace list file to define which dbspaces to back up; on completion, > > there is a file in the DiskData path for each dbspace backed up, the > > filename for each dbspace having a unique identifier, and I can cross- > > reference the files to the dbspaces they refer to by checking the > > bar_act log and the ixbar file. So far so hoopy. > > > But there are always a couple of extra files created after the backup > > (and numbered consecutively with the dbspace and logfile file numbers) > > which I assume are necessary for restore purposes that I can't seem to > > find referred to in any of the log files I mentioned. > > Any idea what they might be and how I can script something to record > > their names to ensure they're not left out when I save everything to > > tape? > > Cheers > > Oh hang on; one of them's referred to in the bootstrap notification > email that comes out (well the email has a number in it that > corresponds to one of the file names) but the other one is still a > mystery. Still looking... Run ism_show -volumes