Quantcast
Channel: Data Protector Practitioners Forum topics
Viewing all 3189 articles
Browse latest View live
↧

CMMDB - Path away from it?

September 21, 2016, 8:29 am
$
0
0

I inherited an environment with 2 Cell Managers. One acting as MoM for centralized licensing and CMMDB to make life interesting and the other cell manager at another site is tied to it.

I've had 2 outages recently of the CMMDB cell manager and it's caused all backups at the other site to not happen.  The only benefit I've seen so far in the CMMDB is it makes device management easy.  However, being unable to create backups during outages and the potential that Auto Replication Sync doesn't work in CMMDB for my site to site replication, means I need to get rid of it.

I have about a year of backups in the current IDBs at both sites.  I opened a ticket asking about how to go forward and dropping the CMMDB and got a "that isn't supported" response.  

The only positive thing I can find about getting rid of it is this for Version 5.1 and it's dated January 16, 2004: How to go back to local MMDB from a CMMDB configuration

If ARS worked I'd be able to see all the clients backups that replicated from the other site on my local StoreOnce and could perform some 1 offs to LTO6 to capture everything and if need be roll a brand new IDB at that site independent of the primary site.  However, since ARS is failing, I'm looking for ideas on moving forward and dropping the CMMDB.  

I am leaning towards getting disk images of my cell managers and trying out the 2004 instructions and see what happens.   

Any thoughts or suggestions are appreciated.

 

 

 

↧
Search

(DP) Support Tip: Virtual Machine restore "poweron" option

September 21, 2016, 8:50 am
$
0
0

DP 9.07 build

Currently, if backing up virtual machines with the DP "vepa" integration to smartcache, 3par or storeonce, the poweron option on restore is "only" supported if the backuphost selected is linux.  Windows backuphost is not supported. 

↧
↧

VM backups - How to set custom Free Space Required percentages

September 21, 2016, 9:25 am
$
0
0

Using DP 9.07:

I ran into an issue with switching a filesystem backup to virtual environment on a VM that is a document server: and getting a higher available than the required setting.

[Major] Virtual Machine 'VM_NAME': Insufficient disk space on datastore 'DATASTORE' for snapshot creation (required: 10, available 16) ...

The error was reporting just the datastore where the OS of the VM presided.  It has 4 disks across 3 different datastores and one of the disks used 1.8 TB of a 2TB Datastore Volume.  That datastore was showing 9.94% free.

I didn't want to drop to 0% for Free Space Required in the VE Settings for the backup spec as I prefer not to have a datastore feel up 100%.  

P.Louage replied to the ESX VM Backups error Data Protector (insufficient disk space) post with:

"... For the VStorage (VEPA) you must specify a 0-100% (steps of 10%) free space check when creating a backup specification. The % is part of the barlist in C:\ProgramData\OmniBack\Config\Server\BarLists\VEAgent"

The files in there are the backup specs and are the same name as the spec.  

I opened up the VM spec in question, found the "free_space_required=10" changed 10 to 8 and saved the file.  I then ran the job without issue. 

I submitted a documentation feedback on the session report asking for them to add all datastores in the message or more verbage that not all of a VM's datastores are shown in the message.

Hope this helps someone else save some time.



 

 

 

↧

(DP) Support Tip: Enabling OB2BMASTATISTICS can assist in troubleshooting performance issues.

September 21, 2016, 9:44 am
$
0
0

OB2BMASTATISTICS=2
#    Default: 0
#    This variable is used to mesure Backup statistics/performance
#    To enable this varaible set environment variable OB2BMASTATISTICS=2 on
#    all Media Agent hosts and collect files "bmastat.log" from system
#    (Media Agent: <OmniBack_home>\log).

This variable is enabled in the omnirc file on the media agent hosts.

Information regarding performance is also logged in the DP Session Report and the debugs if debugging is enabled.

↧

Connection to CRS failed on DP 6.11 installation

September 22, 2016, 2:16 am
$
0
0

Hi!

I am having issues trying to connect from the GUI to cell manager. The cell manager server which at the same time is the installation server is running hp-ux 11.31, and I have installed DP 6.11 on it. It implies that DP services are down, but:

./omnisv -status
    ProcName  Status  [PID]
===============================
    rds     : Active  [13750]
    crs     : Active  [13754]
    mmd     : Active  [13752]
    kms     : Active  [13753]
    omnitrig: Active
    uiproxy : Active  [13756]
    Sending of traps disabled.
===============================
Status: All Data Protector relevant processes/services up and running.

from the cell manager I can ping any "would be client" by its hostname:

#ping mcelbill
PING mcelbill: 64 byte packets
64 bytes from 10.1.20.21: icmp_seq=0. time=0. ms
64 bytes from 10.1.20.21: icmp_seq=1. time=0. ms
#nslookup mcelbill
Using /etc/hosts on:  mceldev

looking up FILES
Name:    mcelbill
Address:  10.1.20.21

but when trying to connect with cell manager, I get the following:

dp611.jpg

Please can you advise

