ISM and file-type device cloning questions

I'm am working on integrating what was a standalone IDS 9.40 on Solaris system in a remote office to new location in a large office where there is an enterprise backup system installed (the IT managers don't want to spend the big bucks for the Informix add-on because the Informix based application may go away in a few years). Anyways, our previous (current) backup method was onbar to an 8mm Exabyte Mammoth tape (20 Gb raw capacity) and backups took 6 or 8 tapes for a full backup. Now we have an NFS mounted partition of a few hundred gigabytes available with the idea that we do a onbar -b to an ISMDiskData pool and then we give a unix file system path the enterprise storage backup administrator to have the unix files backed up to tape. So, new to this way of doing things, I hoped I could just delete the files after they were backed up to tape (I haven't done this file backup yet). But, reading the ISM admin book, I see that it wants me to do cloning, on page 3-9 I see the text "Once a file-type device is full, you must clone the data to tape before you can overwrite the file-type device with new data". It seems to want me to write the file-type device data to an Informix tape device. But what I want to do is have the "enterprise tape backup system" do the backup which is not Informix-aware and is just backing up a unix file system path. So, Question #1: Do I really have to do cloning or will I be able to use a non-cloned restore if it is later restored from tape to a unix file system path ? (if I just rm the directory with the ISMDiskData files after they are in a unix file system backup tape). And Question #2, on the bottom of page 3-9 there is the text: "You cannot clone bootstrap records. Bootstrap records are always backed up to the ISMData volume pool, even when all other data is backed up to ISMDiskData or ISMDiskLogs". Does this mean ISM always has to scribble some information to a tape drive ? Thanks for any help and advice. Cedric

You do not have to clone. Backup the files to tape and them use onsmsync with the -g option to keep N generations of backups on disk. I believe each ISM volume is a directory or file when done to disk. (It should be obvious which). There should be a way to get onbar to recognise the new volumes if you restore the files back from tape. Raise a support call with IBM or play and figure it out yourself.