Backupexec USB Tape drives and Compression
We typically install HP Tape Drives & Symantec Backupexec. In 2010 we installed a HP USB DAT 160 with Symantec Backupexec 12.5. The backup would not compress. Symantec told us that Backupexec is capable of compression & HP told us that the tape drive is capable of compression. But we could not get any compression when used together. An engineer in our firm did some digging around & came back saying that Symantec Backupexec will not support compression on USB Tape devices. We finally gave up & purchased a HP SAS DAT 160 & compression worked. I am not looking for do this do that suggestions, trust me we have done it all. I am not concerned about how much compression & the factors that affect compression. As far as I am concerned 1MB over native capacity is compression My question is does anybody (would love to hear from Symantec) know for a fact if it is still true for the latest version of Symantec Backupexec i.e. It will not support compression on USB Tape devices?
How-To: Downgrade Backup Exec 2012 to 2010 R3
Two months ago I decided to upgrade our backup environment to Backup Exec 2012. I have upgraded Backup Exec in the past and always had relatively few issues during the upgrade process. I had tried to find some detailed information about Backup Exec 2012 but all I could find was some vague descriptions of what was new. I figured I would give it a shot(totally going against my own if it aint broke don't fix it policy). After the relatively smooth upgrade process my jaw dropped at the interface. I thought it was terrible. But I thought I would give it a chance. I eventually got used to the interface although after two months I still preferred the old interface. My problem was the bugs. Maybe it was because I upgraded rather than installed fresh. But over the course of two months I ran into numerous bugs. The application would randomly quit with exception errors. Sometimes during the middle of my jobs it would just stop backing up and I could not perform any jobs (inventory, erase, etc) without restarting the services. It was terrible. I was having to babysit the thing constantly and still not having reliable backups. After working with Support and them telling my to just "repair" the installation and having the same problems, I decided to take matters into my own hands and downgrade. Luckily before I upgraded I made a copy of my Catalog and Data folders that are located in the Backup Exec program files folder. I would like to preface by saying the intro to this article is not meant to start a discussion about the fallacies of BE 2012 - there are plenty of forums for that - just giving a little background on why I chose to downgrade. The following are the steps I used to downgrade my installation. 1. Locate your backed up Data and Catalogs folders.Hopefully, you backed up your Data and Catalogs folder before you upgraded. If you didn't then this article doesn't apply to you. 2. Uninstall BE 2012 choosing to remove everything when asked. 3. After uninstall is complete reboot the server. 4. Install BE 2010 and select the options you need during the wizard, choose to use a new SQL Express instance. 5. After installation run Live Update and update to R3. 6. Reboot the server. It doesn't prompt you to reboot but if you try opening the application it tells you that you need to so go ahead. 7. Stop all the BE services. 8. Navigate to C:\Program Files\Symantec\BackupExec\ and rename the Data folder to Data.new and the Catalogs folder to Catalogs.new 9. Copy your backed up Data and Catalogs folder to the directory in Step 8. VERY IMPORTANT STEP - WILL NOT WORK IF NOT PERFORMED 10. Run thebeutility.exefound in the location from Step 8. Ignore the warning message that pops up when you open it. 11. Select All Media Servers in the left pane. 12. Select your media server in the right-pane and right-click. 13. Select Copy Database. 14. Navigate to the .mdf database file that is located in your Data folder that you copied over in Step 9. 15. Do the same thing for the .ldf log file located in the same location. 16. Press OK. It will run through stopping services re-attaching the database and starting the services again/ NOTE: The first time I did this I didnt do steps 10-16 and the BE services would not start correctly. Thanks to owner ofthis blogI was able to follow their steps and get it going. Big shoutout. 17. You now have an almost fully-restored BE 2010 installation again. It will be running in trial mode. You will still need to contact Symantec Licensing (1-800-721-3934) to get your license keys donwgraded to BE 2010. But at least you can run backups now for 60-days. Now the time-consuming part...This will vary depending on how many servers you are backing up. After I restored my BE 2010 installation I edited my policies and checked my selection list. The first thing I noticed was I was not able to select anything other than user shares on each server. I then proceeded to check my resource credentials. They all failed stating the agent was not installed or the credentials were invalid. I was sure the service account I was using was valid but just to make sure I went ahead and logged into another machine succesfully using it. After I confirmed it wasnt the service account, I knew it was most likely the newer agents I had installed for using BE 2012. I tried to install the BE 2010 agents through the BE 2010 interface. It said they installed correctly but I was still getting the same error. Here is what I did to get the agents going again. 1. Log into each server you are backing up. (I used RDP, but console would work also) 2. Navigate to the backup exec program files unc path located on your media server. ex: \\servername\c$\program files\symantec\backupexec\agents 3. You will see RAW32 and RAW64. These obviously are the Windows installation agents for 32-bit version and 64-bit. 4. Select the appropiate folder for your server architecture and run setup.exe 5. Select the Uninstall option (repair doesnt work - I tried). 6. After the uninstall is complete, run setup.exe and this time install. NOTE: You could also just run the uninstall on all your servers and then re-install the agents using the BE 2010 interface. Actually this would have been my preferred method but I didn't think about it until after I installed all the agents. 7. Most of my servers did not require a reboot but if you get an error about a missing file after the install - uninstall again, but this time reboot after the uninstall and re-install after the server reboots. 8. Go back to your media server and test your resource credentials and selection lists. They should all pass and you should be able to see and select all the drives, SQL database, and Exchange IS'. You are done! I would say for a ~20 server environment this process might take around two hours to complete. It took me much, much longer but I was figuring things out as I went. Like I said the most time consuming part was the agent installs and this will greatly affect how long it takes in your environment. I hope this helps someone out. Again, I'm sure BE2012 is right for someone but for us, we'll stick with 2010 as long as we can. We already bought Avamar and will be moving to that in the next 30 days but we still have to keep BE for at least 7 yearsHow to use external hard-disks and rotate them
Are you thinking of using external USB or eSata hard-disks for your backups and you also want to rotate them? If you do not know how, read my articles For BE 2012 - https://www-secure.symantec.com/connect/articles/how-rotate-external-harddisks-be-2012 For BE 2010 and earlier versions of BE - https://www-secure.symantec.com/connect/articles/how-rotate-external-harddisks
BackupExec 2010 R3, Pauses inside job between resources
After migrating to new Server with Windows Server 2008 backup jobs became more quickly but only for one time. after investigation, I found that during job between resources such as disk "C" "D" "System state" "Shadow Copy Components" from same server, it make PAUSES... not a pause between jobs or etc.. pauses inside job. Do some one know where the problem is? Previous weekends were not such delay inside job. Also no errors or any information regarding backup in System Event log Look for delay between backup completes and starts for Disk "D" Backup started on 12/7/2012 at 10:15:33 PM. Backup completed on 12/8/2012 at 5:01:47 AM. for Disk "C" Delay from 5.01.47 AM till 8.12.55 AM Backup started on 12/8/2012 at 8:12:55 AM. Backup completed on 12/8/2012 at 8:32:12 AM. Shadow Copy Components Delay from 8.32.12 AM till 11.35.53 AM Backup started on 12/8/2012 at 11:35:53 AM. Backup completed on 12/8/2012 at 11:47:20 AM. System State Delay from 11.47.20 Am till 12.56.29 PM Backup started on 12/8/2012 at 12:56:29 PM. Backup completed on 12/8/2012 at 2:27:04 PM. LOG Job Operation - Backup Backup Options Media operation - Overwrite media. Compression Type: Hardware [if available, otherwise none] Encryption Type: None WARNING: The option 'Verify after backup completes' was not selected. Performing a verify operation to make sure that media can be read after the backup has completed is recommended. Server - ******* AOFO: Started for resource: "D:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The snapshot provider used by VSS for volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Set Information - D: Backup Set Information Family Name: "Media created 12/7/2012 10:01:01 PM" Backup of "D:" Backup set #1 on storage media #1 Backup set description: "" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 12/7/2012 at 10:15:33 PM. Backup Set Detail Information The .DR file that is required for Intelligent Disaster Recovery is created/updated. Backup completed on 12/8/2012 at 5:01:47 AM. Backup Set Summary Backed up 2198520 files in 310164 directories. Processed 2,330,573,766,756 bytes in 6 hours, 46 minutes, and 14 seconds. Throughput rate: 5471 MB/min Compression Type: Hardware AOFO: Started for resource: "C:". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Set Information - C: Backup Set Information Family Name: "Media created 12/7/2012 10:01:01 PM" Backup of "C:" Backup set #2 on storage media #1 Backup set description: "" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 12/8/2012 at 8:12:55 AM. Backup Set Detail Information The .DR file that is required for Intelligent Disaster Recovery is created/updated. Backup completed on 12/8/2012 at 8:32:12 AM. Backup Set Summary Backed up 23375 files in 5522 directories. Processed 20,954,762,527 bytes in 19 minutes and 17 seconds. Throughput rate: 1036 MB/min Compression Type: Hardware AOFO: Started for resource: "Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" "D:" . The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). The snapshot provider used by VSS for volume D: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Set Information - Shadow?Copy?Components Backup Set Information Family Name: "Media created 12/7/2012 10:01:01 PM" Backup of "Shadow?Copy?Components" Backup set #3 on storage media #1 Backup set description: "" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 12/8/2012 at 11:35:53 AM. Backup Set Detail Information The .DR file that is required for Intelligent Disaster Recovery is created/updated. Backup completed on 12/8/2012 at 11:47:20 AM. Backup Set Summary Backed up 2 Shadow Copy Writers Backed up 5 Shadow Copy Components Processed 35,035,300 bytes in 11 minutes and 27 seconds. Throughput rate: 2.92 MB/min Compression Type: Hardware AOFO: Started for resource: "System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). The following volumes are dependent on resource: "C:" . The snapshot provider used by VSS for volume C: - Microsoft Software Shadow Copy provider 1.0 (Version 1.0.0.7). Set Information - System?State Backup Set Information Family Name: "Media created 12/7/2012 10:01:01 PM" Backup of "System?State" Backup set #4 on storage media #1 Backup set description: "" Backup Method: Full - Back Up Files - Reset Archive Bit Backup started on 12/8/2012 at 12:56:29 PM. Backup Set Detail Information The .DR file that is required for Intelligent Disaster Recovery is created/updated. Backup completed on 12/8/2012 at 2:27:04 PM. Backup Set Summary Backed up 17 System State components Processed 10,595,184,195 bytes in 1 hour, 30 minutes, and 35 seconds. Throughput rate: 112 MB/min Compression Type: Hardware
Tape set confusion ...
Good morning, I've some logical problem with BE 2010 R3: We use a Quantum i40 tape library with two magazines to backup our SAN. To organize the tapes we use the left magazine for the daily tape set (allways in the library) and the right one for the weekly tape set (changed every monday). So I've configured two jobs and two Tape sets in BE 2010 R3, one for the left with 5-day overwrite protection, one for the right with always overwrite. Everything is full functional, but sometimes BE seems to be "intelligent" and uses some tapes from the wrong tape set, one example from this weekend: The weekend job is configured to use the "right" weekly tape set / magazine. There are a few temporaly tapes and enough over writeable in the right magazine available - but it use one over writeable tape from the "left" daily magazine. Why? Every Job is configured to use one static magazine / tape set, why is BE changing this and re-join the tapes to different sets? Many thanks. Erik