↧
↧

(DP) Support Tip: Faster method to recover DataProtector on UNIX

September 22, 2016, 6:56 am
$
0
0

A faster method to recover from issues with DataProtector on a UNIX cell server (HP-UX, Linux) would be to copy the three DataProtector directories on the UNIX  cell server :

      /etc/opt/omni/       /opt/omni       /var/opt/omni

Now, the Data Protector software should be shut down in order to get a clean copy with "omnisv stop".  The steps are below ;

       1. omnisv stop

       2. cd /etc/opt;  cp -R omni omni_etc_opt_bck

       3. cd /opt;  cp -R omni omni_opt_bck

       4. cd /var/opt;  cp -R omni omni_var_opt_bck

       5. omnisv start

Steps 1-5 could be done daily and even through cron depending on your backups.  You could certainly store each of the omni_*_bck directories on another machine.  If files get corruped in Data Protector, then it would be easy to shut down Data Protector with omnisv stop and bring the 3 directories back into the original location and import any media that has been written.

↧

(DP) Support Tip: Single Object per Store Media

September 22, 2016, 7:04 am
$
0
0

Hi,

 

"Single Object per Store Media" is a property of a Data Protector StoreOnce device which can be enabled in the Settings tab. If not set and a session is serially backing up objects (that is when there are more objects than available data streams to the store, limited by "load balancing MAX value" and "Max. number of Connections per Store" and Max. Number of Parallel Streams per Client System") then multiple objects will arrive onto the same store item and DP medium. This may not be desired and can be prevented by setting "Single Object per Store Media" in the following cases:

 

  •  Protection time is not equal across objects
  •  Object operations will use the media as a source
  •  Customer just finds it nicer to have the one-to-one relationship between media and object version

 

However, when the backup session includes a large number of very small objects the the usage of this option is not recommended as it will create many store items / DP media which may decrease performance or even introduce other issues.

 

Koen

↧

(DP) Support Tip: BSM reports "Too many backup sessions are running in parallel."

September 22, 2016, 12:12 pm
$
0
0

　

If you are seeing the below message during backups, consider installing the 9.07_110 patch for the Cell Manager and enabling the new option OB2IGNOREPARALLELSESSIONS to skip the check.

　

　

|Normal| From: BSM@<hostname> "" Time: <Date><Time>

|61:2050| Too many backup sessions are running in parallel.

Session is waiting for some other session to complete.

　

 

 

↧
Search

(DP) Support Tip: Stopping StoreOnceSoftware stores.

September 22, 2016, 10:47 pm
$
0
0

Hi,

 

Before stopping the StoreOnceSoftware service/daemon, all stores should be stopped first. That can sometimes take a long time. If there is no time to wait then the --force option should be used:

 

StoreOnceSoftware --stop_store --name=<STORE_NAME> –-force

 

This will close existing connections to the store. This is the cleaner and preferred way. Killing the StoreOnceSoftware service/daemon should be avoided at all times.

 

Koen

↧
↧

Oracle: spfile backup

September 22, 2016, 10:56 pm
$
0
0

I don't understand if DP 8.13 is able to backup the single Oracle spfile and to restore it.

 

↧

Problem in Data protector incremental backup

September 25, 2016, 4:37 am
$
0
0

I have the same issue, I'am running on dp 9.07.

But the bizar thing is dat I have this only when I run an incr backup, when I run a full I don't get this error on my backup job.

 

[Major] From: OB2BAR_VEPA_BAR@bu-dco06.bel.centric.lan "/Oostkamp"  Time: 15/09/2016 22:53:09
 Aborting connection to BSM. Abort code -1.

↧

Deduplication is not supported on clusters

September 25, 2016, 4:37 am
$
0
0

When Source Side Deduplication Gateway device configured on cluster node it should failed with the following :

[Major] From: BSM@Cell_Manager_hostname.xxx.yyy "backup_specification" Time: 31.03.2016 09:18:52

Got error: "StoreOnce error: StoreOnce device offline, network error occurred or secure communication failed while contacting the StoreOnce device" when contacting "Device_on_GW" B2D device!

In order to workaround this failure need to configure GW device on agent that is not a part of a cluster .

 

↧

Virtual Machines backup not using all devices as selected on backup specification

September 25, 2016, 4:53 am
$
0
0

Virtual Machines backup used only 10 devices although more than 10 drives were selected on backup specification and concurrency set  30 ( Min=1, Max=30)

Reason for this behaviour is that OB2_VEAGENT_DISK_CONCURRENCY variable limits disk threads to be started in parallel for no more than 10 . 

In order to change this behaviour need to modify omnirc file on backup host and set OB2_VEAGENT_DISK_CONCURRENCY to value higher than 10 .

Note that setting OB2_VEAGENT_DISK_CONCURRENCY omnirc variable to low value will decrease backup concurrency and will avoid lack of hardware resources.

↧
↧

While upgrading DP 7 to 9.07, Hyper-V backups failed... From VEPALIB_HYPERV Internal Error.

September 26, 2016, 3:12 am
$
0
0

Hello Everone, Thought I'd share this information in case it helps others...

Problem
-------
During a DP 7 to 9.07 upgrade, after upgrading the DP 9.07 Cell Manager and the Hyper-V 2012 R2 clients in a particular Hyper-V Cluster, backups failed...
From VEPALIB_HYPERV
Internal Error.

The same Hyper-V backup specifications had worked OK at DP 7.

From debugging the problem it could be seen that DP was trying to contact other Hyper-V clients configured in the cell.

Solution
--------
Two steps that solved the problem...
- Any clients imported as type Hyper-V that could not be upgraded were removed from the cell (using the GUI, Clients context).
- All clients that are imported into the cell as type Hyper-V were upgraded, whether they were in the same Hyper-V cluster or not.

After that all the Hyper-V backup specifications ran without error.

↧

DP9.07 - VMware backups - use of multiple devices greyed out

September 27, 2016, 8:36 am
$
0
0

I am configuring some new vmware backups with DP9.07 and writing to 2 x D2D 4700 appliances. Using catalyst

I have a gateway for D2D_A and a gateway for D2D_B....In the vmware backup specification I cant select more than one device (destination). Once I select one, the other gets greyed out.

I can perform this for other types of backups but not VMWARE. Is this a bug??

↧
Search

(DP) Support Tip: Debugging OpenVMS clients

September 27, 2016, 10:10 am
$
0
0

There are 2 possible ways to enable debugs an OpenVMS client:

1)

