Hola!
Nesecito el instalador de media para un server que tiene una plataforma PA-RISC 8900 con sistema operativo HP-UX B.11.31 U 9000/800.
Me dijeron que para esa plataforma nesecita una versio 6.5 porque la 7.5 no se puede instalar?
No estoy encontrando el intalador del media que nesecito 6.5.
Saludos.-
Scenario.
2 x backup Exec 2014 servers storing backup data locally to disk.
10TB of data backed up.
Aim.
To duplicate backup jobs to Amazon S3 for offsite storage. This would only be accessed in a disaster scenario.
Method.
I've been playing with Amazon's Gateway VTL device and their Gateway Cached Volume. (I believe Gateway Stored option not available for BE)
As such I have implemented both a VTL device and a cached volume device and made the storage available to backup exec via Iscsi initiator.
I have performed test backup jobs of both solutions and both appear to work fine.
Considerations.
The cost of runnning a an Amazon Storage Gateway (either VTL or cached) is roughly £80 per month. Obviously with actual storage and reads etc on top of this.
If I go down the VTL route I need to provision 2 gateways as the Iscsi initiator and the virtual tape library can only be connected to one physical BE server.
My preferred method, to avoid having to use 2 gateways, is 1 Gateway cached Storage device. Within Amazon AWS I can then create 2 volumes each with a unique ID and then each BE server has it's own Iscsi volume that it can use as disk based storage. I have tested this scenario with success.
Question.
How does Backup Exec manage the expiry of data sets that are stored on an Amazon S3 device?
What I need to avoid is costly reads of the whole amazon volume as this is where extra additional costs are going to be incurred.
Does anyone have any experience of this or have any tips to share?
Thanks
Hi
I plan on upgrading my DLO console to 7.6 shortly and was wondering if this would impact the clients in anyway?
Previously I upgraded clients to 7.5 along with the console, but Dedupe, even though it was disabled, was causing a high amount of IOps on our NetApp filer storage when the clients were on agent version 7.5. I had to downgrade all users to agent version 7.0 to resolve this issue.
Has there been any changes made in relation to the operation of Dedupe on version 7.6?
Thanks
Jimmy
Hello All,
I am trying to find a way to have high availability while doing backups and restores. If I have 2 media servers with msdp, I would like to do a backup to any of them and duplicate to the other. It could be done using a slp with storage units, but if I choose a storage unit group for backup, how can I choose the partner for the duplication?
Any ideas would be appreciated :-)
I have been having this random job failure. It started occurring as of BE 2012 and currently I have BE 2014 with service pack 2 installed. It only appear to occurred with our exchange backup job and to this particular mailbox. However, the strange thing about this is that the job going to Disk will always be successful, but when it duplicate to Tape it would sometime get the following error message.
Job ended: Thursday, January 29, 2015 at 5:31:59 AM
Completed status: Failed
Final error: 0xe00002f7 - Cannot extract mailbox messages from the Exchange backup. Review the job log for more information.
Final error category: Resource Errors
For additional information regarding this error refer to link V-79-57344-759
Click an error below to locate it in the job log
Duplicate- \\Galileo1\Microsoft Information Store\ExecutivesV-79-57344-759 - Unable to complete the operation. The following error was returned when accessing the Exchange Database file: '-1018 There is a checksum error on a database page. '
A mandate has been sent down to remove all "vernerable" JAVA content. The bundled java with our netbackup in /usr/openv/java/jre/bin.../java is 1.6.0.10. A swlist reveals we have the following installed.
SYMCnbjava 7.5.0.5 NetBackup Java Console
SYMCnbjre 7.5.0.0 NetBackup Java JRE
I've been told we do not use the java component. my question is can i just remove the directory or will that break something? is there a clean way to do this?
i appreciate the assistance.
Mark
we just moved to the 2014 version of backup exec from 2012, when pushing the updated agent out I had one failure on a windows 2003 server.
I tried doing a manual install instead of push, I get a message that version 13.05204 has been detected, and it will be upgraded, and when I continue from there the error I get is "the application has failed to start becuase BECRYPTO.DLL was not found, Re-installing the application may fix this problem."
I have uninstalled the remote agent, allowed ccleaner to clean the registry of all references to backup exec, then I run into the same exact error again.
suggestions?
Hello,
I have Backup Exec 2012 SP4 hotfix 217347, the backup sets on the dedup storage expired but did not remove.
I deleted manually the backup sets the dedup storage have 0 octet free.
Any ideas,thanks.
NetBackup Guru's
Got a general question about NetBackup Accelerator backups of Win 2k8(7.6.0.4) system state. My Windows 2k8 system state is ~15GB in size, it takes around 16 minutes to backup, with Accelerator features enabled, it always takes anywhere btw 15 to 20 Minutes. I know the system state backups is always full, however I am confused why it takes so long all the time.
Below is some of the job details, 0.0% optimization and 99.9% dedup. The first full backup of the system state with forced rescan took 16 minutes, subsequent incr or full takes the same amount of time.
01/29/2015 13:18:21 - Info bpbkar(pid=4016) accelerator sent 14495026176 bytes out of 14495026176 bytes to server optimization 0.0%
01/29/2015 13:18:23 - Info bptm(pid=20056) waited for full buffer 6736 times delayed 29059 times
01/29/2015 13:18:23 - Info bptm(pid=20056) EXITING with status 0 <----------
01/29/2015 13:18:23 - Info nbmstp01(pid=20056) StorageServer=PureDisk:storageServerName; Report=PDDO Stats for (storageServerName): scanned: 14157435 KB CR sent: 14190 KB CR sent over FC: 0 KB dedup: 99.9% cache disabled
Appreciate your help
Thanks
Ash
All,
When I try to install a new OpsCenter license I recieve the message "The specified license key already exists" from the OpsCenter web GUI. I know there are steps to remove the license file manually form the filesystem which will remove this roadblock, but I cant seem to dig up the file name and location that needs to be removed.
The way I remember it you shut down the OpsCenter services
Delete one or two files
Start the OpsCenter services again, but for the life of me I cannot remember what file/s one needed to remove. Anybody have a KB on this issue? or know what files the OpsCenter cashe it's license key to?
Thanks in advance
I have little different kind of situation compared to what was described here:
Symptoms:
Each night a warning has been generated that I have exceeded licenses, but I can not understand how and why.
Note! The page behind link provided by message above does not exist.
Installed software is BE2014 + SP1 + Hotfix 225092. Liveupdate does not offer any updates at this moment.
There are 2 vmware hosts. Each host has one 4-core processor installed (second socket exists but is empty) so I have purchaced 2 st. 6 core v-ray licenses. BE2014 v-ray is installed on one of virtual machines. I do not have any physical hosts to backup using BE2014. I have two network shares from nas devices which I do backup with BE2014.
Detected licenses are like below, it is strange that it reports 0 licenses used... why?
Screen of "Install licenses and option on this backup exec server..." looks like this:
Behind button "Show Removed Serial Numbers" I still can see old plain "BE2014" licenses, which I have "removed" from this server so I conclude they should not be in use anymore.
Are my backups / restore operations somehow compromised at this moment?
How can I fix this situation?
Which Network interface will the 5230 appliance attempt to use when performing the call-home function ?
For example, if I have a 5230 configured with IPMI port attached to my management network, 2 x 10GbE interfaces attached in a failover mode to my 'data' network - I am assuming the appliance will use the 'data' network (2 x 10GbE in this case) to contact Symantec for call-home.
I will NOT have eth0 (nor eth1/2/3) attached to any network following initial configuration.
Thanks,
AJ.
Hi,
I am having a Slorais 5.9 running on NB 6.5 . Need to configure the Catalog backups - DR file to be mailed . I have already put the required mail id's in the NetBackup 'Catalog Policy'
Created the mail_dr_info.sh touch file in /usr/openv/netbackup/bin .However not sure what exact lines\contents to be placed in it for it to work . Also do guide if any additional files\scripts to be placed as well
Kindly share your inputs
Hello All, I am new to Ops Center and I am trying to get a daily coverage report for all clients. What I am trying to get is a list of clients that did not have a successful backup (did not complete with status 0 or 1) in the last 24 hours. The canned "clients not backed" up report does not provide what I am looking for it is too detailed.
I am looking for 2 things in this report.
1. Call out any client that is in an active policy and did not run a scheduled job within the last 24 hours. Display Master Server Name, Policy Name, Schedule Name and Client Name.
2. Any job that ran within the last 24 hours that did not complete with either status 0 or 1. Display Master Server Name, Policy Name, Schedule Name and Client Name.
I should mention that I do have a license for analytics so if anyone has SQL for this it would be great.
Thanks
Kevin
Have five workstations running Windows 7 x64 Professional, Symantec System Recovery 2013 R2. One machine gets 99% through the backups and is giving EBAB03F1: Following Operating System error occurred while performing requested operation: 'OS error 2147754996.' Nothing is appearing in the Event Log except Error EC8F17B7: Cannot create recovery points for job: WS3. Error E0BB00B5: Snapshot error Error EBAB03F1: Following Operating System error occurred while performing requested operation: 'OS error 2147754996.' (UMI:V-291-3215-6071) It ends up deleting the .tmp files.
The "More Help on the Web" link just shows a problem with Ghost, with an old and new version intermingled. Other Google searches came up with problems on the VSS Provider, but the "vssadmin list providers" on a working system is exactly the same as the one that won't work.
Tried FixInstall.bat, no effect. Tried removing and reinstalling the client. No effect. Not sure what else to try. An identical system works, just this one fails.
Thanks in advance,
Terry
Hi !
We're running Backup Exec 2012SP4 for backing up a Exchange 2007 CCR cluster running on Windows x64. This has given us few problems, but during a restore request I got the other day I ran into a strange problem:
The mailbox I need to restore resides in a storagroup called SG00 (we have SG00-SG37). Allthough backup (boht full and incrementell) have run fine I'm only able to browse some of the backups. The backups that I'm able to browse also restores successfully, but there is a period of about 4 days that I can't restore and this is quite a problem for the user.
When I'm trying to view the content of the media I get the "Query Failed" error.
I'm really baffled by this and the user really need the data for the last 4 days.
I've tried to repair the database (including rebuilds etc) and restarting the server, but to no use.
I've enclosed a Word file with 2 printscreens. One pictures show inability to browse and the other shows succesfull backup.
Any ideas what might cause this?
Best regards
Petter Fossum
Hi,
I have server 2012 R2 With backup Exec 2014 SP2 .A job failed had this error:
Final error: 0xe0009582-Cannot get the disk changed information
Final error category Ressource Errors
For additional information regarding this error refer to link V-79-57344-38274
Any ideas?
I've done a lot of searching in the commands documentation, and on-line, so I assume I need an "undocumented" command or command line option to solve my problem.
I've creating records of tapes (using vmadd) into a new master server so that we don't loose track of some tapes that we'll likely never use again, but for legal reasons have to keep around. I'd like to update the "last update" feild in the EMM so that it shows up with a more realistic date when using bpmedialist against these particular tapes.
I don't need these tapes imported or anything like that, just want to be able to keep track of them, and when they were last updated.
Thanks in advance.
Hi:
I recently inherited a Backup Exec 2010 R3 environment. While I am moderately proficient with NBU I had never worked with or saw BE. The intention is to abandon the environment and migrate to NBU or some other protection solution. There are over 30 TB of storage being used for disk backup jobs. Many of these jobs had not been run for some time as tapes needed to be rotated out of their libraries. Currently nearly all the tapes in the libraries have been replaced by Scratch and I have initialized them for use. I have run every duplication backup to tape job configured and around 90% of them fail. The failure codes are generally: "e0009444 - The requested source duplicate backup sets catalog record could not be found. Perhaps the media containing the source backup sets was previously deleted. For additional information regarding this error refer to link V-79-57344-37956"
I have inventoried all 7 of the disk backup devices, why they are carved into 4 GB chunks for Terabytes worth of storage is beyond my comprehension but ... I am also in the process of cataloging all the disk storage. Many are failing with "Catalog 01521 -- The job failed with the following error: The requested media is not listed in the media index and could not be mounted. To add the media's catalog information to the disk-based catalogs, run an inventory operation on the media and resubmit the Catalog operation." Sounds like I am going in circles. Should I have catalog-ed before the Inventory? Seems strange from a NBU perspective. The intent is to get disk storage to tape should a restore be required and decommision the environment. There are other errors associated with the catalogue process indicating that it wants physical media like tapes. "Catalog 00799 -- The job failed with the following error: Physical Volume Library Media not found." I did notice that when I go under Devices and select one of the disk storage "groups" in the right panel where the 4 GB chunks of disk media "live" I can select groups and vault. From the help menu this does not sound like NBU vaulting where I can duplicate the disk unit contents to tape or any other media. Kindly advise on what is the best way to get the disk storage to tape if I am fumbling. I am aware of the process detailed in a Symantec TN about migrating BE tapes into a NBU environment should this be desired. Thanks for any and all assistance.
Hallo, ich habe ein HP Bandlaufwerk bisher in einem HP Proliant DL 350 G5 mit WIN 2003 und Backup Exec 12 sehr lange fehlerfrei betrieben.
SAS Controller ist ein HP HP SC44Ge 416096-B21 (LSI) .
Bandlaufwerk ist ein “HP StorageWorks Ultrium 4 Tape Drives 1760 SAS LTO“
Nun wurde das Bandlaufwerk inkl. SAS Karte an einen HP Proliant DL 380 G5 angeschlossen und mit Windows Server 2008 R2 und Backup Exec 2014 SP2 (14.1 Rev. 1786) installiert. Seitdem erhalte ich diese Fehlermeldung im WIN Systemprotokoll und auch in Backup Exec:
„Der Treiber hat einen Controllerfehler auf \Device\RaidPort0 gefunden.“
Ich habe die hier im Forum anderen Artikel zu diesem Fehler gelesen – hilft aber alles bisher nicht.
Ich habe die Firmware des Bandlaufwerks aktualisiert
Ich habe den Bandlaufwerkstreiber aus der WIN Gerätesteuerung mittels Suche nach neuem Treiber im Internet aktualisiert
Ich habe den zuletzt gültigen Treiber für den SAS Controller bei HP heruntergeladen und installiert
Ich habe mit „HP Library and tape tools“ die Funktionsweise des Bandlaufwerks geprüft. Das Bandlaufwerk meldet hier keine Fehler.
Trotzdem bekomme ich innerhalb Backup Exec diese Fehlermeldung sobald ich das Bandlaufwerk benutzen möchte. Es blink danach und lässt sich bis zu einem kompletten Servershutdown und Reboot nicht mehr ansprechen.
