top of page

Latest

Public·2 members

Symantec Backup Exec 12.5 For Windows Servers 11


I am still getting exceptions logged for the system state backup after doing this. The tech advised me that the 2 files being skipped in system state are not required and to open another case w/the Backup exec support team (love how Symantec will shuffle you around) to fix the exceptions generated.




symantec backup exec 12.5 for windows servers 11



I recently upgraded from Backup Exec 11d to 12. This upgrade was necessary because we also just upgraded from Exchange 2003 to Exchange 2007. After the upgrade I had to push-install the new version 12 Backup Exec Remote Agents to each of the servers I am backing up (about 6 total). 5 of my servers are doing just fine, faithfully completing backups every night. My file server routinely crashes.


This may be an open file issue, and the open file may be getting corrupted. Try backing everything up EXCEPT the windows (and below) directories. See if backing up just data freezes the sucker. Also, if you have the disk space do a disk to disk backup with NT backup, then backup that file to tape. Make a current rescue disk. Also manually backup the AD files.


Actually Server A is a deduped File Server. Since BE 12.5 Rev 2213 version doesnt support that so I'm doing it this way. The same is being done for SQL 2008 R2 as well and that works perfectly fine, had done couple of restores earlier. With this logic I'm just collecting files from symantec


Back to your query; I'm happy to see you are interested to know how this workaround is working. As mentioned above server A & B are both 2012. Windows server 2012 gives me an option to have LUNs bigger than 2TB. This way I've assigned reasonably good storage for file share and disk backup. This disk backup is being done by Windows built-in back-up utility. Once my first level of backup (windows Image Backup) is done, the files are then simply backed-up as flat files from disk to tape. As mentioned earlier logically it should work as for Symantec be it any extension (doc, xml, csv, vhd or VHDX for that matter) should NOT be an issue while backing up, here I'm not refereeing to SQL or SharePoint file type. However, I'm stuck with restoring large file sizes; anything that goes in loads of GBs or TBs.


I'm running Backup Exec 12.5 on Windows Server 2008 Standard x64. The Server is connected to a Dell Powervault 124T with a SCSI interface and i run backups for the server itself and other jobs that backup other servers across the LAN.


You don't necessarily have to backup the catalogs to tape, but they're handy to have in a disaster scenario. I copy them to other servers in some Customer sites. In others, I just cover them with the regular tape backup. It depends how big they are and what your tape free space / backup window time is like.


Veritas Backup Exec is a data protection software product designed for customers with mixed physical and virtual environments, and who are moving to public cloud services. Supported platforms include VMware and Hyper-V virtualization, Windows and Linux operating systems, Amazon S3, Microsoft Azure and Google Cloud Storage, among others. All management and configuration operations are performed with a single user interface. Backup Exec also provides integrated deduplication, replication, and disaster recovery[1] capabilities and helps to manage multiple backup servers or multi-drive tape loaders.


With its client/server design, Backup Exec provides backup and restore capabilities for servers, applications and workstations across the network. Backup Exec recovers data, applications, databases, or systems from an individual file, mailbox item, table object, or entire server. Current versions of the software support Microsoft, VMware, and Linux, among others.[4]


When only a single job is running, and the source server is constantly seeking at a high rate, the tape drive slows down or may stop, waiting for its write cache to be filled. These delays accessing data can cause the backup availability window to be exceeded, when multiple servers with slow transfer rates are being backed up one after the other to the tape device.


This week our backup server had to be replaced. So we installed the new server. Installed Backup EXEC 12.5 on the new server. But I want on the new server al my jobs, policies, selection lists and catalogs. After some google search I had found all the info I need to do this.


3. On SERVER01 stop all backup exec services and stop the backup exec database. Use the Backup Exec Service Manager(C:\Program Files\Symantec\Backup Exec\BEUtility.exe) to Stop All services. To stop the backup exec database run the following command from the command prompt net stop MSSQL$BKUPEXEC.


Backup Exec 2012 is one integrated product that protects virtual and physical environments, simplifies both backup and disaster recovery, and offers unmatched recovery capabilities. Powered by Symantec V-Ray technology, Backup Exec 2012 restores entire servers, critical Microsoft applications, and VMware or Microsoft Hyper-V virtual environments to dramatically minimize business downtime.


The agent expands network-wide data protection and optimizes data transfers for 32-bit and 64-bit remote Windows servers running Microsoft applications (Exchange, SQL, Active Directory, SharePoint). Exclusive Agent Accelerator technology helps optimize backup and recovery performance by providing source-level compression and distributed processing at the client.


Log Name: ApplicationSource: MsiInstallerDate: 9/7/2009 1:05:06 PMEvent ID: 11719Task Category: NoneLevel: ErrorKeywords: ClassicUser: MERCURIO2\AdministratorComputer: Mercurio2Description:Product: MSXML 6.0 Parser -- Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance.Event Xml: 11719 2 0 0x80000000000000 9512 Application Mercurio2 Product: MSXML 6.0 Parser -- Error 1719. The Windows Installer Service could not be accessed. This can occur if you are running Windows in safe mode, or if the Windows Installer is not correctly installed. Contact your support personnel for assistance. (NULL) (NULL) (NULL) (NULL) 7B46463539434232332D313830302D343034372D423430432D4532304145373035313439317D I have tried: -us -us -us -US/winserverManagement/thread/e22564e1-d08f-4291-9f74-02cb069ae226The version MSI is 4.5 and Ii can not reinstall.I have verified that I can start the Windows Installer service without errors.I have searched all the usual places and found plenty of advice for Windows Installer problems in XP / 2003 / Vista but nothing for 2008.This server is a backup server (Veritas Backup Exec 12.5 and Vsphere Virtual Center). The servier is inside domain.can somebody help me?Thank you 350c69d7ab