Let's say I have a job that has been running for numerous hours and is only half way through the job and I need to patch and reboot the server. Can I suspend the job so that I don't lose the progress I have made up to that point.?
Thanks,
Randy
↧
Can I suspend a session?
↧
(DP) Support Tip: Data Protector supports now backup of Virtual Machine disks in parallel
Virtual Environment Integration (VEA) agent VMware integration supports backup of Virtual Machine disks in parallel using Data Protector 9.05
Two omnirc varaibles can be used to manage this behavior:
OB2_VEAGENT_THREADED_DISK_BACKUP = 1 (default)
This variable is used to enable/disable the threaded disk backup. By setting to 0, the disk objects are backed up serially.
OB2_VEAGENT_DISK_CONCURRENCY = 10
This variable is used to increase the number of disk parallelism. By default, 9 threads will be run in parallel, with atleast one thread.
↧
↧
Download HP Data Protector 6.20 (A.06.20)
Hi There,
Where I can find an active link to download HP Data Protector 6.2 (A.06.20) ?
I'm really need this SW, and all of my searchs didn't provided me a efective solution.
Thank you in advance,
Regards,
Marco
↧
Download HP Data Protector 6.20 (A.06.20)
Hi There,
Where I can find an active link to download HP Data Protector 6.2 (A.06.20) ?
I'm really need this SW, and all of my searchs didn't provided me a efective solution.
Thank you in advance,
Regards,
Marco
↧
DP 9.05 unable to write with 512Kb on StoreOnce VSA
Hello,
I'm trying to setup DP 9.05 (windows Media Agent) and StoreOnce VSA (emulating MSL G3 tape library) as per best practices. I'm following this article https://goo.gl/uLSL6W, but when the backup job starts, it fails with error "[90:51] Tape0:0:1:0C Cannot write to device ([87] The parameter is incorrect. )".
If I set drive blocksize to 64Kb, the job runs.
The O.S. event viewer doesn't report anything about DP activity.
I'm doing something wrong?
Thank you
regards, Davide
↧
↧
(DP) Support Tip: DCBF update after DP 6/7 to DP 8/9 update
Some info can be found in the DP Installation Guide, read this first.
The following document will enrich the given information.
Introduction:
Let´s take the file names of the backed up files to explain the difference in the pre DP 8 and the post DP 8 IDB.
In DP 7 and older, the names of the files that have been backed up are stored in the fnames.dat file (and extensions).
In DP 8 and later, this information is stored in the new DCBF files (version 2).
What happens during an update from DP 6/7 to DP 8/9?
When updating DP 6/7 to DP 8/9, these file names are not converted from the old IDB files to the new DCBF files of version 2.
The DP code is able to read these old files, although the old database engine is not installed anymore.
So we have a fully functional IDB after the update and detail file browsing for restore is possible.
What will happen after the update?
New media will get a DCBF file of version 2.
Old media that is appended will have 2 DCBF files, an old one of version 1 and a new one of version 2.
Old media that is full will expire over the time and the DCBF files that belong to it will be deleted by DailyMaintenance.
Old media that is permanently protected will not expire and keep the old DCBF file and will depend on the old fnames.dat file for restore file browsing.
What is the recommended way to deal with this?
In case no permanent protected media is used, it would be possible to wait until all old media is expired.
After the old media is expired, the DCBF files are gone anyway and after the last media is expired,
the fnames.dat file (and it´s friends) are not needed anymore and can moved to a safe location first and deleted after some time.
See the last part of "How can a DCBF file migration be done?" on how to remove them.
In case permanent protected media (or media that is protected over a long period of time) is used, it is recommended to do a DCBF file migration.
How to determine the current status?
The following commands give an overview and show what media is pending migration:
# omnimigrate.pl -report_old_catalog
Old Detail Catalog Binary Files size:
DCBF ( 268 files): 4573 MB
Old filename data files: 6373 MB
Total: 10947 MB
# omnimigrate.pl -report_old_catalog media
Media that require old Detail Catalog Binary Files:
Medium ID Protected Until
================================================================================
c0a83220:4d3e9a36:55eb:0029 Permanently
c0a87804:4271e7b1:1550:0003 Permanently
...
c0a83206:54899f86:20aa:0009 2016-1-8 2:50:1
Total number of media: 268
How can a DCBF file migration be done?
omnimigrate.pl -start_catalog_migration will start the migration.
It can be monitored by omnimigrate.pl -report_catalog_migration_progress
After the migration of the DCBF files, you can use the following command to check for any remaining DCBF files:
# omnimigrate.pl -report_old_catalog
Old Detail Catalog Binary Files size:
DCBF ( 0 files): 0 MB
Old filename data files: 6373 MB
Total: 6373 MB
Once we see 0 old DCBF files, omnimigrate.pl -remove_old_catalog can be used to remove the old filename data files.
The global parameter SupportOldDCBF=0 must be set to prevent that the DBSM process attempts to read the old filenames data files (even if they do not exist anymore).
Not setting this parameter can lead to delays during restore browsing activity.
Troubleshooting
Logs can be found in the default DP log directory. They are named omnimigrate*.log
In case of trouble while conversion of a specific DCBF file, the migration can be run only for this DCBF file in debug mode.
Example syntax: omnimm -upgrade_dcbf c0a83220:4d3e9a36:55eb:0029 -debug 1-500 mig.txt
↧
Backup protection for "Completed/Failures" DP 9.01
A few of our jobs have status: "Completed/Failures". From what I can tell, the objects from these sessions are NOT getting the data/catalog protection set in the job . Instead the data/catalog/IDB info is disappearing after only 30 days.
This has been going on for a while, and since the jobs 'completed', everything seemed ok.
What I really don't understand is why the IDB sessions are disappearing, I thought that info never went away. I can't even see (in the IDB) information from a session from 31 days ago!
↧
81:76 Cannot perform stat on two configuration objects sind Update 9.05
on two domain controllers:
Minor] From: VBDA@dom02.ads01.ekt.ch "CONFIGURATION:" Time: 12.01.2016 07:10:11
[81:76]
Cannot perform stat(): ([3] Das System kann den angegebenen Pfad nicht finden. ) => not backed up.
since we have updated to HP DP V. 9.05 before that we have no problems.
thx for help
↧
(DP) Support Tip: DP IDB backup consistency failed + "Schema consistency -schema_consistency Failed"
Problem
A Data Protector (DP) Internal DataBase (IDB) backup fails with "Check of the Internal Database consistency failed"
An `omnicheck -extended` has
"Schema consistency -schema_consistency Failed"
Solution
If this is an occasional error you can run `omnidbutil -set_schema_crc`.
Also, make sure your Data Protector patching is up to date.
If your patching is up to day and the error is a regular one it should be logged with DP support.
DP support would likely require the debug trace file created by the command.
`omnidbcheck -schema_consistency -debug 1-331,333-500 SCH.txt`
↧
↧
(DP) Support Tip: omnirc setting recommendation for DP CMs where ECC is implemented.
There is an omnirc setting we strongly recommend for Data Protector (DP) Cell Managers (CM) where ECC (Encrypted Control Communication) is implemented...
OB2_DNSTIMEOUT=2
It changes the OB2_DNSTIMEOUT value from the default to 3 (we count 0, 1, 2).
It is the number of dns lookup attempts for every client. The default is 30.
With 30 attempts per client, and ECC, we often see strange performance problems, timeouts, or hangs of crs, or bsm.
If the CM can not lookup a client in 3 attempts, there is little advantage in proceeding with an extra 27 tries.
In fact the extra lookup attempts can cause problems.
For this reason please set OB2_DNSTIMEOUT=2 in the omnirc file of all Cell Managers using ECC.
The omnirc (.omnirc on unix) file, by default, can be found as follows...
\ProgramData\OmniBack\omnirc - Windows 2008 and later
/opt/omni/.omnirc - unix systems
The omnirc does not exist by default.
If it is required, make the file by copying omnirc.tmpl (or .omnirc.TMPL) found in the same directory.
↧
Best way to repair access database file
I would recommend a more reliable or professional access file repair tool, that name is Kernel for Access. It can easily repair all Access related issues. Access File Recovery Software is an intelligent solution to fix all corruption issues in ACCDB and MDB database files and saves all the deleted records and objects like indexes, queries, relations and tables, on new database file. It supports most versions of MS Access. Find more details at http://www.nucleusdatarecovery.org/repair-access-database.html
↧
Unable to recover a single file using GRE
I'm trying to recover a single file from a VM image using the GRE, but I'm getting this error:
---------------------------------------------------
Target location: /test does not exist or could not be created.
[Failed ]
Source:/tmp/vmware-root/15305077501532206247_3/downloads/urlparse_replacement.zip
Failed to copy
Recovery failed for one or more files. Check if target location has enough space.
Recovery completed: 01/12/2016 10:56:37 AM
-------------------------------------------------------------------
The SO of the target VM is Linux, I'm passing the root credentials to perform this operation, the folder does exist and everything else works with this VM regarding DP (I can copy and restore files without problems to this machine).
I think it is something i must do client side, but I can't figure what it is. When I do the same for a Windows client, everything works just fine.
The DP version is 9.04
Any ideas?
Thanks!
↧
DP 9 100GB Backup takes 25 hours
DP 9
Windows Cell Manager
I have a Windows server with about 100GB of data files, mostly encrypted image files, that takes around 25 hours to back up. I have a similar server with half a terrabyte of data that takes less than half that time so I do not believe it is a global issue but possibly a setting on this particular server. I have checked and the server hardware is not an issue, it's an HP server that is about 3 years old.
I am just wondering the best way to capture a log to see what is happening or if anyone else has had this issue and the fix. The backup log is clean, no errors, no warnings.
Thanks.
↧
↧
LTO6 Tape Sizes incorrect
Some of our LTO6 tapes have ungodly high values for used/total MB. This is throwing off reporting. Any way to fix this?
↧
(DP) Support Tip: Data Protector 9x and SQL 2012 Availability Group Backup Configuration
During backup creation, the application client is the Availability Group Listener and the application database is the Availability Group Name.
↧
(DP) Support Tip: DP 9.0 `omnicc -check_licenses -detail` gives Licenses Capacity In Use : 0 TB
Problem
On Data Protector (DP) version 9.0 the command `omnicc -check_licenses -detail`, for
"License Category: HP Data Protector - capacity based per TB SW"
reports used capacity as zero eg.
"Licenses Capacity In Use : 0 TB"
Solution
This is a known problem, reference QCCR2A64410.
It scheduled to be fixed in future DP 9.0 patches... 9.05_106
Another similar problem is reference QCCR2A65832 and this is also scheduled to be fixed in DP 9.0 patches (9.05_106).
This information is correct as of 12th January 2016.
↧
(DP) support tip: vmware GRE + OneView - error sending query to service ../GetMountProxies.jsp
You will get this error
->
Http Error - 500
{"message":"Unexpected error:There was a problem while sending query to service https://<hostname>:7116/dp-gui/grePlugin/GetMountProxies.jsp. Check that this agent is accessible."}
<-
when HP OneView for VMware vCenter is also installed. There is a CR (QCCR2A65688) already raised for this issue and currently pending decision by R&D. The issue is also present in DP9.05.
The obvious workaround is to uninstall HP OneView but this is not a viable option for many customers.
I found another workaround which worked for me.
When the "VMware vSphere Web Client" service is restarted with no plug-in executed yet. At this point DP vmware adv GRE will still work. Once customer click on "HP Management" tab, and OneView plug-in is executed, after this point DP vmware adv GRE will fail with the above error.
So when DP vmware adv GRE report the error, the workaround is to restart the "VMware vSphere Web Client" service and make sure not to execute the OneView plug-in by clicking "HP Management" tab, until they have finished with using DP vmware adv GRE.
Hopefully this workaround would be more acceptable, until there is a permanent fix from R&D.
↧
↧
DP9 Storeonce backup size soft quota
I'm getting this warning in backup reports from data protector 9.
The StoreOnce store "Store01" on server "dpmadc3" exceeded the quota of 1450 GB for the cumulative backup size by approx. 79 GB !
I'm not sure I understand these settings, can anyone shed any light on this.
backup size soft quota
store size soft quota
Thanks
↧
General best practices for backup jobs
Is there a recommended best practice for how many filesystems you should include in a backup job?
We have around 500 filesystems and 75 hosts. One large job? One job per host? If one job per host, how do you schedule to go one after another?
We currently have 8 LTO6 drives for a disk-tape file level setup. The nightly incr job runs across all these hosts/filesystems in about 35mins and is normally 350GB. A weekly full runs in 9.5hours and is about 15TB.
↧
incompatible media move
We are running DP 8.10. When I try to move a tape to a particular drive using the web interface, I get an error message saying 'incompatible media move blocked by media barcode ID check'.
↧