- $ edit OMNI$ROOT:omnirc.
OB2DBG=1-99 Debugs.txt

And restart services:
- $startup:omni$shutdown.com
- $startup:omni$startup.com

2)

- $startup:omni$shutdown.com

- Change INET startup script with:
$ edit OMNI$ROOT:[BIN]OMNI$STARTUP_INET.COM

- Change the folloiwng Line:
$ INET="$OMNI$ROOT:[BIN]INET.EXE"
To:
$ INET="$OMNI$ROOT:[BIN]INET.EXE -debug 1-99 Debugs.txt"

Start DP services
- $startup:omni$startup.com

↧

DP9: [61:1002] Inactivity timeout on CONFIGURATION object

September 27, 2016, 11:41 pm
$
0
0

We do currently face some problems on different jobs where we are running a backup of the complete machine (see the error below):

If I unselect the CONFIGURATION object the job runs without any error. If I create an additional job with ONLY the CONFIGURATION object this one also completes without error. As soon as it is within one job we see the following error:

[Major] From: BSM@xxx.yyy.zzz "XXX" Time: 28.09.2016 03:20:36
[61:1002] The BMA named "XXX [GW 3836:1:4014134147542123963]" on host xxx.yyy.zzz
reached its inactivity timeout of 8400 seconds.
The agent on host will be shutdown.

[Major] From: BSM@xxx.yyy.zzz "XXX" Time: 28.09.2016 03:21:15
[61:1002] The BMA named "XXX [GW 3836:2:4014134147542123963]" on host xxx.yyy.zzz
reached its inactivity timeout of 8400 seconds.
The agent on host will be shutdown.

We're currently running DP 9.07_110, but we did see this already in earlier DP9 versions.

Any suggestions?

↧
↧

Client Installation agent

September 27, 2016, 11:47 pm
$
0
0

Hi 

currently i have DP 9.0, i have got a few new server to add in DP 9. i need to know which client agents do i need to install during the client installation. below are the type of server 

1. Domain controller   ( Physical Server)

2. Additional domain controller ( Virtual Hyper-v server)

3. Remote Gateway RDS 2012 ( Physical Server).

4. Application server including SQL on it  (Virutal Hyper-v VM) i need to take full image and SQL Level backup.

Thank you 

↧

DP GRE Plugin Problems with Smartcache on MS-Cluster

September 28, 2016, 1:51 am
$
0
0

Hello!

 

We have DP 9.07 and VSphere 5.5.

After New GRE-Request in WebClient we want to browse the disks. Then we get an error:

Error while trying to get the partitions for the disk(s).
Unable to present shared disks - Invalid parameters to access share.

The Backup of VM was done to a SmartCache-Device. This device is located on a MS-Cluster 2008-Node.

If we take the backup of VM to an SmartCache-Device located on a Standard Server (not MS-Cluster) we do not have any problems.

I did not found any support-matrix for this constalation.

Is it correct, that a smartcache have to reside on a standalone-Server?

 

rg

hansi

 

 

↧

Advanced backup to disk - data protector 9.07 - StoreOnce catalyst

September 28, 2016, 2:54 am
$
0
0

Hi ,

I'm currently installing a new license "Advanced backup to disk" and want to backup over COFC to catalyst stores.

license capacity is 300TB and i'm curious if i can use Catalyst store for it or it is for VTL only?

Data protector 9.07, storeonce 6500 3.15

Please suggest.

Many Thanks,

Dpx

 

 

↧
Viewing all 3189 articles
Browse latest View live
Search