Thanks for the reply. We bought our barcodes and they are all unique. Also the same tapes have been in there before this started happening. Our SAN is backed up by a job that this does not happen on. The libraries and servers have been restarted. I am stumped. I have 5 jobs - 2 Full Backups of different servers/SAN, 1-database backup, 1-backup of just one server fileshare, 1-Daily Incremental. The Daily job is the only one with this issue. This also was happening on a job that was set up to just back up the DP database. I only had two tapes for that job. I am not real sure why that does not happen any more but I think it may have been when I deleted the job and recreated. It is a bit of work but I guess I will try that on my other job.
↧
Re: DP 7.03 after backup tapes not showing in slots
↧
Re: (DP) Support Tip: Configuring a backup to use a specific LAN.
Hello,
Thanks for your tips.
i have a scenario of using 2 LAN networks on Vcenter and backup host/Media Agent.
On that case is it similar to yours?
↧
↧
Auto Resume a session with failed backups
Is there a script you can run to Automcatically resume a session after it completes if there are failed backups.
Currently we are just restarting failed objects from a script but would rather it resume.
↧
Restore of multi-streamed backup
One of my clients is looking at replacing their aging LTO-2 environment with LTO-4 drives. However, for reasons of cost, they are looking at going from an 16 drive LTO-2 environment to just a 4 drive LTO-4 environment. LTO-4 has been chosen since it can read LTO-2 tapes. However, the question they have (and I'd be grateful if anyone has real-world experience of a similar scenario) is regarding the scenario of restoring a multi-streamed Oracle backup.
If an Oracle backup has been multi-streamed to 8 LTO-2 drives, what will happen if they try to restore from the 4 LTO-4 drives instead (LTO-2 library now decommissioned but LTO-2 tapes inserted into LTO-4 library)? Will the restore work (and just take longer - changing tapes as it goes) or will it fail (since it can't load 8 tapes simultaneously)? Are there any options to "trick" data protector into allowing the restore (e.g. via changing the original device selection in the restore context menu) or will the restore simply not work unless 8 LTO-4 drives are available at the start of the restore? Given the cost of the LTO-4 drives, it's not something the client wants to consider paying for unless absolutely necessary.
Thanks,
Chris
↧
Re: Encrypting communication between the servers and cell manager & Encrypting data on tapes
Hi All,
I have a similar issue.
We have enabled ECC in HP Data Protector lately in our environment for encrypted communication and post the same backup is running fine and no issues in client and CM.
But we are not able to connect the HP DP Server from clients via HP DP Console from client(Windows 7,8). and get below error wile connecting. We monitor the backups and perform other related tasks remotely from this console.
Connection to CRS failed.
To start the Data Protector daemons on the Cell Manager host use the command
omnisv -start on the Cell Manager
or check if the communication between the Cell Manager and client is encrypted with the command
omnicc -encryption -status -all on the Cell Manager.
Please suggest for the same.
↧
↧
Data Protector - Advanced Scheduler
Hi
We are testing HP Data Protector. In the Advanced Scheduler, I created 2 jobs.
1. Full monthly backup that will run every 1st Friday of the month
2. Incremental daily backup that will run on weekdays.
On the first Friday of the month, there are 2 jobs because the jobs overlap. In Backup Exec, it will only run the less frequent job which is the full monthly backup and it will not run the incremental backup. How about for HP Data Protector? Will it also run the less frequent job or it will run both? Thanks in advance for your help.
↧
(DP) Support Tip: Restoring Virtual Machines when the Original host/cluster is down
While restoring VMware Virtual Machines in Data Protector, we can select the destination datacenter.
This can be done in the "Destination" context, "Restore to datacenter" option.
By default this option is set to "Original Location"
We need to keep in mind that Restoring to the Original Location, does not only mean restoring to the original Data Center but also to the original Host/Cluster and to the original specific ESX host. This is why all the host options are grayed out, because we are enforcing restore to Original Location.
So if the Original Host/Cluster/ESX is down, this restore will fail.
In order to be able to restore to the same Data Center but to a different host, we need to select the Destination data store name without the "(Original Location)" label.
This way we will be able to select a different Host/Cluster and/or ESX host as the destination, and the restore will be successful this time.
Regards
Juanjo
↧
Re: (DP) Support Tip: VEPA backups stop working after 9.05 b106 patches installation
In case it helps some people…
Some users have been confused as to which system they re-install the Vepa agent ("Virtual Environment Integration")
The system you choose to re-install the Vepa agent is the Backup host/Mount proxy host, not the ESXi or vCenter servers.
Go to the "Clients" context of the DP GUI. Expand Clients.
Find the problem Client (Backup host/Mount proxy) with the Vepa agent already installed.
To re-install Vepa agent, right click on Client (Backup host/Mount proxy) hostname and select "Add Components..."
At the next screen ensure the Client (Backup host/Mount proxy) hostname is selected, Next.
Select "Virtual Environment Integration", Finish.
↧
Re: Auto Resume a session with failed backups
Hi,
I am not sure it makes sense to resume objects some time after the backup failed or was interrupted.
Let's say that about 60% of my Filesystem has been backed up when something happens and this backup is interrupted.
Then some time later we want to resume this backup, which I assume means that we want to continue backing up from the same point it was interrupted, and complete backling up the pending 40% of that Filesystem.
But this means that this backup object will not be consistent, we will have mixed objects versions.
What if we were in the middle of backing up a big file when the backup was aborted? Should we resume and backup the rest of that file some hours later when it has probably changed?
What if some files have been deleted/created during the time between the abort and resume?
I would prefer to restart the full object just in case.
Regards
Juanjo
↧
↧
Re: MSL Drive status Yellow Icon
Hi Tommy
This is teh expected bejaviour, as you have had tapes errors and limit for number of errors has been reached drive goes to yellow.
You can modify or disable this using gloabl variable.
# SmDeviceErrorThreshold=MaxNumberOfUnknownErrors
# default: 5
# SmDeviceErrorThreshold >0 is used by session managers to
# define the upper limit of unknown device errors. The device
# will be disabled when number of unknown device errors reaches
# specified value. All other values will disable functionality.
Use value 0 for disable it.
Best Regards
↧
Re: MSL Drive status Yellow Icon
Thank you JBasilio,
I checked that and It was already disabled. I tried several things, shutting down Omnisrv and my GUI client, but nothing appeared to work.
Strange thing is, that this morning, The drive status is normal.. It was yellow last evening, nothing has been done since I brought this to the forum.. Oh Well, nothing like gremlins to keep us on our toes..
I Actually had another drive on a different MSL that had a yellow icon, Disabling and Re-enabling brought it back to normal. That is why I was worried about some deeper issue.
Iam closing this thread. Thanks, Tommy
↧
Q: DP 9.05 // IDB & Backup Scheduler
Hello,
Comming from 7.03 the IDB backup changed from filesystem backup to db backup.
So I've set up a daily IDB backup after all backup/copy jobs finished. Additionally I've set up a filesystem backup of both paths (db/config & bin) too. Now I want to ask if I have to exclude the IDB from that backup (no db backup mode) or could I leave it (second backup)?
Second question is about scheduling backups after backups.
If you don't know how long a backup would run it would be perfect to schedule a backup after finishing another backup. Is there a way to do that? The only way that I think of is, to start a backup with a post-exec script, that starts another backup, but this would be the latest option I would use.
Thank you!
Best regards,
Tobias
↧
Re: Auto Resume a session with failed backups
We backup by object so if a object failed it would backup the whole drive not half the drive and then fail.
What would be the point of having a resume feature in the first place then?
↧
↧
Re: Q: DP 9.05 // IDB & Backup Scheduler
Hi Tobias,
data backed up in IDB specification is automatically excluded in filesystem backup specifications eg:
[ 1] 32. -exclude
[ 1] 33. /ProgramData/OmniBack/config/server
[ 1] 34. /ProgramData/OmniBack/server/db80
etc.
As for your other question: obvious option is post-exec or other option would be to make sessions compete for same device (scheduled at same point) via advanced scheduler and setting priority levels to determine starting order.
↧
Re: installing HP-UX data protector agents
This same solution fixed my HP-UX client using version DP 9.
#swagentd -r
After it installed without issues. Thank you.
↧
Re: Granular recovery to restore send "error 67"
Please provide more information:
What is the Operating system on VM?
DId the VM have a network configured?
↧
Re: Error VMware ZDB Integration with 3PAR. Failed to resolve datastore for vm
OS 3.2.2 will be supported wuith next release of DP (906)
↧
↧
Re: Encrypting communication between the servers and cell manager & Encrypting data on tapes
I believe that software encryption will effectively disable compression on the tape drive.
You might want to consider using software compression instead.
Regards
Jeremy
↧
Re: Q: DP 9.05 // IDB & Backup Scheduler
Hi markovdi,
Automatically? Not really!
That's because I asked. If I backup parallel to the IDB db backup the IDB via filesystem backup, I can select
D:\Program Files\OmniBack D:\ProgramData\OmniBack
and
D:\ProgramData\OmniBack\db40 D:\ProgramData\OmniBack\server\db80
will be backed up via filesystem backup too.
Should I exclude the IDB paths or is it not necessary?
Thanks for the hint with the Advanced Scheduler. I tried it, but to get a quick overview over planned backups, it's not that advanced as it should be. But I will try it the priority!
Best regards,
Tobias
↧
(DP) Support Tip: How to enable CORE dumps on Linux/Unix
You may be asked to provide a CORE dump on a process crash for backline support or as a data collection action plan.
here are the steps to enable CORE dumps on both Linux and Unix
Linux:
mkdir -p /var/core
chmod a+rwx /var/core
echo kernel.core_pattern=/var/core/core.%e.%p >> /etc/sysctl.conf
echo \* soft core unlimited >> /etc/security/limits.conf # permanently ulimit -c unlimited
reboot
HPUX:
mkdir -p /var/core
chmod a+rwx /var/core
/usr/bin/coreadm -e global -g /var/core/core.%f.%p
↧