Articles on this Page
- 08/11/15--05:20: _Query regarding Ops...
- 08/11/15--05:27: _Backup Exec can't c...
- 08/11/15--05:38: _System Recovery
- 08/11/15--05:52: _DISASTER RECOVERY
- 08/11/15--06:09: _bpdbjobs -restart d...
- 08/11/15--06:36: _BE JOb stay queued
- 08/11/15--07:32: _After SDR success b...
- 08/11/15--08:11: _Creating a backup job
- 08/11/15--09:03: _Backup Exec 15 Slow...
- 08/12/15--02:01: _Problem on BE15 age...
- 08/12/15--02:17: _one duplication job...
- 08/12/15--02:21: _Error : 69: invalid...
- 08/12/15--03:17: _NBU App_cluster not...
- 08/12/15--03:43: _Backup Exec 2010 ca...
- 08/12/15--04:50: _disk not coming up
- 08/12/15--06:14: _Monitoring unfinish...
- 08/12/15--08:30: _events out of sequence
- 08/12/15--09:31: _Configured name of ...
- 08/12/15--09:34: _Client for Red Hat ...
- 08/13/15--04:10: _symantec Exce back...
- 08/11/15--05:20: Query regarding OpsCenter
- 08/11/15--05:27: Backup Exec can't connect to agent
- 08/11/15--05:38: System Recovery
- 08/11/15--05:52: DISASTER RECOVERY
- 08/11/15--06:09: bpdbjobs -restart doubt
- 08/11/15--06:36: BE JOb stay queued
- 08/11/15--08:11: Creating a backup job
- 08/11/15--09:03: Backup Exec 15 Slow Verify
- 08/12/15--02:01: Problem on BE15 agent update
- 08/12/15--02:17: one duplication job is running at one time
- 08/12/15--02:21: Error : 69: invalid filelist specification
- 08/12/15--03:17: NBU App_cluster not recognising new active node
- 08/12/15--03:43: Backup Exec 2010 cannot browse resources
- 08/12/15--04:50: disk not coming up
- 08/12/15--06:14: Monitoring unfinished replication progress
- 08/12/15--08:30: events out of sequence
- 08/12/15--09:34: Client for Red Hat - Backup Exec HELP
- 08/13/15--04:10: symantec Exce backup types
We had this step documented in one of our documents
Could anyone please let me know whether disabling the https protocol is the same as changing the default shutdown port?
Why is this disabling of https protocol being suggested? Is there any specific reason? What happens if we do not change the default shutdown port?
Disable use of https protocol with OpsCenter (use http only).
#/opt/SYMCOpsCenterGUI/bin/goodies/configurePorts.sh -shutdownPort 8181
I have been having issues with Backup Exec not being able to connect to a few target computers. I thought I had found a solution to this (restarting target machine, removing and establishing trust, etc) but that doesn't seem to be working anymore. I ran a full job on monday morning and the incrementa got stuck at discovering resources. I have put the job on hold and restarted the target machines but the server still can't connect. I open the job properties (where selections can be modified) and three of my 12 target machines can't connect.
i need to know what is diffrence between Backup Exec and System Recovery technically.
What i know is system recovery takes block levelbackup whereas Backup Exec filelevel backup.
Which one is more preferable ? And what is the diffrence?
Se eu NÃO marcar a opção de Disaster Recovery e perder meu servidor (único e local) eu consigo recuperar os dados (não o sistema operacional) apenas refazendo a instalação do Symantec Backup Exec?
OU é obrigatório eu marcar esta opção para que seja possível recuperar os dados?
Versão: Symantec Backup Eexec 2010 R3
Anytimes when I issue a
# bpdbjobs -restart 4334521
I get this message:
What's wrong in this command ?
I am runing BE15 FP1 on w2k8R2 platform.
I use it to backup VMs and everything is working fine excpet for one particular VM for which the job stay queued indefinitely.
This VM is quite big (1.4TB vmdk)
VM is runing W2K8R2SP1 on vSphere 5.5
DataStores are accessible thru iSCSI network
I really do not understand why ...
Any idea dear members ?
I've been encountering some odd behavior seemingly at random after some backups complete. The issue seems to occur primarily with GRT backups, however is not limited to GRT backups as I've seen the same behavior when non-GRT backups complete. I can only assume that the actual backup process completes successfully as the system generates an alert notification of ;SDR Success...' and I see the correct amount of data (xx GB) was backed up during a given job, however the actual backup job is reported as 'Failed' with an error code of E0000602 which is ...query for media sequence...unsuccessful... I can't be certian that the non-GRT backups are the same exact root cause, but they report the same error code even though I have an SDR Success alert corresponding to the backup that has reported as 'Failed'.
I have a feeling that the error code may be a bit of a red herring in this situation as well; after the backup completes, generates the 'SDR Success' message and begins to verify, the verification process can't find some of the backup sets created by the recently completed backup job. As such, the entire job fails. All jobs in question are B2D jobs, so I don't have any reason to suspect any configuration issues as we've had the same configuration and backup jobs running weekly for several years now and this behavior has only just begun to occur within the past few months.
What is leading me to believe that there is something else going on here is that consistantly, when this behavior occurs, I can look at the backup sets list in the B2D storage location that was used for the failed job and some of the backup sets that I expect to see are missing. This is reliabally the case when our Exchange backup reports failure after 'SDR Success...' alert is generated, I check the B2D storage location and I can see the 'system state' and individual Drive letters were backed up, however I don't see the mailbox or public folder databases backup sets. I'll then check the actual file system (Windows Explorer) and verify that there are indeed img###### folders which contain the mailbox and public folder databases - created at the date/time of the backup job that failed. If I then inventory/catalog the B2D location from within the storage view of the BE GUI, the missing backup sets appear. I can then manuallly re-run the failed catalog job (corresponding to the failed GRT backup job) and everything succeeds as if nothing was ever wrong.
So, as far as I can tell, the first behavioral problem contributing to this issue is that when the backup completes, the backup sets that were just created are not being listed in the backup sets list in storage - before the verification process for that particular backup job begins. As such, the verification process can't find one or more expected backup sets and fails the job with the E0000602 error code citing that it can't find the media. A manual inventory/catalog of the storage location finds the missing backup sets, lists them in the backup sets view in the GUI and then all is happy once again in backup land until the next failure occurs.
At one point I was under the impresssion that it had to do with the fact that some backup jobs run a little long sometimes and due to our short backup job expiration times the media was being deleted before the verification process could complete. (We B2D2T all the time, so having short expiration for the B2D portion keeps the B2D locations empty and available for subsequent backup jobs). This however is not the case since I'm beginning to see the same behavior occur more frequently when there is only one backup job running with no duplciate backup sets linked job and so the expiration should make no difference since BE won't delete the most recent available backup unless it has been duplicated by BE to other media.
So in short, the issue here seems to be that Backup Exec is not properly adding newly created backup sets to the storage inventory in all cases, seemingly at random. The bahavior does not occur only for one backup job and occurs for both GRT and non-GRT backup jobs. After a failure is reported, I can manually inventory/catalog the storage location containing the backup sets from the failed job which fills in the missing backup sets and allows a manual re-run of the catalog operation to succeed.
Any chance anyone has seen this before and/or is this possibly a known issue? If so, I could use a fix or a handy work-around so I don't have to continually baby-sit my backup jobs and re-inventory the B2D storage locations sevaral times a week.
Much appreciate any insight,
Hi again everyone,
I was having issues with my media server and i believe to have most of it fixed but i want to create a new selection list and a new backup job policy that runs automatically as it was doing before. I did not setup the previous server.
So far i have gone to File > New > Backup Selection List and selected everyhting i need backed up.
My question is.. now what.. ?? Do i create a new policy and associate the list with the policy or do i create a new backup job and associate the list with this new job?
thanks for the help as always!
Our Backup Exec is using an AWS VTL and can back our data up in a reasonable amount of time but the verifys are extremely slow. Right now we have a job that ran around 1700 MB/min and is verifying at 223 MB/min. We've setup antivirus exclusions and upgraded Backup Exec to feature pack 1. The Backup Exec server is a Windows 2012 R2 box. I'm not clear on what else we can do to speed this up so any assistance would be greatly appreciated, thank you.
Just updated BE server to BE15.
Then I copied agent folder from BE server to remote server for installation.
After installation, agent got error "cannot obtain settings for the agent for windows publishing from the registry".
Since in previous version update, all settings was kept.
We are facing backup issue due the duplication job.
in our environment we have set backup will first write on disk and then from disk to tape. And in SLP it has been configured that backup will be expire from disk once it will be duplicate on tape.
However currently I am facing issue, we have two tape drives in environment and at one time only one duplication job run at tape drive, which means maximum two duplicate jobs run at one time and other stay in queude. Which cause disk has been full and backup are failing with error 129, becuase until backup will not copy on tape it will not expired from disk.
Could you please suggest if we can run multiple duplication jobs at one time at one tape drive.
we seem to be getting this message suddenly on our backups .
ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1
Error : 69: invalid filelist specification
We have the policy set to backup all local drives and exclue Shadow Copy Components:\* and System State:\*
All the data disks backup succesfully ok
Any ideas how to get rid of the
Netbackup master is 7.5.04 and media servers are 7.1.02 All Solaris. We are getting error 13 when the node fails over, its taking the master up to 60 mins to recognise the new active node. So how do I lower the time for the update to occur or can I make netbackup discover each time rather than use cached setting? Help appreciated.
I'm using symantec backup exec 2010 on windows server, and suddenly i'm not able to browse the resource or edit my selection lists check the attached file
i cannot browse in order to add a new job
is that an update related problem ?
Thanks for your cooperation
IT Technical Support
I have one question? Please share the steps as what to do if disk is not coming online after vmoprcmd -up command.
Have somebody found a way to monitor the progress of unfinished replication ?
Know there is some reports in OpsCenter, but they all seem be on the complete images.
Where I am looking for: Kilobytes transferred, number of fragments transferred or simllar to tell me how far a long the image in progress is.
Have looked at nbstlutil/nbstl list options, the support site, connect and of course google search without luck.
We are having issues in duplicating some of the backup images:
Aug 12, 2015 2:14:07 AM - begin Duplicate
Aug 12, 2015 2:14:17 AM - Info Duplicate (pid=29268) Initiating optimized duplication from @aaaa8 to @aaaaD
Aug 12, 2015 2:14:13 AM - requesting resource randd01_lsu6_su
Aug 12, 2015 2:14:13 AM - reserving resource @aaaa8
Aug 12, 2015 2:14:15 AM - resource @aaaa8 reserved
Aug 12, 2015 2:14:15 AM - granted resource MediaID=@aaaaD;DiskVolume=arch_lsu_6;DiskPool=randd01_lsu6_dp;Path=arch_lsu_6;StorageServer=randd01;MediaServer=nwkbkup01
Aug 12, 2015 2:14:15 AM - granted resource randd01_lsu6_su
Aug 12, 2015 2:14:15 AM - requesting resource @aaaa8
Aug 12, 2015 2:14:16 AM - granted resource MediaID=@aaaa8;DiskVolume=arch_lsu_5;DiskPool=dd01_lsu1_dp;Path=arch_lsu_5;StorageServer=dd01;MediaServer=nwkbkup01
Aug 12, 2015 2:14:19 AM - started process bpdm (pid=29473)
Aug 12, 2015 2:14:37 AM - begin writing
Aug 12, 2015 2:18:19 AM - end writing; write time: 0:03:42
Aug 12, 2015 2:18:26 AM - begin writing
Aug 12, 2015 2:20:41 AM - end writing; write time: 0:02:15
Aug 12, 2015 2:21:07 AM - Error bpduplicate (pid=29268) Could not validate backupid: fs_1433721299, copy 2
Aug 12, 2015 2:21:07 AM - Error bpduplicate (pid=29268) Duplicate of backupid fs_1433721299 failed, events out of sequence - image inconsistency (229).
Aug 12, 2015 2:21:07 AM - Error bpduplicate (pid=29268) Status = no images were successfully processed.
Aug 12, 2015 2:21:07 AM - end Duplicate; elapsed time 0:07:00
no images were successfully processed (191)
Our Netbackup environment is running on version 6.5.6
I need some help to undertand maybe a very basic issue or doubt that I am having right now.
We have Netbackup 18.104.22.168 with Windows master and media servers.
Now I have to configure backups for Oracle RAC so I am in the process of NetBackup Client Installation on the Oracle nodes. We have 4 nodes for a load balanced cluster in our main site and four pasive nodes in our DR site.
During the installation one of the first prompt is "Would you like to use "name" as the configured name of the NetBackup client". I am unsure which client name should I use during the NetBackup for Oracle Client Installation in each node of the cluster. I know that in the policy configuration or RMAN scripts is recommended to use virtual name but confused if in this specific step of installation this should be the physical hostname of every single node.
Please your advice.
Hi! I'm Luke, i need help.
I have Symantec Backup Exec 10 in Microsoft Server, but i need one client for Linux Red Hat Enterprise Linux Server release 5.5.
Someone help me?
there is asymantec Exce backup types acoording to size by TB and according to number of servers that will backup from ?and what it is ?