Netbackup Installation failing Error - ERROR: NetBackup Database Creation Failed!
Netbackup Installation failing Error - ERROR: NetBackup Database Creation Failed! Version: NetBackup_10.3.0.1_Win 06:49:43.985 [4552.4492] <4> NBDBsystem: Command exited with status: 0 06:49:43.985 [4552.4492] <4> create_nbdb_tablespace_directory: The NetBackup database tablespace directory creation complete [C:\Program Files\Veritas\NetBackupDB\data\nbdb]. 06:49:43.985 [4552.4492] <16> DbConnection::Execute: (6848.3) Execute error: SQL - native=<1> sqlerror=<ERROR: directory "C:/Program Files/Veritas/NetBackupDB/data/nbdb/PG_14_202107181" already in use as a tablespace; Error while executing the query> sqlstate=<55006> retval=<2007143> nbdberror=<DB_ERROR_SQLUnknown(2007143)> 06:49:43.985 [4552.4492] <2> DbConnection::Execute: (6848.3) stmt=<CREATE TABLESPACE NBDB OWNER postgres LOCATION 'C:\Program Files\Veritas\NetBackupDB\data\nbdb'> 06:49:43.985 [4552.4492] <16> create_postgres_nbdb_tbspaces: Unable to execute sql statement "CREATE TABLESPACE NBDB OWNER postgres LOCATION 'C:\Program Files\Veritas\NetBackupDB\data\nbdb'", error 2007143 06:49:43.985 [4552.4492] <4> CreatePostgresDatabase: Exiting with rc = 29 06:49:43.985 [4552.4492] <16> create_pgnbdb: Failed to created PostgreSQL NBDB database.
Where install VIOM: on Windows? or on Linux?
Hi every one: I want to install VIOM, I never do it before, and my first question is: Where I should do it? In Windows envioroment? or in Linux Envioroment? All my clusters are in Linux Envioroment: Infoscale 8.0 on Red Hat 8.9. Other question: Is it posible install Cordination Point Service in the same server? All my clusters have 2 nodos: node one in one CPD (site 1) and the node two in other CPD (site 2). I think that the new server (VIOM+CP) shultd be another CPD (site 3). Correct? Thanks Jaime.
Backing up Active Directory: V-79-57344-33928 - (AD LDS) database was not found.
Hello, We have this error from time to time, but it usually fixes itself without any end user intervention. However I am getting this error three nights in a row now on one of our domain controllers. This started happening on Wed morning, and continued through Friday morning. In all three instances the error message in the log is: Job ended: Thursday, October 29, 2009 at 1:18:54 AM Completed status: Failed Final error: 0xe0008488 - Access is denied. Final error category: Security Errors For additional information regarding this error refer to link V-79-57344-33928 Errors Click an error below to locate it in the job log Backup- \\dc1.domain.com\System?State V-79-57344-33928 - Unable to complete the operation for the selected resource using the specified options. The Active Directory, Active Directory Application Mode (ADAM) or Active Directory Lightweight Directory Services (AD LDS) database was not found. So I checked the selections and under the server in question, I can see System State > Active Directory > C:_WINDOWS_NTDS, and this is all checked off. I did a test Resource Credentials for everything in this backup and it all returnedsuccessfulso I'm at a loss. Under Settings > Microsoft Active Directory for this job properties we have all three boxes checked (GRC, Consistency Check, Continue if Consistency check fails.) Backup method is greyed out, but says Full - Back up entire Active Directory. We are using Symantec Backup Exec 12.5 for Windows Servers Media Server Version 12.5 Rev 2213 Administration Console 12.5 Rev 2213 Desktop and Laptop Option: Version 3.1 Rev. 3.41.32a Installed updates: Service Pack 2 Hotfixes: 324947 317436 325647 319242 324012 326004 323894 324011 Thanks for the help, we really do appreciate it!
Replacing Windows Media Servers with Linux Media Servers
Good Afternoon. I have a customer planning to replace his existing Windows Media Servers with new RHEL servers, and I'm wondering if that will cause issues when trying to use the new Media Server to restore older images. We suggested they keep the windows media servers around for restores, but they are not amenable to that. Is there a way that I can re-assign all primary image ownership from 1 Media Server to another? They are on Netbackup v8 right now but will be upgrading to v9 as a first step. Thank you
Backup failed with error code 71 (EXIT STATUS 71: none of the files in the file list exist). The server rebooted automatically on 28th march and after that the backups are failing.
Problem description : Backup failed with error code 71 (EXIT STATUS 71: none of the files in the file list exist). The server rebooted automatically on 28 th march and after that the backups are failing. The network drives are Netapp storage Shares and it is mapped to the client COLLECTIONSRV. The drives are accessible from OS using the user “USER1”. The netbackup client service is having the logon credentials of user “USER1”. In the policy the “ Backup Network drive” option is selected. The path is also specified properly. Also tried with the mapped drive letter “Y:\”. But the backups are failing with the same error code. The server has been rebooted manually but still the same issue. BPBRM: 03:02:59.482 [3339] <4> bpbrm handle_backup: from client COLLECTIONSRV: TRV - object not found for file system backup: \\10.10.5.138\evsqlbkp\SQLFULL\ BPBKAR: 10:58:04.857 AM: [1136.2856] <2> tar_backup::V_SetupProcessContinue: TAR - CONTINUE BACKUP received 10:58:05.107 AM: [1136.2856] <2> tar_backup::V_SetupFileDirectives: TAR - backup filename = \\10.10.5.138\evsqlbkp\SQLFULL\ 10:58:05.107 AM: [1136.5844] <4> tar_base::V_KeepaliveThread: INF - The Keepalive thread is active. Keepalive interval 60 Seconds 10 …. 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - ================================================================================ 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking estimate: start 10:58:07.794 AM: [1136.2856] <2> tar_base::V_vTarMsgW: TRV - object not found for file system backup: \\10.10.5.138\evsqlbkp\SQLFULL\ 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking estimate: stop 10:58:07.794 AM: [1136.2856] <4> tar_backup::V_DetermineEstimate: INF - job tracking time: 0 secs 10:58:07.841 AM: [1136.5844] <4> tar_base::V_KeepaliveThread: INF - Keepalive Thread Terminating. Mutex:WAIT_OBJECT_0 10:58:07.841 AM: [1136.2856] <4> tar_base::V_StopKeepaliveThread: INF - The Keepalive Thread has Exited. Wait Reason:WAIT_OBJECT_0 10:58:07.841 AM: [1136.2856] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 71: none of the files in the file list exist 10:58:07.841 AM: [1136.2856] <4> tar_backup::backup_done_state: INF - ================================================================================ 10:58:09.856 AM: [1136.2856] <16> dtcp_read: TCP - failure: recv socket (460) (TCP 10053: Software caused connection abort) 10:58:09.856 AM: [1136.2856] <4> OVShutdown: INF - Finished process 10:58:09.872 AM: [1136.2856] <4> WinMain: INF - Exiting C:\Program Files\VERITAS\NetBackup\bin\bpbkar32.exe 10:58:11.872 AM: [1136.2856] <4> ov_log::OVClose: INF - Closing log file: C:\Program Files\VERITAS\NetBackup\logs\BPBKAR\040312.LOG
Ignoring Stub Files
Can we filter our Backup Policy based on file size. Regardless of whether or not it is a stub file. Can we backup files ONLY greater than 8k? or by file creation date. Currently we have a process that we purchased (Rainfinity from EMC) that takes images once a month and stores the image on lower cost file system and leaves a stub file that is 8k in size. When I run a full backup the policy sees the 8k and backs up the file. Which is great but the stub file is 8k the actual file is larger and has to be retrieve from the lower cost disk which is very slow so my 1TB area takes days to backup to tape because of the slow retrieval speed. Yes EMC can replicate the data to another area but because of the cost this is not an option at this time
