GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- OmniBack post scripts
Operating System - HP-UX
1846136
Members
4951
Online
110254
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
11-08-2000 11:58 AM
11-08-2000 11:58 AM
In setting up and running post backup scripts in OmniBack II (3.5) I have noticed that some scripts written and provided by my DBA did not use an exit code of the form "exit 0" but instead only had the word "exit" at the end of the script or where he wanted to exit the script. This appears to cause OmniBack to believe that the script has not yet completed and to wait the timeout value for OmniBack post script execution and then fail the backup even though it completed correctly including the post script. Is this a known probelm in OmniBack or is it just a case of bad script coding on the part of my DBA. I have corrected the scripts, but have not tested the changes yet.
On call 24 by 7 ... Ooops another beep!!
Solved! Go to Solution.
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-08-2000 12:54 PM
11-08-2000 12:54 PM
Solution
Yes, it is advisable to have an exit code, because the exit code is used by Omniback to determine if all the stages of the backup were successful...and when to proceed to the next stage.
Besides, its good programming practice to have exit codes anyway.
Besides, its good programming practice to have exit codes anyway.
nothing wrong with me that a few lines of code cannot fix!
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP