Hi Sigrid, > when performing a backup/restore of an R/3 SAP DB database > using Legato > Networker we achieve a data throughput of about 20GB/h during > backup and > 15GB/h during restore. > > As our system is (only) equipped with a 100Mbit/full duplex > network card, > the card is 100% busy during backup/restore - so using > parallel mode seems not to be an option.
Are you sure, that it is 100% busy? I'm no expert with Networks but I always thought 100Mbit/s=12.5MB/s=45GB/h. Even with network protocol overhead that is much more than your 20GB/h. > Does anyone have an additional idea about > - speeding up backup and (most urgently) restore > - using data compression in this environment? As SAP DB is able to perform backups to pipes (which is used anyway with External Backup Tools like NetWorker), you could plug-in a compression tool between database and NetWorker's save/recover commands. Although, you would be forced to organize the usage of compression tool and NetWorker by yourself. > A second but related problem is the fact that - when having lost the > datafiles e.g. through a disk crash - the datafiles have to be rebuilt > before being restored (this takes about 12min/8GB datafile, > at least in our > configuration). During this time the tape drives are already > blocked. Is > there any way to avoid this e.g. split the rebuild and the > restore process? That is an interesting observation, but unfortunately there is only one way of splitting that. Backup your log in database mode COLD, do an "Initialize Configuration" aka "Init Config" and restore Data and Log. But I guess that is not faster than the normal way. > Thanks for ideas and special thanks to everyone having > answered my questions > already although I put them in GERMAN (shame on me), I Could not see any replies to the list, guess I need new glasses. Best regards, Tilo Heinrich SAP AG, SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
