| Title: | NetWorker |
| Notice: | kits - 12-14, problem reporting - 41.*, basics 1-100 |
| Moderator: | DECWET::RANDALL .com::lenox |
| Created: | Thu Oct 10 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 750 |
| Total number of notes: | 3361 |
Hi
The 'NetWorker Save and Restore Application Interface for SAP/R3 v1.1
Administrator's Guide' mentions, on p.17, that "sapclone uses
"nsrclone" to initiate the cloning operation'. Why is sapclone needed?
Are the savesets created by the NetWorker AI for SAP somehow different
than other savesets?
Thanks!
tl
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 538.1 | not really, but here's what goes on... | DECWET::EVANS | NSR Engineering | Mon Mar 31 1997 12:55 | 15 |
As you guessed, sapclone is a shell script that automates/simplifies access to cloning of SAP savesets. Since SAP provides a list of files to the save operation, which the SAP R/3 interface application passes through to a NetWorker save command, the SAP data is saved in normal NetWorker savesets, but with ID's like "backint:ora<SID>" (SID = ORACLE_SID, and "ora<SID>" is, per backint spec, the user ID doing the operation (save/restore)). When one wants to clone the savesets, sapclone gathers the interesting ones (default, last 24 hrs) via mminfo command (extracting the ssid's) and then issueing nsrclone...<ssid-list>. Legato was trying to be nice to the average NetWorker user, since SAP savesets had to be named differently than "normal" (eg, the save path). | |||||
| 538.2 | SANITY::LEMONS | And we thank you for your support. | Mon Mar 31 1997 13:17 | 6 | |
Ah! Thanks very much for the illumination. I copied sapv11.tar and
took a look at sapclone. I was concerned that these SAP savesets would
not fit into my automated clone procedure, but it looks like they will.
Thanks again!
tl
| |||||