All backup are scheduled and work without problem.
I already try to restart omnitrig but the issue is still present.
Thank you for your help :)
↧
Re: Dataprotector - scheduled copies don't start
↧
Options for new Cell Manager
Hi,
I'm putting together a design for a new Data Protector 9.03 Cell Manager on Windows 2012 R2 running on a VMware virtual machine. The spec is 32GB RAM, 8 Xeon CPU, 1TB disk (for IDB). The machine will only be a Cell manager and NOT a Media Server.
I'm also suggesting these inclusions in the global file:
MaxBSessions=100
SmWaitForDevice=3600
SessionStatusWhenNoObjectToCopy=1
SessionStatusWhenNoObjectToConsolidate=1
SessionStatusWhenNoObjectToVerify=1
And these suggestions in the omnirc:
OB2IPCNOSENDRECVLOOP=1
OB2SHMIPC=0
OB2IPCKEEPALIVE=1
OB2IPCKEEPALIVETIME=900
OB2IPCKEEPALIVEINTERVAL=60
Are there any additional (or amended) entries that are recommended?
Any help would be gratefully received.
John
↧
↧
Data Protector Express and Quantum Dat 160
Hi,
we are running Data Protector Express Single Server Edition 4.00 sp1 (Build 43064) with a HP Dat160 Tape Streamer. Due to a malfunction I borrowed a Quantum Dat160 Tape streamer. When I attach it it says "Fehlerstatus 1406 nicht unterstütztes Gerät" which in English should be something like "Errror 1406 Device not supported." In the Windows Server 2008 R2 Device Manager the drive shows up with no errors. It also says something like "License state: not licensed"
According to the Compatibilty Matrix this combination should work.
May be someone has a hint to solve this issue?
Thanks in advance
--
Sorry, English is not my native language
↧
Re: Dataprotector - scheduled copies don't start
Try starting omnitrig with -log Option, maybe it writes out the reason for not starting the Job.
Possibly the Permissions on the schedule-File are wrong or the format was altered inproperly.
Removing the Files and creating them from scratch may do the trick as well.
↧
Re: Data Protector 9.0 and StoreOnce
Let me add some clarity here. StoreOnce integration with Data Protector is an API level integration that allows you to deduplicate your backup data at the source (with Data Protector). You still would need a target StoreOnce appliance (or VSA) to write your backup to. This blog post is from about a year ago but does a good job describing StoreOnce Catalyst(the name we've given to the APIs that integrate with Data Protector and else where in your backup environment). Happy to answer questions you may have.
↧
↧
Re: Data Protector Express and Quantum DAT 160
↧
Cannot include more than one VMware VM in a backup job
Trying DP 9 installed on CentOD 6.6 with Virtual Environment Integration. A backup of a single VM in a job succeeds, but when there is more than one VM selected in the job, the failure is:
Cannot start program '/opt/omni/lbin/vepa_bar.exe'
[70:15] Cannot start program '/opt/omni/lbin/vepa_bar.exe' ([4] Interrupted system call) => abortingGot unexpected close from OB2BAR Backup DA
Appreciate any assistance.
↧
DataProtector 9 Storeonce Network Sensitivity
Hi,
We are running DP 9.03 on our Windows Server 2012 R2 Cell Manager. All Media Agents are also upgraded to 9.03 and also Windows Server 2012 R2.
Recently we have had some very brief network outages between our main datacentres, the outages last about 1 - 2 seconds. During these any Data Protector jobs going over the WAN will fail. We just had a network drop where we only missed one ping between our datacentres, however an active job in Data Protector failed. Below is what occurred in the Session Log:
--------------------------------------
[Major] From: BMA@Site2-Server01.Domain.com "Site1-StoreOnce01-Veeam_gw4 [GW 7380:0:15697104232020443816]" Time: 15/06/2015 1:06:52 PM
[90:51] \\Site1-STOREONCE01\Site1Veeam\042c3c9f_557cc22d_0828_0375
Cannot write to device (StoreOnce error: StoreOnce device offline, network error occurred or secure communication failed while contacting the StoreOnce device)
[Critical] From: VBDA@Site2-Server01.Domain.com "Site2-Backup-Veeam-Prod-Exchange2013-All-Weekly" Time: 15/06/2015 1:06:52 PM
Unexpected close reading NET message => aborting.
[Critical] From: VBDA@Site2-Server01.Domain.com "Site2-Backup-Veeam-Prod-Exchange2013-All-Weekly" Time: 15/06/2015 1:06:52 PM
Connection to Media Agent broken => aborting.
--------------------------------------
This job was backing up files sitting on a Storeonce NAS share in Site2 to a Storeonce catalyst in Site1.
I can see the following values in the OMNIRC on the Cell Manager:
# OB2RECONNECT_RETRY=s
# Default: 600
# Time-out (in seconds) before either a Disk Agent (DA) or Media Agent (MA)
# should stop trying to reconnect to the Session Manager or Disk Agent
# should stop trying to reconnect to the Media Agent during backup.
#
# OB2RECONNECT_ACK=s
# Default: 1200
# Timeout (in seconds) before an agent gives up waiting to acknowledge a
# message from the session manager.
These values have not been defined on the Cell Manager, so the defaults should be taking effect. Are these the only settings that control session timeouts due to a loss of network?
It seems the connectivity between the Cell Manager and the Storeonce devices is very sensitive, is there any way to make it less so?
Cheers
Wal
↧
Re: Backup Navigator collecting issues
Hi Bammboole,
It would be nice to see logs (especailly those from "agent_util_cmd.log") but in most cases NullPointerException in agent core is pointing to communication issues between Navigator and Cell Manager host.
First try to disable iptables on linux machine and re-run data collection:
# service iptables stop
If it does not work you can also check DNS resolutions:
On Backup Navigator host:
nslookup <bn_hostname>
nslookup <bn_ip>
nslookup <cm_hostname>
nslookup <cm_ip>
On Cell Manager host:
nslookup <cm_hostname>
nslookup <cm_ip>
nslookup <bn_hostname>
nslookup <bn_ip>
I can also provide you a tool to simulate collection queries so you don't have to wait for collection to start all over again.
Please, inform me with the results you'll get.
Regards,
Nik
↧
↧
Re: Dataprotector - scheduled copies don't start
Hello,
When I run omnitrig -log, I obtain this message:
Erreur lors de l'analyse de la planification debug.log.
"L'erreur Jeton attendu pour indiquer le mode de sauvegarde."
s'est produite dans l'expression :
********************** dctadmbwp01.prod.gemplus.com ********************** 15/06/2015 03:00:07 OMNITRIG.11276.12016 ["/lib/cmn/win32exe.c $Rev: 30803 $ $Date::2012-05-08 18:37:43":700]
A.07.00 b107 Process exited with exception error 0xC0000142!
15/06/2015 03:00:09 OMNITRIG.11276.12016 ["/lib/cmn/win32exe.c
error 0xC0000142!$Rev: 30803 $ $Date:: 2012-05-08 18:37:43":700]
A.07.00 b107 Process exited with exception error 0xC0000142!
15/06/2015 03:01:32 OMNIB.12072.11640 ["/omnibackup.c $Rev:46606 $ $Date:: 2015-02-06 14:21:04":4207] A.07.00 b107 [Process] CsaStartSession failed! 15/06/2015 03:01:32 OMNIB.12072.11640 ["/lib/cmn/win32exe.c $Rev: 30803 $ $Date:: 2012-05-08 18:37:43":700]
A.07.00 b107 Process exited with exception error 0xC0000142!
15/06/2015 03:02:57 OMNIB.12072.11640 ["/omnibackup.c $Rev: 46606 $ $Date:: 2015-02-06 14:21:04":4207] A.07.00 b107 [Process] CsaStartSessionfailed! 15/06/2015 03:02:57 OMNIB.12072.11640 ["/lib/cmn/win32exe.c $Rev: 30803
$ $Date:: 2012-05-08 18:37:43":700] A.07.00 b107 Process exited with exception
I checked in the event log, the process omnitrig is faulting every 15min...
Exemple in the event log:
Faulting application name: omnitrig.exe, version: 7.0.107.0, time stamp: 0x551a7ebe
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace4e7
Exception code: 0xc0000005
Fault offset: 0x0000000000018b27
Faulting process id: 0x22c8
Faulting application start time: 0x01d0a736d01e61a9
Faulting application path: C:\Program Files\OmniBack\bin\omnitrig.exe
Faulting module path: C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_08e61857a83bc251\MSVCR90.dll
Report Id: 111a51da-132a-11e5-bc52-00215af01fc0
Do you ever this a problem like this?
Regards,
François BRETON
↧
Re: Dataprotector - scheduled copies don't start
Appears omnib is faulting, causing omnitrig to fail before it comes to the Copies.
Are you sure all your Backup-Jobs are started properly?
I'd expect at least one of them to not be executed, indicating a faulty Schedule-File or malformed Datalist/Barlist.
↧
Re: Options for new Cell Manager
Default for MaxBSessions is 100, so no use to set it unless you need more
SmWaitForDevice is counted in Minutes, don't think you want it to wait 60 hours.
Suggest to set these two in case you intend to use bigger BAR-Sessions like VMware:
SmWaitForFirstBackupClientSec
SmWaitForNewBackupClientSec
The SessionStatus* are a question of taste, set them as you please
Do not set OB2SHMIPC unless you really really need it, causes process overhead and impacts Performance quite a bit (10-25% performance reduction on a MediaServer for example)
OB2IPCNOSENDRECVLOOP=1 is a MediaServer variable, since you don't want to use the CM as such it wouldn't do much.
The IPC Keepalives are fine, just be sure to also check the OS-Settings since they only work in combination.
Some options you may also consider:
OB2PORTRANGE/OB2PORTRANGESPEC - in case you want to backup DMZ
OB2INETTIMEOUT, OB2DBRETRY,OB2INETTIMEOUT - in case your VM performance varies and you want avoid session aborts caused by that
OB2DISABLEIPCERRDBGLOG, OB2DBGDIR - for better Debuging/Logging
OB2RECONNECT_RETRY, OB2RECONNECT_ACK, OB2SKIPDIRECTORY, OB2NOREMOTEWARNINGS - for the DA on CM, totally optional
↧
Re: Data Protector 9.0 and StoreOnce
That is true for the Appliance-Version
There the other option available in DP is the StoreOnce Software Store, an Agent-Modul to acompany the MediaAgent.
the Software Store was quite instable in the past, no experience how it is with 9.03. Requires the normal Advanced Backup to Disk License to be used.
↧
↧
Re: DataProtector 9 Storeonce Network Sensitivity
There are way more Options that influence Timeouts but those two should be a good start, f.E. set them like this on DA and MA:
OB2RECONNECT_RETRY=3600
OB2RECONNECT_ACK=3600
Also configuring KeepAlive may help:
OB2IPCKEEPALIVE=1
OB2IPCKEEPALIVETIME=900
OB2IPCKEEPALIVEINTERVAL=60
But in general try to avoid Backup via an unstable WAN-Link if possible. StoreOnce Replication should be way more resiliant than a normal Backup is.
↧
Re: Cannot include more than one VMware VM in a backup job
is it working with any particular single VM or is maybe a specific combination of VMs the Problem?
Have you tried the Job in Debug-Mode to get more Details on why the SystemCall may abort? f.E. insufficient Memory or Space.
↧
Data Protector issues following upgrade from 6.2 to 7.0.3
Hi,
We have recently upgraded to Data Protector 7.0.3 from 6.2 and onto a new server with a different name.
When I look at the monitor section of the gui I am finding that the owner of any "transferred" backups is still root at the old server name. Any new backups are correct with root at the new server name.
i.e. a backup from the old server now running on the new server will have the owner as -
root.sys@"old-server-name".domain
A new backup running on the new server will have the owner as -
root.sys@"new-server-name".domain
Can the old backups be changed so that the owner is root at the new server or do they have to be created from scratch for this to happen?
Many thanks - Mark P.
↧
Data Protector issues following upgrade from 6.2 to 7.0.3
Hi,
We have recently upgraded from Data Protector 6.2 to 7.0.3.
I am having trouble reading SDLT tapes on SDLT drives (old technology). This was fine at 6.2 but now at 7.0.3 the tape read just hangs. It is not the tape as I have tried many tapes and it is not the drive as we have two SDLT tape drives and the issue is occuring on both of them.
I think I read somewhere that the tape hang does eventually time out after a large amount of seconds (an eight figure number of seconds?) but at the moment I am having to kill it from the unix prompt.
I believe this might be a known bug?
Any advice gratefully received.
Kind Regards - Mark P.
↧
↧
Re: Data Protector issues following upgrade from 6.2 to 7.0.3
I assume you already did omnidbutil -change_cell_name [OldHost], besides that there is not much you can do.
The Owner of an Object is fix in the IDB and could only be changed by Exporting and manually editing the ASCII Files.
Unless you have very restrictive User-Policies in place this will more or less be just a cosmetic issue.
↧
Re: Data Protector issues following upgrade from 6.2 to 7.0.3
During which action is the Job hanging? Restore, Import, Catalog-Import, Verify?
↧
Re: Data Protector issues following upgrade from 6.2 to 7.0.3
Yes - omnidbutil -change_cell_name [OldHost] was run.
↧