Parity Error Rdb Rmu
GoogleВойтиСкрытые поляПоиск групп или сообщений
tapedrives (TZ887 on HSJ40) to direct attached COMPAQ SuperDLT1 drives for our Rdb-databasebackups using RMU-backup under SLS. VMS: 7.2-1H1 / Rdb : V7.0-6.2 / SLS V2.9 F Performance inprovement was spectacular : In some cases we went from a 4 hour 30 minutes to about 25 minutes of total backuptime. That's great of course.... But we seem to have a problem with reliability for this SDLT-solution: We started with a tapepool of about 130 COMPAQ Super DLTtape 1 (=dark green). About 5 tapes were faulty already during the first initialize in SLS and had to be replaced. We normally do 4 different databasebackups a day, 7 times a week. The 4 databases are quite large (between 55.10E6 blocks and 65.10E6 blocks) In https://groups.google.com/d/topic/comp.os.vms/43uXRvUCaaY 4 months time I replaced 4 other tapes and experienced about 20 Parity errors on 4 different drives and with different tapes. And these tapes are NOT cheap !!! The different drives are weekly cleaned with an appropriate cleaning tape. Any explanation why this tapesolutions seems so unreliable compared with my former CI-based config ??? Any suggestions are very welcome. Polite greetings, Systemengineer Delight Information Systems Archimedesstraat 7 bus 6 8400 Oostende Tel: 32(0)59/554.547 Fax: 32(0)59/806.888 Top SDLT http://www.verycomputer.com/30_5c0d4ec76beba7b5_1.htm parity errors by Jack Trachtma » Sat, 30 Mar 2002 06:54:09 Just for comparison, we are evaluating a Compaq MSL5026 SDLT jukebox. It came with 6 new (green) tapes. Of these, 3 were bad. Two could be physically loaded but a VMS INIT command would just hang! The third would cause the drive to continuously try to complete loading!!! We purchased a batch of 20 new cartridges and all inited w/o problems. > Hi there, > A simple question concerning SDLT drives and tapes (Super DLTtape I). > We switched quite recently from CI-based tapedrives (TZ887 on HSJ40) to > direct attached COMPAQ SuperDLT1 drives for our Rdb-databasebackups using > RMU-backup under SLS. > VMS: 7.2-1H1 / Rdb : V7.0-6.2 / SLS V2.9 F > Performance inprovement was spectacular : In some cases we went from a 4 > hour 30 minutes to about 25 minutes of total backuptime. That's great of > course.... > But we seem to have a problem with reliability for this SDLT-solution: > We started with a tapepool of about 130 COMPAQ Super DLTtape 1 (=dark > green). > About 5 tapes were faulty already during the first initialize in SLS and had > to be replaced. > We normally do 4 different databasebackups a day, 7 times a week. > The 4 databases are quite large (between 55.10E6 blocks and 65.10E6 blocks) > In 4 months time I replaced 4 other tapes and expe
failure. REFERENCE Please contact the Data Center Supervisor to clarify any process within this procedure and for any concern beyond its scope. OVERVIEW and PROCEDURE A VMS D2T XXXX Backup job creates a VMS backup of an RMU disk-to-disk backup of http://www.wordwonk.com/Policies_And_Procedures/WebHelp/Procedures/VMS_D2T_Production_Or_Franchise_Backup_Failure.htm either the T2 Production database (PROD) or the T2 Franchise database (FRAN). This job is automatically submitted on HOLD status on the DBA$MARLIN queue once the corresponding RMU_D2D_XXXX_Backup job successfully completes. The most common causes for a job failure are media errors (most likely) or hardware problems with the tape drive. Whatever the type of error, the cause must be corrected and the backup job must be resubmitted to the DBA$MARLIN queue in HOLD status. To find out parity error what went wrong with a backup job, locate the following >LOG file and look at the end of the file. The error message will be there, just before the job execution summary information: MIS:[MIS>DBAMGR]VMS_D2T_PROD_BACKUP.LOG; or MIS:[MIS.DBAMGR]VMS_D2T_FRAN_BACKUP.LOG; If the problem is a media / parity error, it was probably caused by defective or damaged tapes. Replace them with new tapes and retry the backup procedure. If the error message does not indicate a media or parity error, you can parity error rdb retry the backup job in a different MARLIN tape drive. Notify VMS systems support. If the problem is a media /parity error, you must resubmit the job. First, make sure that you have two available sessions (in KEA! or DECTERM). These sessions should be connected to MARLIN, DOLFIN or CANES (does not matter which). Log in as OPERATOR on both sessions and leave them at the VMS command prompt (ready to type a VMS command). On the first session (window), type the following at the VMS command prompt: SET DEFAULT MIS:[MIS.DBAMGR] EDIT/READ RMU_D2D_abcd_BACKUP.LOG where abcd = PROD (if the PROD job failed) or abcd = FRAN (if the FRAN job failed) Locate the SUBMIT command at the very end of the file. The SUBMIT command will have the following format (the values will be different in the actual file than those from this example): $ Submit- /keep- /noprint- /notify- /queue=dba$marlin- /hold- /log- /user=dbamgr- /param= ($30$MKC300, PROD011209.RBF)- dbamgr$rdb:VMS_D2T_PROD_BACKUP.COM Once you have found the SUBMIT command, you can either: Copy and paste all of it from the DECTERM or KEA! Sessionj window into the other available KEA! Or DECTERM session, or Simply type the command exactly as shown in the .LOG file. Press RETURN/ENTER if necessary to submit the job. Exit the editor without saving the LOG file (type Ctrl-Z followed by QUIT). At this point the job should be ready for release o
be down. Please try the request again. Your cache administrator is webmaster. Generated Mon, 24 Oct 2016 01:38:55 GMT by s_wx1011 (squid/3.5.20)