B2D Jobs gone after migrating to new Server
Trying to upgrade to BE20 eventually. Upgraded W2008R2 server to W2012R2 and then had to uninstall original BE2014 (did not work after OS upgrade). Installed new copy of BE15 and did not touch the Ext HD BEData folder that was used for B2D. Was able to use a VM copy of the original W2008R2 w/ BE2014 (vm ran on different PC w/o the EXT HD)and upgraded to BE15 and then W2012R2, so physical server and VM servers are the same OS and BE15 versions. The upgrade to BE15 did not put a BEData folder on the C: system drive. Can't put the VM on the network to use migration assistant so followed article100020224 "How to migrate (move) Backup Exec from one system to another with the same version of BE, Windows and same or computer names". Followed instructions and copied the Catalogs\Data folders to the clean install of BE15. They mention "create a folder where the new Backup to Disk folders will reside and copy the saved off .bkf file(s)", but this doesn't make sense to me as the fresh install created that, but I want to use the existing one ont the EXT HD. In any case, BE15 runs, sees the EXT HD online and limited to "read-only" under storage tab, but when I click on it, it only shows Job History entries and not the Jobs or backup sets from before. In addition, if I try to do a test restore, the past backups dates are not there to choose from. Is there something else I can do to have theExt HD BEData folder fully recognized (Jobs, etc.)? Tnx..
Duplicate Jobs stuck in Active Queued
Veritas support has been worse than useless. We have a CAS MBS enviroment, duplicate jobs are scheduled to run every week from MBS to Deduplication storage on CAS but will get stuck in the active queued state for hours without any data transfer. No failure and no events in logs. Many weeks ago there was an Alert about Robotic Libraries but it has been cleared and not appeared since. Vertias support had me run an inventory on Dedupe storage, recreate storage, update all servers to 20.5, and generate several different logs. All to no avail. Any ideas are welcome.Request information full backup
Hello everybody! I need to know about jobs. I have a costumer wich use Backup Exec 2012 (v14 rev1794), and i have differents issues with the incremental job, like -528 file log missing, timestamp mismatch and so on. The full backup completes successfully. So, is necessary to keep trying to solve the incremental job? Thanks!