Just after brrestore starts, when it tells you that '<filename> will be deleted (or overwritten, if cloning)' -- it goes when you type 'cont' and hit enter. This is normal mode for brrestore from 3.0D. If you invoke brrestore with "-c force" you won't even have to type 'cont'. Note that this is all part of the cleanup routine done by brrestore before starting backint -- and backint is the utility that checks to see if the files actually exist.
This would be an SAP issue, but don't expect them to do much here. Tom Kauffman NIBCO, Inc > -----Original Message----- > From: J Sorensen [mailto:[EMAIL PROTECTED]] > Sent: Friday, August 09, 2002 6:11 PM > To: [EMAIL PROTECTED] > Subject: failed brrestore deleted my entire SAP database > > > I ran the brrestore and the restore failed due to the files > not being available on the server. That was due to them > having expired. However, the brrestore deleted all of my > database files on the server. Not only was I not able to > restore what I wanted, brrestore deleted what I had!! > > I opened a ticket with Tivoli. They concluded it was SAP' s > brrestore that was responsible and suggested I contact SAP. > > Has anyone else ever heard of this? Is it supposed to work > this way? I think this is a really bad thing.... > > Thank you...... > > My environment is as follows: > > TSM server version 4.2.2.4 > > TSM server os Aix version 4.3.3 ml 06 > > TSM client os HP/UX 11 > > TSM Client version 4.2.1 > > SAP TDP version 3.2.0.8 > > SAP brrestore version 3.1I > > > > --------------------------------- > Do You Yahoo!? > HotJobs, a Yahoo! service - Search Thousands of New Jobs >
