9/3/2018»»Monday

Hp Rdx Continuous Data Protection Software Download

9/3/2018
Hp Rdx Continuous Data Protection Software

We installed a RDX-320 on 350-G5 with SBS 2008. At that time there was no support for x64 and we got around this problem by installing BAckup Exec on a 60 day trial. This worked ok. We've now installed the x64 drivers and the unit is upgraded to F/W 3032 The software running is HP Continuous data protection version:3.0.512.5393 The software is now prompting us 'insert an HP RDX cartridge to protect the system' even though there is one in there. In fact, the diagnostic utility confirms there is one in there, it has its own drive letter and we can browse it from within Windows Explorer.

I suspect because it's been used (it is now blank - formatted with NTFS) the system doesn't recognise it? How do I re-initialize it so that we can use it with the HP software rather than BE?

Hi, i had similar issues on different installation. On a 2003sbs server, i had to set the sysmon service to 'start manually' and to start it manuallay after reboot to succesfully recognize new tapes.

Now i'm stucked on an xp sp3 pc, which recognized the first tape, but after that, no more tape where recognized. I have tried to start the services manually without success. Both pc have the newest software version xxxxx.5424, and most recent firmware available.

Drivers For Hp Deskjet 960c Windows 7 there. • Insomecases,offlinecartridgesarenotseenintheCartridgestabofRDXmanagement. • TheinstallerfilemustbenamedHP-RDX-Installer.exe. El Jardin De Al Lado Pdf Printer more. Ifyourenametheinstallerfile,you. It comes with two software CDs: one contains the install wizard, a diagnostic/firmware upgrade utility and documentation, while the other has HP's RDX Continuous Data Protection (CDP) Software.

Same symptons: software ask for tape, and utility shows it with a 'good' status. I'm able to eject and so on, but the 'new catridge window won't show up'?

Any help welcomed. Hi everyone, in the mean time, we have been testing a lot of things, lot of trouble recognizing new cadridges.

What we suspected is: depending how the RDX services start and wich user they are configured too (the service itself), they would either recognize new tap or not. In fact, new tape are allways recognized in the mon utility. But the 'new cartridge wizard' will never show. Manual For Xerox Memory Writer 6251 there.

Thats why i'm pretty sure that we all have the same problem! On one installation (sbs2003) i've managed to start the service in the right order to get the wizard shown. I could not manage to find differences beetween the two installation. The hp support told us to update firmware with a 'hidden' version that we received from them, which is not published on the official support and download site. As the firmware-update was not succesfull, they have sent us an exchange unit.

I will replace it in the next days. But i cannot beleive it will change something.

It has to be software/services related. What do you think? I believe I have the same problem, has anyone got any steps to enable the continuous data protection? System Specs: HP ProLiant ML310 G5 Internal RDX Module connected via the internal tape drive USB connector. 320GB RDX Cartridges MS Server 2008 SP1 x64 Drive Firmware: 3040 RDX Util: 2.20 RDX Util DLL: 2.28 CDP Software: 3.0.512.5424 RDX util will recognise all cartridges and shows their status are 'good' However cannot get the CDP to recognise the new cartridge, 'Manage HP RDX' always reports '(no cartridge loaded)'. The new cartridge wizard never appears.

Out of ideas now, anyone have any? Have an identical problem with RDX-160, when inserting the drive it is detected but no prompt for 'do you want to use this harddisk with CDP or as regular HD'. Found out that the process HP-RDX-TRAY.exe is running under a different user. This user has the rdx sys tray icon displayed and is prompted for above question. Killing this job will automatically restart it again, eventually under a different user. We are running this on a terminal server 2008 and it seems it takes the first user in the configuration to prompt.