WSFC and Netbackup
I have some question and it complicated Current setup 1 primary server and 1 netbackup appliance We actually have 2 server for WSFC setup but some how it wasn't setup Now that I have been task to do so may I know what are my options? Redo win 2019 with WSFC and reinstall netbackup but how am I able to connect back the appliance media server to the WSFC netbackup.
Duplicate/copy backup images from tape to tape
Hi, I have gotten a request to duplicate/copy 2 tapes to new tapes. On each tape there's 1 backup set. The backup environment has 2 tape drives attached. I just need a 1-1 copy of tape in order to have an extra copy. If I right click the backup set I can choose "duplicate" and the process seems pretty straight forward. As destination I can see the library and also partitions and also the tape drives. If I pick the tape storage pool will the duplication job just take an available scratch tape if I pick the scratch media media set or? Any input would be much appreciated. Thanks.
Fehler beim Überprüfen der Identifikationsdaten MSSQL
Guten Tag, wir haben auf einem Server "Backup Exec 20.4" und auf einem weiterem Server den "Backup Exec Agent for Applications and Databases" Wenn ich nun in Backup Exec die Identifikationsdaten testen lasse, dann werden auf dem Server alle Laufwerke, Systemstatus und EFI-Systempartition als "Erfolgreich" getestet angezeigt. Nur der MSSQL-Server schließt mit einem Fehler ab. Auch bei einem Versuch bei einem Backup die Datenbanken aufzulisten, bekomme ich eine Fehlermeldung, dass das Login-Konto fehlerhaft ist. Ein Test des Loginkontos zeigt allerdings "Erfolgreich" an. Kann mir bitte jemand erklären, was da schief läuft. Hier die dazugehörigen Screenshots Danke.
Backup Exec 20, taking longer to backup randomly.
Backing up 1.5 TB of files to a tape drive. Backup takes 5 hours, including verification. It works just fine for days but on other days (random, not the same physical tapes or days of week) it times out after 10 hours. Changed thejob's maximum configured run time to 15 hours from 10 to remedy this. What could be causing this difference? Is it change or altered state of files being backed up? And if so, how do I fix this? I would appreciate all the help I can get on this.Autoloader 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
Newb's question first time restoring in Backup Exec 20.4
When I select the backup set that I want to restore and then hover my mouse over the 'Restore' function, it reads 'Browse the backup set and then restore the data.'. If I then click on 'Restore', is there a subsequent window where I get to select the specific folder(s) I want to restore or does it automatically restore the entire backup set? I'm hoping it's the former as I don't want to overwrite all my current data. Thanks.V-79-57344-65033 - Directory not found. Cannot backup directory
Backup Exec 20.4 running on the host and multiple VM servers all running Windows Server 2019. Some of the servers are running the agent and backing up separately, some are just backing up as VMs under the host therefore it is not possible to make specific file selections to add/skip. I am regularly gettingV-79-57344-65033 - Directory not found. Cannot backup directory for a list of directories. It seems to happen on one server a day, different servers each time, with no discernible pattern. I have tried removing a server from the backup, saving then re-adding and saving again which seems to stop it happening for a while on that specific server, but it pops up sooner or later. I cannot get a clean set of full backups for all the servers. We run multiple sites with multiple server setups using backup exec, every server will have files in the Windows directories being created and removed for updates/temporary files etc but this is the only site where this is a problem. Please can anyone advise on what I might be able to do to fix the issue?
