bpbakcup.exe Error Status 23
Hello, I'm trying to troubleshoot an issue I'm having with backups initiated with bpbackup.exe. We migrated the application and backup scripts from a Windows 2003 SP1 server to a new box with Windows 2003 SP2. The Netbackup version stayed the same 5.1MP3. The script initiates the user backup Whit bpbackup.exe then waits for the backup to complete. The command line includes the -w switch. On the previous box this ran fine, since we've migrated the bpbackup.exe process ends before the backup is complete which causes the script to fail. The script depends on bpbackup.exe to return once the backup is complete, so it can report success/failure. The error returned from bpbackup.exe is "EXIT STATUS 23: socket read failed" We get this error exactly two hours after the backup was initiated. Unfortunately, I don't have access to back end netbackup infrastructure only the client. The folks that support the back end can only tell me that the backups partially succeed, and no reason why I get the other error. Has anyone experienced similar behaviour, and resolved it?
Symantec or Doubletake Disaster Rocovery Solution
this is the setup I have a live SBS2003 server on site called server1 (Site A) 75 remote offices connect to this server for file an mail access should the server get stolen I need to replace it in as little time as possible and the clients should be non the wiser. when they log in I want to Mirror server1 with server2 at my office (Site B) and have it replicating in real time or on a schedule. after failover I need server2 to assume the role of server1 and become server1. I would then take the new server1 to Site A plug it into the network and log the clients in. I would then buy another server and call it server2, starting the replication/failover process again ready for another disaster. Doubletake have a package which can do this but i would prefer to use a known brand. is there a symantec package which can do this and where would i find someone who can explain the setup. All i get from symantec (if you are lucky enough to find tel Number) Is a load of propaganda advertising data sheets. and no presales tech assistance. I have 14 other clients ineterested in persuing this DR option if I cannot get a symantec product i will have to shell out a large sum to Doubletake for their package
6.2 Backup Reporter
Wow - this product seems overly complex in installation and the documentation for configuring the Symantec Security part is just lax. Am I the only person that finds this application cumbersome to install and configure; and/or has anyone successfully deployed version 6.2 Veritas NetBackup Reporter?
Help with designing backup scheme using BEWS & BESR
I've consolidated my questions here previously posted to another forum.. I'm looking for suggestions for setting up a disk-to-disk-to-tape backup scheme that utilizes either BEWS or BESR (or both). I have a NAS device and a single, non-autoloading tape drive with which I need to backup a file server, Exchange server, app server (SQL Server), and a few others. - The file server contains 400GB of files. - The NAS has 1TB available for disk-to-disk - A full backup currently fits on three 100GB tapes. - Differential backups currently fit on one 100GB tape. Requirements: 1. Ability to perform full system restores. I guess that means that at least BESR will be used for disaster recovery. 2. At least daily, weekly, monthly restore points. 3. Normal, file level restores from disk. 4. Tape for offsite backup not to exceed one day of lost data. In addition, it would be nice to allow users to perform restores of files from the file server. I don't believe CPS can target NAS devices, but I know BESR can. However, as far as I can tell, Retrieve comes with BEWS, not BESR. Since I need tape for offsite duplicates, and full restores for disaster recovery, I'm guessing both products are needed. I'm just not sure how to best integrate them. So far, I've come up with the following: - BEWS to backup the file server's attached disk enclosure to NAS. - BEWS to backup Exchange and SQL Server to NAS. - BEWS to backup DCs System State to NAS. - BESR to image servers (excluding file server's attached disk enclosure) to NAS. All of the above jobs would be run as full monthly and weekly, and incremental daily. The idea would be to use the NAS as a staging area for all of the various sources of data, then make full and incremental duplicates to tape. Can it be done? Does it make sense?
Backup Reporter
Backup Reporter sounds like a repackaged CommandCentral Service http://www.symantec.com/enterprise/products/overview.jsp?pcid=2244&pvid=73_1 Veritas Backup Reporter helps IT staff enhance the efficiencies of backup and recovery operations, verify backup service-level compliance, and bring costs associated with backup and recovery in line with the needs of the business. For heterogeneous environments, Backup Reporter provides a global, centralized reporting view of Veritas NetBackup, NetBackup PureDisk, and Backup Exec as well as other backup applications such as CommVault Galaxy, EMC NetWorker, and IBM Tivoli Storage Manager. Key Features Track backup job success against targets over time to ensure backups occur within SLA parameters. Aggregate historical data to identify growth trends and effectively plan backup resources. Monitor resource utilization and identify constraints associated with individual geographies or applications. Customize data views providing context to backup reports such as line of business, backup domain or application. Key Benefits Achieve backup service level compliance and align backup recovery operations with business goals. Lower CAPEX costs by accurately forecasting growth of backup and recovery infrastructure. Increase operational efficiency by proactively identifying risks and quantifying exposures before they impact critical backup operations. Keep customers happy by tailoring report content to the intended audience allowing them to see only what they want to see. Message Edited by Bob Stump on 07-24-200707:15 AM
Go Back corrupts Windows XP Pro - blue screen of death.
I had Go back 2007 installed in a Windows XP Pro system. It started to malfunction and technical support advised me to uninstall it using add/remove and Norton Clean UP tool. This resulted in a blue screen system crash that had corrupted Windows XP Pro. Symantec Technical Support said I had to contact Microsoft Technical Support - $80 up-front-fee if I had proceeded with them. The system would not boot from the XP disk. nor the Symantec Recovery disk. When reinstalling XP on Drive :C out of necessity, Windows corrupted the partitioning on a separate hard drive. I had to spend $500 to recover data from the second hard drive. The problem started by GO Back not working and corrupting files. Go back in 2007 bundle is a problem and there appears to be no satisfactory warning that it will corrupt Windows XP Pro when uninstalled. Hard to recommend Symantec products under these conditions. I was also very disappointed to find in SystemWorks 2007 that Ghost had been removed and a much inferiour Save and Restore Program included. Yes, bundles make it cheaper but I feel ripped off compared to SystemWorks 2006. Overall, SystemWorks 2007 slowed my system to unbeleievable levels and then ultimately led to a full system crash with corruption of XP, loss of partitioning and loss of data. Beware.DR backup media verification ...
Currently we are running our Disaster Recovery backups on Netbackup 6.0 MP4. We run vault twice a weekday and once every weekend day. I would like to track or verify that when operations runs vault, all the tapes that were written from the previous night were in fact ejected. I guess if they get list they can then verify with the physical media that were ejected. What command would I run to give me that information? What is the best way I can do this?
Need help selecting a DR Solution
We need help setting up a DR solution for our Symantec Antivirus Ver 10 server Our current setup is the Production Server is downloading updates from the Web and deploying them to clients in the normal manner Our plan for the DR site is to setup a secondary server , which will recieve its updates from Production and deploy them to all the clients in the DR site In the event of a DR we want the secondary server to assume the primary role During testing we discovered when the Primary server went offline, it took all of its client members with it. (could no longer see them under the primary servers list) Symantec’s solution says to promote the secondary (which we did), and to re-establish connectivity to the clients , copy a grc.dat to all the client members? We have a few thoudand clients so this is not the turn key solution we are looking for and are wondering if we are missing anything or perhaps there is a better approach to providing a DR solution. Any help appreicated Cheers