Media host override for SAP restores on Data Domain storage server
Hi, We are required to run a very large restore (~12TB) of a SAP database. The backup image is stored on a Data Doamin storage server. We would like to force the restore to use a specific media server that is not the server used for the oirignal backup. The storage server has 6 DD Boost enabled media servers accessing it for both backups and duplications between data centers. Each time we initiate the restore a different media server is used. We have used the "media host override" settings but these do not seem to be honored for OST storgae servers according to this artilce - http://www.symantec.com/connect/forums/how-use-media-host-override Has anyone else experinced this problem?Backup Exec 2012 Has Issues
To help someone who may be thinking about upgrading to Backup Exec 2012, be careful. Backup Exec 2012, while it does have a very nice user interface and much better view of the backup jobs, it has some major issues that are not yet resolved. We did an upgrade over a week ago and we still can not compete our backups. The issues today are: -- The upgrade got us into a look over the "deduplication" feature and needed to call support for a answer (we have placed the solution on the forum) -- The reports are not working at all. It appears it is using the old reports or is just broken. So no reports on media, or jobs, etc. -- We have run out of backup space and there is NO way to manage the "media". You can see media sets but you are unable to sort or figure out which ones you can delete. (other than just reading though the unordered list) NOTE: We can not run a report to view the media which was suggested as a work around. -- There is no way to change the "retention" date of a "media set". So we wanted to reduce the retention period for existing backups so the space on the backup to disk folder will be reclaimed. Well since there is no concept of a "media set" in this version, you can only change the date for future backups. -- It keeps doing "discovery" on computers we have already noted as not needed to be backed up. Discovery runs on its own and adds machines that it finds. Even if we delete the machine, the next time discovery runs we are deleting it again from the list. We need to run discovery but once we make a decision on the machine, it should stop showing up. We are committed to Backup Exec 2012 but are really in a bad way with the product right now. So if you thinking of an upgrade, it might be better to delete you old version and start from scratch. Or wait. Hopefully this will prevent another user from going through this nighmare.
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
Monitor Appliance Health & Performance 24x7
Today’s businesses require access to their information on a 24x7 basis, not to mention the ability to protect that data in the event of unplanned interruptions which leads to complexities in their IT infrastructure. For many IT leaders, moving to Symantec appliances for their backup issues to protect data means reducing cost, complexity and operational risks in their IT environment. Symantec understands that a properly planned out data protection strategy enables customers continuous access to their information. To that end, Symantec has gone a step further to simplify, automate and enhance the support experiences for its appliance customers with its latest functionality in appliances, Symantec AutoSupport. Symantec AutoSupport proactively identifies issues, automates support, and enables faster resolution with the aim of lowering customer’s total cost of ownership of their appliance environment. As a result, appliance downtime is minimized, product reliability and serviceability is enhanced, storage capacity planning and management is simplified, and who doesn’t want their issues resolved before the customer is aware of any problems. To find out how Symantec AutoSupport can help, check out this video http://bit.ly/EnableAutoSupportBE 2012 Beim Verarbeiten eines Backup-to-Disk-Befehls trat ein Fehler auf
Hallo zusammen, ich bekomme folgende Fehlermeldung im Eventlog eines W2k8 R2 mit BE 2012 SP1. Das Volume mit dem BtD Ordner ist 16TB grioß und hat noch über 1 TB freien Platz. Die Meldung erscheint im Sekundentakt bis zu 50 mal beim Sicherungsauftrag. BackupExec Job Engine schmiert dann ab und muss neu gestartet werden. Jemand eine Idee? Alle Artikel die ich gefunden habe beschreiben einen andren Fehlercode. Error=0 hört sich nach "könnte alles sein" an. Protokollname: Application Quelle: Backup Exec Datum: 06.09.2012 00:46:25 Ereignis-ID: 33808 Aufgabenkategorie:Keine Ebene: Fehler Schlüsselwörter:Klassisch Benutzer: Nicht zutreffend Beschreibung: Beim Verarbeiten eines Backup-to-Disk-Befehls trat ein Fehler auf. Changer: MoveMedium() Improper InitCode Found (B2DDrv1.4). Error=0 THX tcpip