Title: | Technical issues concerning SAP/R3 OSF1 |
Moderator: | EUSACT::MICHAELIS |
Created: | Fri Dec 17 1993 |
Last Modified: | Thu Feb 20 1997 |
Last Successful Update: | Wed Feb 26 1997 |
Number of topics: | 412 |
Total number of notes: | 1550 |
Concept for backup with backint interface ? DB=Oracle A customer has move his backup from brbackup with normal tape devices (TZ87) to brbackup with a TL810 via the backint interface. Everything works well and perfectly automatic. But their is a lack of security because all backups (brbackup and brarchive) and are written to a pool of predefined tapes. The pool has write access to all tapedevices (nrmt0h - nrmt3h) of the TL810. So the backup files (datafiles from DB) and the archive files from up to four days are saved to the same tapes. That means in worst case the saved datafiles and the saved archivefiles of the last four days are lost if one of the four tapes is damaged. The customer wants a backup-set (four tapes) for every day of the week (Mo-Fr) and a extra tape for the archivelogs. The only idea I have is to create six initfiles (init<SID>.mon - init<SID>.fri + init<SID>.arc) for brbackup and six initfiles for the backint interface to start brbackup via crontab with the specific initfile for the day. Is there any other solution or experience about this problem. Andreas
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
411.1 | backint? | USCTR1::ASCHER | Dave Ascher | Tue Feb 18 1997 15:25 | 5 |
how is backint related to using a tl810? Is he using Networker to talk to the tl810? what version of backint is being used? the 'official' product version or something else? | |||||
411.2 | backint V1.0 | HAMSUP::WESE | Wed Feb 19 1997 11:07 | 9 | |
Hello Dave, the customer is using NSR V4.2A and backint V1.0. This is the first from SAP certified version. We got the backint SW as a external field test from Diane Adams. Thanks Andreas | |||||
411.3 | USCTR1::ASCHER | Dave Ascher | Thu Feb 20 1997 15:04 | 35 | |
If I understand you properly the problem is that the customer wants to use a separate backup tape pool for each day's backups and antother pool for the archive logs. I've still not been able to get my hands on a specification or any other kind of document about the 'official' backint, however, I thought that that backint did allow at least for definition of one tape pool for archive logs and another for db backups. I'd have thought that that much separation of the backups to different pools would be more than sufficient. A customer has move his backup from brbackup with normal tape devices (TZ87) to perfectly automatic. But their is a lack of security because all backups (brbackup and brarchive) and are written to a pool of predefined tapes. The pool has write access to all tapedevices (nrmt0h - nrmt3h) of the TL810. So the backup files (datafiles from DB) and the archive files from up to four days are saved to the same tapes. That means in worst case the saved datafiles and the saved archivefiles of the last four days are lost if one of the four tapes is damaged. The fact that the pools can have their tapes on any of the devices is not relevant. The 'normal' use of the restriction of a pool to a subset of the tape devices is that you have one additional tape drive, say a DAT tape, that you want to use for the archive logs... so you restrict that pool to only the one drive. I'm not understanding the 'loss' scenario. Is the concern over the loss of a particular indiuidual tape? the whole set of tapes? the tl810? If you define one pool for archive logs and another for backups what is the need for separate ppols for each day? |