Drive status shows AVR should be TLD
We have two HP tape Libraries in netbakcup 6.5.4. Both libraries have two drives. All 4 were working fine. 6 months ago I used Tape library 2 to utilize Acronis backup for a temp project. Now I reconnect Tape Library 2 fibers to netbackup and ran “Configure Storage devices”. Tape library 1 works fine. One of the tape libraries 2 drives shows AVR and the other one show Missing Path. I am trying to fix the AVR. I cannot use quick Erase or Label. What do I need to do to change AVR to TLD? ThanksSolved18KViews1like11Comments
Error 2060022: software error Backing up to Disk
Hello People: Here my situation, We have a Quantum DXI for OST Backup to Disk. All my clients do the backup over my Master Server to the Quantum DXI. But many of those client have error 84: Here the error on 2 of clients, The error was the same on other clients: Client 1 2/10/2011 7:36:40 PM - Critical bptm(pid=9304) image write failed: error 2060022: software error 2/10/2011 7:36:40 PM - Critical bptm(pid=9304) sts_close_handle failed: 2060017 system call failed 2/10/2011 7:37:31 PM - Error bptm(pid=9304) cannot write image to disk, Invalid argument 2/10/2011 7:37:41 PM - end writing; write time: 00:39:08 media write error(84) Client 2 2/10/2011 7:36:24 PM - Critical bptm(pid=8396) image write failed: error 2060022: software error 2/10/2011 7:36:24 PM - Critical bptm(pid=8396) sts_close_handle failed: 2060017 system call failed 2/10/2011 7:36:50 PM - Error bptm(pid=8396) cannot write image to disk, Invalid argument 2/10/2011 7:36:50 PM - Critical bpbrm(pid=5204) from client CLIENTNAME: FTL - tar file write error (5301376) 2/10/2011 7:36:57 PM - end writing; write time: 01:41:26 media write error(84) Our Enviroment: All my servers with Windows 2003 SP2 STD 32Bits Some of those clients are Virtuals (VMWare). Master Server HP G5 (Very Good Specs). Policy don't create any checkpoint on any client. Policy have available the option for Allow Multiple Data Stream. Policy are limited to run 2 per policy. Any HELP or Idea? ThanksSolved14KViews0likes14Comments
MIssing PATH: for drives
I ahve a LINUX Media server, and the drive path when i run a tpconfig shows missing. How do I get NB to see the paths once again? Enter option: Id DriveName Type Residence Drive Path Status **************************************************************************** 1 Sep1-71 hcart2 TLD(3) DRIVE=71 MISSING_PATH:4:0:0:2:SG11029122 DOWN 2 Sep1-70 hcart2 TLD(3) DRIVE=70 MISSING_PATH:4:0:0:1:SG11029121 DOWN 3 Sep1-84 hcart2 TLD(3) DRIVE=84 MISSING_PATH:2:0:0:3:SG11029135 UP 4 Sep1-83 hcart2 TLD(3) DRIVE=83 MISSING_PATH:2:0:0:2:SG11029134 UP 5 Sep1-82 hcart2 TLD(3) DRIVE=82 MISSING_PATH:2:0:0:1:SG11029133 DOWN 6 Sep1-69 hcart2 TLD(3) DRIVE=69 MISSING_PATH:4:0:0:0:SG11029120 DOWN 7 Sep1-81 hcart2 TLD(3) DRIVE=81 MISSING_PATH:2:0:0:0:SG11029132 DOWN Currently defined robotics are: TLD(3) robot control host = nbuf1a EMM Server = nbuf1aSolved12KViews1like6Comments
Backup jobs Hängen "In der Warteschlange"
Hallo, habe ein mittelschweres Problem... Egal ob Inventarisierung oder Auswerfen eines Bandes die Jobs bleiben immer mit Auftragsstatus "In der Warteschlange" hängen... habe schon die DB reorganisiert bla... ALLES was das BEutility halt machen kann... jobs gelöscht die noch geplant waren und nochmal versucht... anmeldekonto nochmal das Passwort eingetragen dienste neugestartet, Server neugestartet... Habe auch den Medienserver schon angehalten neugestartet... da bekomme ich ne Meldung: Der server kann icht angehalten werden und beim Starten dass er nicht wiederaufgenommen werden konnte... Habe dann auch das Bandlaufwerk aus BE entfernt und nochmal neu erkennen lassen und treiber nachinstalliert von SYM erst wenn ich die Dienste neustarte kassiere ich ne Fehlermeldung: E0008821 Ansonsten kann ich sagen: Windows 2003 Server 32bit Full Patched Backup Exec 12.5 for Windows Full Patched... Im Oktober bzw. November lief alles absolut einwandfrei... Ich wäre sehr dankbar für tipps!Solved10KViews1like8CommentsMinimum permission to backup a MS-SQL database using NetBackup
Any bad-developed application is avoiding the permission issues using the most intrusive role. In a security strategy, the main goal is to assign the minimum necessary roles for each login. The RDBMS MS-SQL Server allows to maintaing several specific databases in one specific instance, with a correct permission granularity. To maintain this granularity, SQL Server 2005 splited the system admin role in several less intrusive server roles and db roles. Now, a backup operator is able to backup a database without accessing to the data of this database. The db_backupoperator database role is only necessary. The list of the databases is available through the public permission in the master..sysdatabases system table. In the document "Veritas NetBackup™ for Microsoft SQL Server Administrator’s Guide", the permission issue is evasive : "When the NetBackup scheduler is used, backup operations are launched from a daemon process called the NetBackup Client Service. You must ensure that the Client Service has SQL Server privileges to perform backup and restore operations. If you are using integrated security, then you must ensure that the NetBackup Client Service specifies a Windows account that has been granted SQL Server administrative privileges." In the technote http://www.symantec.com/docs/TECH43512, you're specifying "Any logon that requires permissions to perform backup or restore operations should be provided membership in the following SQL Server roles: Server Role : sysadmin DB role : db_backupoperator, dbo_owner Permissions required for performing restore - Server role : sysadmin, dbcreator DB role : db_owner" My question : do you really understand something about the MS-SQL permission ? Why do you need the sysadmin permission ? If it's really necessary, why do you need the dbcreator (included in the sysadmin) ? Why the db_backupoperator and the db_owner ? In fact, only the db role db_backupoperator is necessary, in a MS-SQL point of view. We experimented some hard failure on production applying the sysadmin permission in the Netbackup Logins (client VaultAdmin) : a modification in the sysusers tables is done, replacing the db_owner database role with and changing the db owner to an non-existent dbo user (technically, the dbo'sysusers.sid was replace on each database from 0x01 to the vaultadmin'sid.) Did you plan to implement a correct security in a future version of your product ? Did you already provide a patch for this issue ? Thanks in advance for your answer. Fadace9KViews1like6Comments
Backups failing - "Ready; No idle devices are available"
All of a sudden, Backup Exec 2012 is not running most of my jobs. The job status stays at "Ready; No idle devices are available" It ran 2 of the backups but I'm not sure why it didn't run the others. I have 2 drives, but it would only use one at a time. Both initially have a status of 'Online.' When I was able to get one of my backup jobs running, it would load into one drive, that status would change to 'Active.' Then, if I try to run another job, the other drive will change to 'Active' for a moment, then go back to 'Online' and the job status goes to "Ready; No idle devices are available" These are the things I've tried: Shutting down and restarting the server and the backup device Restarting the Backup Exec services Pausing and unpausing the backup drives What else can I try?8.6KViews1like6Comments
Job fails each time - Error e000fe30 - A communications failure has occurred
Hello, I get the following link when I try to run a backup job that has never run successfully: V-79-57344-65072. I have an agent running on one server running WS 2008 r2, and the BE server is running Windows 2012. The storage unit is a NAS. The BE server is also a file server and it runs like clockwork to the same NAS with no failures. However, the agent running on another server (it's a fax server) has never successfully backed up even a single bit of data; it errors out each time. I've ensured that the agent has local admin access to both the BE server and the local server where it's running, and the NAS allows the same user read/write access (it's actually open to anyone). The server running the BE agent can open and write to the NAS's file share. It can telnet on port 10000 to the BE server and vice-versa. What else can I cover? I tried disabling IPv6 but it still fails each time.Solved8.6KViews1like10CommentsHow to Add a Tape Drive
I have an older system running Windows Server 2003 Enterprise and Symantec Backup Exec 10d. The internal tape drive (Dell DLT-VS160) has gone bad. I have connected an external tape drive (Dell PowerVault 110T) to the SCSI connection on the back of the server. However, Backup Exec does not yet "see" this new tape drive. Wht must I do so that the system and Backup Exec see this tape drive and so that Backup Exec can use it? Thanks for the help.Solved8.1KViews1like7Comments
Backups failing - "Ready; No idle devices are available"
All of a sudden, Backup Exec 2012 is not running most of my jobs. The job status stays at "Ready; No idle devices are available" It ran 2 of the backups but I'm not sure why it didn't run the others. I have 2 drives, but it would only use one at a time. Both initially have a status of 'Online.' When I was able to get one of my backup jobs running, it would load into one drive, that status would change to 'Active.' Then, if I try to run another job, the other drive will change to 'Active' for a moment, then go back to 'Online' and the job status goes to "Ready; No idle devices are available" These are the things I've tried: Shutting down and restarting the server and the backup device Restarting the Backup Exec services Pausing and unpausing the backup drives What else can I try?