- Community Home
- >
- Storage
- >
- Legacy
- >
- Automated Backup
- >
- Re: RDX-160 HP-RDX-Sysmon failed to start after 16...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-11-2009 12:20 PM
тАО03-11-2009 12:20 PM
RDX-160 HP-RDX-Sysmon failed to start after 16 minutes
Device successfully installs & begins backup, but once server is restarted (SBS2003) The login screen freezes at the "Applying Computer Settings stage". Was able to boot in safe mode & find in Event Viewer the failed service in subject header relating to the RDX160 device.
Unable to open utility & check backup, or create new jobs on new RDX disks.
HP aware of this problem & waiting for solution since 25th Feb. Anyone else have this problem as HP are aware. Perhaps someone has found a fix for this. Many thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-14-2009 06:32 AM
тАО04-14-2009 06:32 AM
Re: RDX-160 HP-RDX-Sysmon failed to start after 16 minutes
Any news on this??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-14-2009 07:30 AM
тАО04-14-2009 07:30 AM
Re: RDX-160 HP-RDX-Sysmon failed to start after 16 minutes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2009 03:33 AM
тАО04-16-2009 03:33 AM
Re: RDX-160 HP-RDX-Sysmon failed to start after 16 minutes
Right now I have set the service to "Manual" and only start it when i need to recognize a new cartridge. It still backs up and recognizes a "initialized" backup cartdrige when the "HP-RDX-SYSMON" service is disabled/stopped.
Do you know if this software backs up SQL Server / Exchange Online (VSS)?
How about Virtual Server 2005 Virtual Machines?
It does seem to backup the virtual hard disks (.vhd) But at 8 gb per .vhd version it will fill up the cartridge pretty quickly.
It appears to only do file deduplication, but I think I read it somewhere that it would do data(sector,chunk) deduplication. Any ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2009 08:56 AM
тАО04-16-2009 08:56 AM
Re: RDX-160 HP-RDX-Sysmon failed to start after 16 minutes
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-28-2009 01:29 AM
тАО04-28-2009 01:29 AM
Re: RDX-160 HP-RDX-Sysmon failed to start after 16 minutes
This time the server started normally & I was surprised to see that the backup did actually work perfectly. When I contacted HP about this, I was told the old service is not used anymore, but isnt removed.
Problem resolved, although would have been helpful if HP let me know to disable the service in question & avoided another site visit.