Hi team,
I've a question related data protector licenses.
I want to generate license for DR site but DR site cell manager has different ip address but same hostname. as primary.
Is it possible to generate license keys on license portal with same host but different ip address?
I've checked on HPE license portal but couldn't find any option.
i'm also not sure, if hostname is important while generating a license keys. Please assist.
Many thanks,
dpx
We have 4 different DP cells that all run as SG packages. We do not use autorun as we want to be involved in any failover in case of IDB corruption. However, my question is should we use a startup command for DP in the SG script. My concern is that is our active DP cell node crashes someone from our server team attempts to start our package on the alternate node without involving our team. We are using the shutdown command as it is somewhat of a safety net.
Curious of others thoughts on this topic...
DP9.07 (2 - RHEL clusters, and 2 HP-UX clusters)
Mt T:
Here is the current error from the log : please enighten whats gong on ?
[root@ret-rh1p log]# tail messages
Nov 9 10:46:13 ret-rh1p xinetd[6008]: START: omni pid=55085 from=::ffff:10.21.3.206
Nov 9 10:46:13 ret-rh1p OB2DBG_StoreOnceSoftware_Debug.txt[64970]: -0800 2016-11-09 10:46:13 StoreOnceSoftware is within the memory capacity limit
Nov 9 10:46:14 ret-rh1p xinetd[6008]: EXIT: omni status=0 pid=55081 duration=2(sec)
Nov 9 10:46:14 ret-rh1p kernel: rma[55085]: segfault at 7fc84ef7c000 ip 00007fc84f4343dc sp 00007ffd98f9de30 error 4 in libserializer_64bit.so[7fc84f408000+52000]
Nov 9 10:46:14 ret-rh1p abrtd: Directory 'ccpp-2016-11-09-10:46:14-55085' creation detected
Nov 9 10:46:14 ret-rh1p abrt[55100]: Saved core dump of pid 55085 (/opt/omni/lbin/rma) to /var/spool/abrt/ccpp-2016-11-09-10:46:14-55085 (80351232 bytes)
Nov 9 10:46:14 ret-rh1p xinetd[6008]: EXIT: omni signal=11 pid=55085 duration=1(sec)
Nov 9 10:46:14 ret-rh1p abrtd: Package 'OB2-MA' isn't signed with proper key
Nov 9 10:46:14 ret-rh1p abrtd: 'post-create' on '/var/spool/abrt/ccpp-2016-11-09-10:46:14-55085' exited with 1
Nov 9 10:46:14 ret-rh1p abrtd: Deleting problem directory '/var/spool/abrt/ccpp-2016-11-09-10:46:14-55085'
Hello All,
I was wondering if there is a possibility of moving the C:\ProgramData\OmniBack directory to a new drive (i.e. E:) after the installation has been in use. I have noticed there are references to that directory in the registry and was hoping there was a documented procedure for this.
(v9.08 is installed on a Windows 2012 server)
Thanks,
Trish
for windows you could try using "junction". This is a tool to help create symbolic links, similar to unix...
see here:
https://technet.microsoft.com/en-us/sysinternals/bb896768
if this helps, please click KUDOS! thanks!
What are the main features in DP 9 in comparison of DP7 & DP8
Kiekeboe,
your MC/SG conf should look like:
/etc/cmcluster/DP # more DP-2.cfg | grep -v "^#" | grep -v "^$"
package_name DP
package_description "DataProtector Package"
module_name sg/basic
module_version 1
module_name sg/priority
module_version 1
module_name sg/failover
module_version 1
module_name sg/package_ip
module_version 1
module_name sg/volume_group
module_version 1
module_name sg/filesystem
module_version 1
module_name sg/service
module_version 1
module_name sg/monitor_subnet
module_version 1
module_name sg/external
module_version 1
package_type failover
node_name <NODE1 short name>
node_name <NODE2 short name>
auto_run yes
node_fail_fast_enabled no
run_script_timeout no_timeout
halt_script_timeout no_timeout
successor_halt_timeout no_timeout
script_log_file $SGRUN/log/$SG_PACKAGE.log
operation_sequence $SGCONF/scripts/sg/volume_group.sh
operation_sequence $SGCONF/scripts/sg/filesystem.sh
operation_sequence $SGCONF/scripts/sg/package_ip.sh
operation_sequence $SGCONF/scripts/sg/external.sh
operation_sequence $SGCONF/scripts/sg/service.sh
failover_policy configured_node
failback_policy manual
priority no_priority
ip_subnet <XXX.YY.84.0>
ip_address <XXX.YY.84.168>
concurrent_vgchange_operations 1
enable_threaded_vgchange 0
vgchange_cmd "vgchange -a e"
cvm_activation_cmd "vxdg -g \${DiskGroup} set activation=exclusivewrite"
vxvol_cmd "vxvol -g \${DiskGroup} startall"
vg vgdp
vxvm_dg_retry no
deactivation_retry_count 2
kill_processes_accessing_raw_devices no
concurrent_fsck_operations 1
concurrent_mount_and_umount_operations 1
fs_mount_retry_count 0
fs_umount_retry_count 1
fs_name /dev/vgdp/lv_etc
fs_server ""
fs_directory /DP9/etc_opt_omni_server
fs_type "vxfs"
fs_mount_opt "-o rw"
fs_umount_opt "-s"
fs_fsck_opt "-s"
fs_name /dev/vgdp/lv_var
fs_server ""
fs_directory /DP9/var_opt_omni_server
fs_type "vxfs"
fs_mount_opt "-o rw"
fs_umount_opt "-s"
fs_fsck_opt "-s"
service_name omnimon
service_cmd /DP9/etc_opt_omni_server/sg/csfmodular.ksh monitor
service_restart 3
service_fail_fast_enabled no
service_halt_timeout 0
local_lan_failover_allowed yes
monitored_subnet XXX.YYY.84.0
external_script /etc/cmcluster/DP/DP.sh
/etc/cmcluster/DP #
unfortunately this level of information in HP DP documentation is not there! I do find HP lacks that detail people require in the guides!
Anyway, with vmware backups you will need a backup host which is normally physical. Make sure all datastore luns are presented to this host. When a backup is performed then the agent will detect the luns are available via the SAN so SAN direct mode will be used. The fastest method is always used as default which is SAN!
I would always run diskpart on the backup host and perform a automount disable and automount scrub before presenting the datastore luns to the host. You dont want those LUNS being re-signatured by windows!!!
hope this helps. Click KUDOS if you have found this helpful.
Hi,
We've just inherited Data Protector and are new to this application. Currently, we have both cell manager and media server on the same server. We would like to move cell manager to another server. Would you point me to the right direction and show me any document, whitepaper abour how to do that.
Thanks,
Long
Thank you very much for the quick reply. I am curious though, what would happen in case of IDB corruption if primary node fails, is it really recommended best practice to have this package auto_run?
Maybe our team is just being to cautious? :)
Perhaps we should consider autorun, knowing that if there is IDB corruption, the failover will not succeed and we will have to become involved regardless?
Hi,
I'm trying to perform a replication of a previous backup session that completed to a StoreOnce 4700 but want to use a different source device. I need to script this so am using the omniobjcopy command.
The command syntax I'm using is:
omniobjcopy -replication -session 2016/11/10-44 -sourcedevice "NewSourceDev" -targetdevice "TargetDev"
The problem is that no matter what I define the source device to be, it defaults back to the original device that was used for the backup. Unfortunately, the original device is behind a firewall and can't communicate with the target device. This results in the error:
[Critical] From: CMA-NET@OriginalServer "OrigBackupDev [GW 3340:1:6224988868828998542]" Time: 10/11/2016 14:49:17
[90:205] Cannot connect to Media Agent (IPC Invalid Hostname or IP Address
System error: [11004] No data record available
) => aborting
However, when I define the object copy (replication) in the GUI it works fine.
Does this happen to anyone else?
DP details:
v9.06 Build 107
StoreOnce 4700 Catalyst Store
Cell Manager on Windows 2012R2
Many thanks,
John
this looks correct and I cant see any other options. Looks like command line limitation....
Hello,
Usually the Data Protector licenses are associated to the IP address of the Cell Manager. If you need to use Data Protector as Cell Manager on another location, you will need to buy a new set of licenses. Please confirm with the Licenses Department.
Regards,
Hello,
Could you please let us know what is the Data Protector version? and OS (include architecture) that you are using with the Cell Manager at this moment and What will be the specifications for the new Cell Manager?
Regards,
Hello folks
I'm new to DP. We run DP 9.05 and the question should be easy for most experts in the forum. We have a Storeonce disk library and a Tape library
Because of some issues with the tape library, a lot of tape copy jobs have failed in the last number of months.
We have a policy set up in a way that our backups go to the Storeonce disk library and then a copy job to tape. if the tape copy jobs are successful, their "parent" backup job on the StoreOnce is expired and removed from the StoreOnce after 5 weeks.
The large number of jobs that failed the tape copy have been left on the StoreOnce and the protection is Permanent and are taking a lot of space in the disk library see attached picture
How can I push these images flagged with a Permanent protection (shown in the picture attached) to tape so that they are set to expired in the StoreOnce device and free up space ?
Thaks a lot
Calleghf
I have the MSL8480 running firmware 4.90 (tape are LTO6) , our cell manager(Linux server) is runnning DP9.06, we tried enable drive based encryption and had to back out,due to errors we wer getting with tapes devices.
[Major] From: BSM@server.domain.muntul.co.za "XX_XYZ_File_Encrypt_Test" Time: 2016/11/09 02:47:49 PM
[61:1005] Got unexpected close from BMA on server.domain.muntu.co.za.
Our understanding is with LTO6,there are no licenses required for drive based encryption. Is there anyone that has a clear guideline on the issue.
thanks in advance
Dibate
Hello everyone.When i take backup with dp i have an error like this:
[Major] From: VBDA@socecmdb "C:" Time: 11.11.2016 10:21:23
[81:1009] It was not possible to create volume snapshot for 'C:\'. System error: 'VSS Snapshot creation failed'.
[Critical] From: VBDA@socecmdb "C:" Time: 11.11.2016 10:21:23
Fallback to legacy filesystem backup was not allowed. Aborting the backup.
[Critical] From: VBDA@socecmdb "C:" Time: 11.11.2016 10:21:23
[81:52] /C
Not a valid mount point => aborting.
Please if someone know how to resolve this problem.Help me..
Thanks everyone
PLease install xinetd rpm in that server and re-start installation. You can the rpm from the same ISO image when you mount.
The plugin requires ESXI 5.5.1 (AKA 5.5U1);