Restore data old tapes Issues
hello im trying to restore data from old tape i follow the procedure fine (inventories, catalog, restore selection) each time i tries it ask for a tapes i insert it but it was ejected because it's not the good one it seems what can i do ? Thanks1.2KViews0likes9CommentsAutoloader 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. JuZe3.2KViews0likes9CommentsUnble to inventory in symantec
Dear All support Team, We have old Symantec backup 2012. So I am facing an issue recently when I insert old tape this error comes for restore. (Server: "I-S-BKUP") (Job: "Import Library 01163") Import Library 01163 -- The job failed with the following error: Physical Volume Library Drive or Robot paused, offline, or disabled. After getting this error, I check in the application in Windows Server, then I do not see the tape, so do you know any of them, then reply to me, thank you very much670Views0likes2CommentsUnable to create Deduplication disk
******************************************************************************** ***** SGMon log for \\\\backupsrvr ***** ***** Local Offset =-03:00 ***** ******************************************************************************** PVLSVR: [03/23/23 20:03:26] [6020] PvlMoverSession::CreateEntity: OST WORM - ServerFlags=0x107, MinInterval=0, MaxInterval=0 PVLSVR: [03/23/23 20:03:26] [6020] PvlEntityDatabase::CreateEntity() ParentEntityType = NULL_ENTITY_TYPE ParentEntityGuid = {00000000-0000-0000-0000-000000000000} EntityType = OST_SERVER_ENTITY_TYPE ServerGuid = {00000000-0000-0000-0000-000000000000}, "PureDisk:Backupsrvr:PureDiskVolume" PVLSVR: [03/23/23 20:03:26] [6020] [IsCloudStorage] Called with P PVLSVR: [03/23/23 20:03:26] [6020] [IsCloudStorage] Called with P. Returning 0 PVLSVR: [03/23/23 20:03:26] [6020] PvlEntityDatabase::CreateEntity() : SUCCESS! ServerGuid = {BD0487B4-C816-4895-A839-A26949F69B27}, "PureDisk:Backupsrvr:PureDiskVolume" PVLSVR: [03/23/23 20:03:26] [6020] PvlEntityDatabase::CreateEntity() : SUCCESS! PVLSVR: [03/23/23 20:03:26] [6020] PvlMoverSession::CreateEntity: OST WORM - ServerFlags=0x0, MinInterval=0, MaxInterval=0 PVLSVR: [03/23/23 20:03:26] [6020] PvlEntityDatabase::CreateEntity() ParentEntityType = MACHINE_ENTITY_TYPE ParentEntityGuid = {F89860D9-A8CE-4CC1-AD2F-60D7CAFD6EE4} EntityType = PDDE_CONFIGURATION_ENTITY_TYPE PDDE Configuration = {00000000-0000-0000-0000-000000000000}" PVLSVR: [03/23/23 20:03:26] [6020] PvlDevice::CheckDedupeMemory() - PureDisk:Backupsrvr:PureDiskVolume:I:\BackupExecDeduplicationStorageFolder: StorageTotal 1675GB, StorageFree 1675GB, PercentFree 99, MemoryTotal 56GB PVLSVR: [03/23/23 20:03:26] [6020] PvlEntityDatabase::CreateEntity() : SUCCESS! PDDE Configuration = {8DAAD452-5277-460F-BA5F-5A48DB9624C6}" PVLSVR: [03/23/23 20:03:26] [6020] PvlEntityDatabase::CreateEntity() : SUCCESS! PVLSVR: [03/23/23 20:03:28] [6020] PvlEntityDatabase::DeleteEntity() ParentEntityType = NULL_ENTITY_TYPE ParentEntityGuid = {00000000-0000-0000-0000-000000000000} EntityType = PDDE_CONFIGURATION_ENTITY_TYPE EntityFlags = 0000 PDDE Configuration = {8DAAD452-5277-460F-BA5F-5A48DB9624C6}" PVLSVR: [03/23/23 20:03:28] [6020] PvlEntityDatabase::DeleteEntity() : SUCCESS! PVLSVR: [03/23/23 20:03:28] [6020] PvlEntityDatabase::DeleteEntity() ParentEntityType = NULL_ENTITY_TYPE ParentEntityGuid = {00000000-0000-0000-0000-000000000000} EntityType = OST_SERVER_ENTITY_TYPE EntityFlags = 0000 ServerGuid = {BD0487B4-C816-4895-A839-A26949F69B27}, "" PVLSVR: [03/23/23 20:03:28] [6020] PvlEntityDatabase::DeleteEntity() ParentEntityType = MACHINE_ENTITY_TYPE ParentEntityGuid = {00000000-0000-0000-0000-000000000000} EntityType = LIBRARY_ENTITY_TYPE EntityFlags = 0000 Library = {BDD7F82F-865C-4897-93F2-6668162EA718}, "" PVLSVR: [03/23/23 20:03:28] [6020] PvlEntityDatabase::DeleteEntity() : SUCCESS! PVLSVR: [03/23/23 20:03:28] [6020] PvlEntityDatabase::DeleteEntity() : SUCC604Views0likes1CommentThe path appears to be an invalid path. Please ensure the server name and share name are correct.
I have downloaded a trial version of Backup Exec version 20.2 rev 1188, but I can't add my storage. The error I get is "The path appears to be an invalid path. Please ensure the server name and share name are correct." I've found this document: https://www.veritas.com/support/en_US/article.100028740, but it still doesn't work. The storage device is in DNS, and it's pingable from the BE server. The user also has full read/write to it. I'm trying to add it as disk storage. Also, I can map the drive through Windows, but I can't see it as a local disk from the drop down.Solved8.5KViews0likes6CommentsBackup error "remote agent not detected on another server"
Hello everyone, Currently I am getting the following error when backing up my data: I have 2 servers A and B, Server A backup data on itself to Tape 1. Server B backs up data on Server A to tape 2. Backup on server A is no problem, but backup on server B The problem is that the message after a successful backup is "remote agent not detected on server A", in addition, the Incremental backup also backs up all the data, not just backing up the file changes. Looking forward to your guidance and help to solve this problem, I sincerely thank you.949Views0likes3CommentsRestore backup from failed server to new server
I have a USB backup disk from an old 2008 server. Symantec BE 14 was running on the server which is now corrupt and unusable. I have setup a 2012 server with BE 2015 (only install disks I could get hold of). Is there a way to recover the backup to new server. I can see the bkf files on the USB HD and it appears to be intact. Thanks.Solved921Views0likes2CommentsKatalogisieren von LTO-Band in Endlosschleife
Hallo, überVeritas (Symantec) Backup Exec 20.6 R1.1.8.2 V-Ray-Edition versuchen wir alte LTO-Tapes zu katalogisieren. Dazu nutzen wir ein LTO4 Laufwerk mit einem 8-fach Wechsler. Wir haben im Wechsler zum Beispiel 8 aufeinanderfolgende Tapes mit Backups eingelegt und inventarisiert. Die Inventarisierung lief problemlos und alle Tapes wurden sauber erkannt. Jetzt wollen wir 1 Tape aus der Mitte katalogisieren. Er fängt an das 1. Tape z. Bsp. Nr. 4 zu katalogisieren. Dann nimmt er sich das nächste Nr. 5, dann Nr. 3 ... bis er alle hat und dann stoppt er und möchte das nächste haben, was jedoch nicht möglich ist. Wie können wir das unterbinden? Wir können den Prozess jetzt nur unterbrechen und den Wechsler neu bestücken, was dann auch sinnlos wäre, da wir von vorn beginnen müssten. Wir benötigen die Daten von nur einem Band. Hat jemand eine Idee oder einen Lösungsansatz? Danke Euch schon einmal!Solved709Views0likes1Comment