Error 1722: The RPC Server is Unavailable - Disaster Recovery of CAS
Good Day Pros, I got an error which is reffered to the image below when I'm trying to restore the BackExec DB of Original CASO to the D.R Server: I simply follow the steps regarding this link below when performing D.R: https://vox.veritas.com/t5/Backup-Exec/How-to-backup-Backup-Exec-itself-and-how-to-restore-it/m-p/311908#M184173 I also installed the options needed in the D.R server and when i opened the console, i noticed that the D.R server's console configurations appeared as the same as the old CASO. After that, i run the BEUtil to restore the database which i copied from the old CASO server, and the error occurs. I've search for the Error, check the windows services regarding RPC and DCOM but the options in the properties of those are grayed-out (e.g. start , restart, stop ,etc.). Did i missed some step/s regarding this scenario and leading to this error? Any help would be appreciated Use: Windows Server 2012 R2, Backup Exec 16 - Central Administration Server Regards, JakeAutoloader goes offline by drive calibration (Quantum V700, LTO-9)
We changed a LTO-6-Library against a new LTO-9 Autoloder. A new tape is shown as "unknown media" and the capacity "0 Bytes used" with a green bar that the full tape can be used. New for us is the experience that each new tape we loaded into the 16-slot-magazine will need a calibration when the tape is "inventoried" the first time. When we start the inventory, the tape will be moved to the picker and the loader shows "calibrating" in the display and in the Onboard-Management console. After ca. 2 minutes the loader goes offline and Backup Exec shows both drive and loader offline. We did make them online again, but the calibration goes further on. After some hour, the drive will load the tape and then we can move the tape by move-command in the management of the loader (we did not try the onboard-management) to the slot, where it comes from. After this we make a "read slot" and the tape will be shown in the slot. Then we start inventory for this slot again, and the tape will go over the picker to the drive, loaded and unloaded and then the tape return to the slot automatically. The tape is shown in Backup Exec as "empty Medium" and the capacity is shown as "0 Bytes used of 16,4 TB". Now we can use the tape for backup-jobs. No error and no offline will occur. But whenever we start an inventory for a brand new tape, the drive and the loader goes offline. We think, this is a time-out-error, because the inventory in the drive continues without error. But the time, how long backup-Exec is waiting for an answer for calibarting is to short, so it make drive and library offline. Is this correct? Can we adjust manually the parameter for the time-out (Registry?)? Is there another reason, why the machine goes offline? In the "bengine_AlwaysOnLog_2022-09-22_10-49-31.log" we can find: [2556] 2022-09-21T18:40:59.990 [tpfmt] - TF_GetTargetMediaDeviceInfo(): Execute(ADAMM_MOVER_EXECUTE_GET_SERVER_INFO) failed. mvrRet=87. In the beginning, we did only disable the tape0 (LTO-6), but at the end the device was switched off, removed from SAS-Connector and deleted from Backup Exec. The error consists. By the way, all drivers are current. The library and the drive are shown correct in device manager. JuZe
Tape spanning and overwrite-append protection
I am having some difficulties with tape spanning, and I've traced it down to the overwrite protection period. What I'm trying to do is have the overwrite protection period long enough that it won't overwrite the first tape in a tape span. The issue I've come across is that I think it's too long and the overwrite/append protection is still in place when an append job starts a couple of days later. What I am wondering is a) Does the overwrite/append protection period start when the job STARTS or when the job ENDS. This will help dramatically trying to plan this out. I found a couple articles through the search but it describes everything but that. b) The only other thing I can think of is have a tape job that erases all tapes present in the drives run before the main jobs start, this will definitely fix the problem but this seems like a sledgehammer approach to me. Thoughts?
