Hi,
First of all DP 7.x does not support VMware 5.5 so you should consider upgrading. If you don’t get this init phase done in 600 s (create snaps / resolve vms) so no Starting Backup for ... you will get this abort. It depends on the load on vCenter and how much this takes. I would suggest that you increase this timeout in global file.
Best regards,
Damir
This is a workaround I've used before. Either copy the spec in GUI or in filesystem. I still can't believe that the basic feature "disable client" does not exist.
Please open an Enhancement Request from the following site
https://support.openview.hp.com/enhancement/do/main
so that you can ask this question directly to the developers. I was giving you my take on this, have looked for something more official, and have not found anything
I thought, at first, that you could use s template, but, checking the pre-existing templates, there is no Backup Object Summary
I checked the 'global' file, and saw nothig about this, but, I wouldn't expect there to be anything there, since 'global' is exactly what the name implies, that is, for all systems in the cell, but is mostly for Cell Manager environment variables
Last, I checked the 'omnirc' template. All I found that was even close was
# OB2SKIPDIRECTORY=0|1
# Default: 0
# Setting the variable allows the backup option -skip for directories, not
# only files.
So, if you are aware of an environment variable that will skip a specific file, it is not documented
Some of the other folks who contribute to the forum may have found something useful that pertains to this
Hi,
I think that incremntals are supported from Win 2012 and higher. Need to check this though.
Best regards,
Damir
Hi,
DId you by any chance look inside the logs to see if you can find any additional infromation why did putting of the IDB into backup mode failed?
Hi,
I need some info for this:
You have set snapshot handling to single/mixed?
Your full CBT backups are passing?
You are using VMFS datastores?
This is happening for all VMs?
Hmm yeah, HPUX 11.11 is a problem :(.
I would suggest this.
1) Upgrade PA-RISC to DP 6.2. It's a straightforward upgrade - just omnisetup.sh.
2) Follow the DP 6.2 Installation & Licensing Guide on how to migrate from PA-RISC to IA-64.
3) Once everything is working in the IA-64 upgrade it to DP 7.0 (another simple omnisetup.sh).
I have extracted the relevant pages for you.
Hi,
Any LTOx drives will accept LTOx and LTOx-1 tapes. The different product numbers listed are only whether the drive is half-height or full-height.
You can order any LTO5 and LTO4 tapes from the market, though we would recommend HP tapes :).
You can probably program a script to read cell_info and output the client name into omnicheck.
You can actually move the client to it's own backup specification, and then disable the schedule as and when required.
You can have multiple MAs connecting to the same store. It's just a configuration in the StoreOnce gateway option (add more gateways). I believe the whitepaper lists this option. The MA function is independent of the StoreOnce software (SOS) function.
You can use source-side (client) or server-side (dedicated MA) deduplication on location A and then transfer the data to location B. Or, if you feel the bandwidth is still not sufficient, setup a StoreOnce store in location A and then perform object copy to location B.
Actually this parameter influences the GUI behavior. If a single existing file in a directory has been deselected using the DP GUI, then the directory still exists in the backup definition…only the deselected file is entered in the exclude list.
Without this parameter, once you deselect the file. the GUI automatically deselects also the directory.
It is not a parameter for excluding a (certain) file from a backup...the parameter influences the GUI usability as described above.
Thanks Alex,
the DP deduplication manual is not clear about store versus store segments (store domain) - it is not clear when they talk about store (with segments) and when about individual store segments.
I was wrong, the individual store can be accessed by only one B2D device, but B2D can have many gateways. So by seleting appropropriate gateway I can limit data flowing between my locations.
According to documentation, object copy to another dedup store should copy the deduplicated data (chunks). I assume that object copy will send set of object chunks along with "description" how to assemble the object from the chunks and target storage matches them against their chunks.
Kind regards, Jan
But this would mean we'd have only a single data stream per job. With > 1000 clients that no option.
I have some tapes in here that I can not format. When I right click on the tape, the format option is not available. I am looking at these tapes from inside Media\Pools.
If I go to Devices\devicename\Slots, the Format option is available but I am not seeing the tapes that I need to format.
If I go to Media\Pools and right click on the All backup Jobs, where all these tapes are located, I can select Format. I tried formatting these tapes, and it looked like it ran, but when I checked when the format job got done, all the tapes are still unformatted.
"If I go to Devices\devicename\Slots, the Format option is available but I am not seeing the tapes that I need to format"
If this is the case, are you sure that the tape is in the library?. You may want to do a Barcode scan (if available) to update the IDB as to what tapes are in the library
Your screen shot did not provide enough detail to make further assessments. In the Media Pool, right-click on this media, and pick Properties. if it is in the library, you will see it in the 'Location' line, for example, looking something like
[Tape Library: 21]
which would mean that it is in the logical library named "Tape Library" in slot 21
Hi,
Your physical Cell-Server was damaged.
So we install a virtuall Server install DP 8.1 (same Version as befor) and overwrite the new programdata with the old.
When we make a backup from some folders on the exchange server it works correct.
But we can not backup exchange.
We receive this massegs:
[Normal] From: BSM@cellsrv01.abc.corp "BTV_ABCD_MSEX2010_DB_Daily" Time: 05.09.2014 17:05:42
Backup session 2014/09/05-119 started.
[Normal] From: BSM@cellsrv01.abc.corp "BTV_ABCD_MSEX2010_DB_Daily" Time: 05.09.2014 17:05:42
OB2BAR application on "abcexdag01.abc.corp" successfully started.
[Normal] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:05:58
Analyzing MS Exchange Server 2010+ environment.
[Normal] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:22
Mailbox Databases selected for backup on server mlsoex11.bdo.intra
DAGMBMLSO\ server01
DAGMBZSLU\ server01
DAGMBZSNL\ server01
DAGMBMLNL\ server01
DAGARCHIVMLSO\ server01
[Normal] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:22
Initializing DP VSS Interface.
[Normal] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:23
Starting backup using DP VSS Interface.
[Normal] From: OB2BAR_VSSBAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:23
Performing Full Backup.
[Normal] From: OB2BAR_VSSBAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:23
Connecting to Volume Shadow Copy Service.
[Normal] From: OB2BAR_VSSBAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:23
Gathering Writer Metadata.
[Major] From: OB2BAR_VSSBAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:32
Backup failed.
[Major] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:32
Error occured while executing backup for component DAGMBMLSO(4083790e-fe0f-4cb0-bd4e-0aba99a0de24).
[Major] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:32
Error occured while executing backup for component DAGMBZSLU(66022807-ff8e-438f-8b24-a8f1a7514ce6).
[Major] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:32
Error occured while executing backup for component DAGMBZSNL(353d55bd-0c3b-4f73-a91f-8628f23cba12).
[Major] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:32
Error occured while executing backup for component DAGMBMLNL(3b91bd82-be08-4764-b9c0-dc5cc4e75792).
[Major] From: OB2BAR_E2010_BAR@server01.abc.corp"MS Exchange 2010+ Server" Time: 05.09.2014 17:06:32
Error occured while executing backup for component DAGARCHIVMLSO(635199b8-bd0f-411d-9ff7-59f52203ba8e).
[Normal] From: BSM@cellsrv01.abc.corp "BTV_ABCD_MSEX2010_DB_Daily" Time: 05.09.2014 17:06:33
OB2BAR application on "abcexdag01.abc.corp" disconnected.
[Critical] From: BSM@cellsrv01.abc.corp "BTV_ABCD_MSEX2010_DB_Daily" Time: 05.09.2014 17:06:33
None of the Disk Agents completed successfully.
Session has failed.
[Normal] From: BSM@cellsrv01.abc.corp "BTV_ABCD_MSEX2010_DB_Daily" Time: 05.09.2014 17:06:33
Any ideas?
Thanks for your help
Fipe