BE2014 - Loading Media for hours during any restore (deduplication)
Hi There, Whenever i try and do a restore from my deduplication device (locally attached) from a recent backup, it takes forever to restore. For example today, i tried to restore a 70MB file, and it took over 1.5 hours. Most of the time the job was just stuck on 'loading media'. I logged a ticket with support, and got nowhwere. I logged a couple of tickets with support for a similar issue with backups, and got nowhere with that either. (Was told that it was normal behaviour) Is there anyone here who has tried to restore from a dedupe store? If yes, are you getting these issues? The server i'm trying to restore from is also a CASO Thanks in advance for any comments
The queried backup sets contain two backup sets with the same ID
Hi, After some serious disaster on BE15(latest patch), I managed to get the server running again. However I am facing a different issue. When I select the deduplication storage and select Backup Sets tab, I see "Load Failed... The queried backup sets contain two backup sets with the same ID." . This happened after I removed this member server from CASO environment. I checked the catalog files and they are present. I also tried the "Catrebuildindex -r" method mentioned at the post "https://www-secure.symantec.com/connect/forums/duplicate-backup-sets-same-id". This had happened a couple of times when the server was a managed server in CASO environment but after a couple of F5, I was able to see the Backup Sets and even start restores. Any ideas?
Backup 2015 DLM not running
I have a CASO setup with one VM running the CASO role and three media servers on different locations. The media servers are physical with big D: and E: drives (only local disk, no removable disk or so), disk storage + dedupe storage. Catalogs are stored centrally and all servers run 2012 R2 OS and Backup Exec is fully patched with the latest patches as of today. Our normal backup procedure is to run the backup jobs to disk and then duplicate to dedupe storage, we also do some optimized duplication from one media server to another with duplication from dedupe to dedupe storage. We installed all servers early September and everything is running fine except that the disk storage backup sets will not be removed by DLM even if they are expired (or manually expired by right clicking and selecting "expire"). I installed another server to test earlier today and noticed that in the audit log (on the new test server) I could see that DLM log an event for every backup set it removes and it works just fine on that setup. This is a completely independent backup exec instance and only runs one backup job for test. In the audit log of our "real" backup server there is not a single entry logged by DLM from day one which is really strange. I logged a case yesterday with Veritas/Symantec support and the test we agreed on doing was to first run an inventory of the disk storage and when that didn't help we decided to do an inventory + catalog as well, since we have 39,5 TB of data to process it will take a while so I decided to try it on one of the other media servers instead (which is not fully used yet) and it didn't help so instead of just waiting until Monday I decided to write here to see if anyone else have experienced the same issue. I have tried with (and without) the "Allow Backup Exec to delete all expired backup sets" enabled with no change of the result. Anyone who has information that can help me, it would be very appreciated? Thanks!Deduplication & Optimized duplication - multiple jobs for one server?
Hi There, I have a number of servers that i want to back up with BE2014, using the deduplication add-on. I will also be adding a stage to duplicate certain backups to an offsite, shared dedupe store. I have a query about using multiple jobs for the same backup server. Say i create job A,(consisting of Full and Incrementals), and this job backs up one server to the primary dedupe store, and this will be duplicated to another dedupe store offsite Then, i go along and create job B, with different retention settings (also backing up the same server, to the same dedupe store), and this is also duplicated to an offsite dedupe store. Will job B go off and create a completely new batch of files (eg full backups) on the primary dedupe store, or will everything be completely deduped and no duplicate of files created (, because it can 'see' all of the full backups that were previously created via Job A? If new backups will be created, will the same thing happen in the offsite dedupe store, and the duplicate jobs will also create new backups in the offsite store? Basically, i will be creating one job for daily/weekly, and the weekly will be duplicated offsite. I will be creating a seperate montly job, with suitable retention, and this will have a duplicate to send it offsite. I will also be creating seperate quarterly and annual jobs with suitable retention for them also. Is this a good approach, and will this all work together and deduplicate well? Thanks in advance for your adviceBE2014 Optimized Duplication - 'Loading Media - Duplicate' for hours
Hi There, I have BE2014 on the latest version, and my architecture is as follows: -Production Environment, with CASO, Duplication Add-on, and a local dedupe store on this windows 2012 R2 server. (no extra devices connected) -DR environment, with a BE managed server out there, and Deduplication Add-on (no extra devices involved out there either). I have a dedupe store shared out on this managed server (shared with the CASO server in Production) -At present, there is a 1GB LAN connection between the two servers/sites. I have my backup jobs defined on the CASO server in production, and the data is being saved to the dedupe store in Production just fine. I have a stage added to duplicate the data over to the shared store over in DR, but the jobs are taking forever (too long for the backup window at present). Every time i check in on it, it's almost constantly stuck on 'Loading Media - Duplicate' Anyone got any ideas? Thanks in advance