Netbackup Error 199
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet NetBackup for Microsoft SQL Server database agent backup failed with Status Code 199 Article:000036605 Publish: Article URL:http://www.veritas.com/docs/000036605 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem NetBackup for Microsoft SQL Server database agent backup failed with Status Code 199 Error Message operation not allowed during this time period Solution An MS-SQL-Server policy must contain a schedule of type Application Backup. If a backup is attempted during a period where there is no open window in the Application Backup schedule, the backup will fail with Status Code 199 (operation not allowed during this time period). To resolve this issue, modify the Start Window of the Application Backup schedule so that there is an open window covering, at least, the expected backup time period. An Application Backup schedule called Default-Application-Backup and with a 24x7 open window is set automatically when an MS-SQL-Server policy is created. Except for selecting the desired retention level, it is generally recommended to accept the default settings for this schedule. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been madeGovernance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup https://www.veritas.com/support/en_US/article.TECH66372 and Recovery : NetBackup : Status code 6 and 199 (DESPERATE HELP NEEDED!) VOX : Backup and Recovery : NetBackup : Status code 6 and 199 (DESPERATE HELP NEEDED!) Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer https://vox.veritas.com/t5/NetBackup/Status-code-6-and-199-DESPERATE-HELP-NEEDED/td-p/489511 Friendly Page Solved! Go to Solution Status code 6 and 199 (DESPERATE HELP NEEDED!) Chronos Level 4 02-25-2012 08:09 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Guys, I've been battling for serveral months now a pesky problem related to SC 6 and 199 for two schedules of the same policy. Basically, every Saturday at around 5:30AM, one of my schedules fails invariably with SC 199, while the other completes successfully the first time, but fails about 12 min later with SC 6. I'm running 6.5.3.1 on my master, and the client is Solaris 9. This is how it looks like (pm**** is the client, pb***** is the master): root@pb*******:/ # bpdbjobs | grep hdb-rman | more 339027 Backup Done 199 hdb-rman archivelogs_app pm****** 02/25/12 05:42:32 339024 Backup Done 199 hdb-rman archivelogs_app pm***** 02/25/12 05:31:32 339023 Backup Done
schedule with an open backup window. This error implies that an appropriate policy and schedule combination exists for this client. netbackup error 199 Recommended Action: Determine the policies to which this client belongs that also have a schedule of the appropriate type (either user backup or archive). If possible, retry the operation when the backup window is open. If the backup window is not open during appropriate time periods, adjust a backup window for a schedule in one of the policies.
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum Error failed 199 on changing volume pool thread776-1329238 Forum Search FAQs Links MVPs Error failed 199 on changing volume pool Error failed 199 on changing volume pool sosasap (TechnicalUser) (OP) 31 Jan 07 18:09 A tape was added to the robot but cannot change volume pool from netbackup to scratch.I keep getting failed 199 on the change command. RE: Error failed 199 on changing volume pool nbkp25v (TechnicalUser) 3 Feb 07 20:54 Has the media been written to??If there is data on the tape that has not expired, the media will not be able to be moved to a different volume pool.Run the following to see if the tape has a 'Time Assigned':Unix:/usr/openv/volmgr/bin/vmquery -m