Upgrading Netbackup hardware. We have money to spend - any advice?
Hi to all, We currently have 1 x NB 6.5.4 (Win2003) Master Server with a SCSI attached Dell TLD containing 6 x LTO3 tape drives. Additionally we have 1 further media server (Win2003) which we use for disk backups (occasionally as it is extremely slow!). We also have 1 x NOM (Win2003) server and 1 x NB PureDisk 6.5.1.2 (PDOS) server which has 2TB of local disk space. We have noticed that since we introduced multiple copy backups and all 6 Tape devices are in use, the NB platform slows to a halt. We are going to try and spread the load around a bit more. Our thinking is that we buy a media server for each of the 3 LAN's that have servers that we backup (SQL DB and File/Folder backups mainly). Each of these new media servers would either have a lot of local disk storage or would use DAS hardware. We are keen to get more out of our PureDisk software and are considering beefing that up and making it a clustered environment to an offsite device. Quite simply, I have been asked to provide a design document and I wanted to ask if anyone had any reccomendations on how they think we should invest? Our largest backups are around 2TB and these happen on a weekly basis. We also send tapes offsite on a weekly basis for the critical backups so we are not keen on disk-only solutions. We are happy to upgrade to NB7.0 too if this has any relevance with regards to our forthcoming hardware purchase. Any advice greatly appreciated..... Martin859Views0likes5CommentsNetbackup 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.142Views0likes4CommentsCompactation taking too long?
Hello! We have a 30T MSDP with 70% used, we expire a lot of images recently but the storage wouldn't go down, so the next logical step was to run de compactation via CRCONTROL, but it's taking too long? I started the proccess 2 days ago and it's still compacting, but the storage don't seems to respond to this. What am I doing wrong? the logs seems fine (I think...) July 20 11:14:46 INFO [000000078C403640]: COMPACT: instance 0: release space 11837480 from container 4879606 July 20 11:14:59 INFO [000000078C403640]: COMPACT: instance 0: release space 13771159 from container 4879607 July 20 11:15:07 INFO [000000078C403640]: COMPACT: instance 0: release space 7164343 from container 4879609 July 20 11:15:23 INFO [000000078C403640]: COMPACT: instance 0: release space 4810206 from container 4879611 July 20 11:15:23 INFO [000000078C403640]: COMPACT: instance 0: release space 0 from container 4879612 July 20 11:15:23 INFO [000000078C403640]: COMPACT: instance 0: release space 0 from container 4879614 Please send help.Solved841Views0likes2CommentsNetbackup Deduplication Licensing
Hi guys, This is my first post talking about Netbackup Solution. I'm plannig a NBU7 Deduplication but I don't know the differences about this option. 1 - SYMC NETBACKUP DEDUPLICATION OPTION 2 - SYMC NETBACKUP PLATFORM DEDUPLICATION OPTION ADD-ON I need know understand this information to get the correct SKUs. Who can help me? Tks a lot.Solved2.2KViews0likes9CommentsReplacing 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 you1.5KViews0likes7CommentsBackup 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.LOG4.6KViews0likes7CommentsIgnoring 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 time1.3KViews0likes5CommentsNetBackup API call format works in Unix but not Windows
I am running NetBackup 8.2 on a Solaris master. I am writing a script to run on my existing Windows clients for when the server needs to be reinstalled and it needs to have a re-issue token to allow automated installation of the NetBackup software. I have a working version of the script for Linux but I am having an issue converting it to run as a PowerShell script. I have been able to convert all the other API calls but not the POST /security/securitytokens to create the new token. If I use the autogenerate API GUI when connecting to https://MASTER/api-docs/index.html in the security section it will only produce a Unix curl version. I even created a test Windows master server and it also only generates a Unix curl formatted output. I have checked the github site but I could not find a PowerShell example of this API command The generated code obtained is as follows: curl -X POST "https://MASTER/netbackup/security/securitytokens" -H "accept: application/vnd.netbackup+json;version=3.0" -H "Authorization: ABCDEFGHIJKLMNOPQRSTUVWXYZ" -H "Content-Type: application/vnd.netbackup+json;version=3.0" -d "{ \"tokenName\": \"test1\", \"hostId\": \"testid\", \"reason\": \"Re-Issue\", \"allowedCount\": 1, \"validFor\": 3600, \"type\": 1}" I had to change curl to curl.exe to use the true curl program not the alias to Invoke-WebRequest (which format is completely different) and add the -k option. This will produce the following error: {"errorCode":9926,"errorMessage":"Input JSON is invalid","attributeErrors":{},"fileUploadErrors":[],"errorDetails":[]} I have tried replacing the \" with ^" and also ' instead of \" but still get the JSON invalid message. Is there an option or any way to generate the output for Windows PowerShell? Any help will be greatly appreciated. Thank you.Solved2.4KViews0likes4CommentsDFSR backup failing
10 May, 2020 7:19:40 PM - begin writing 10 May, 2020 7:19:46 PM - Error bpbrm (pid=17654) from client client1230020: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1 10 May, 2020 7:19:46 PM - Info bptm (pid=17662) waited for full buffer 1 times, delayed 448 times 10 May, 2020 7:19:46 PM - Error bpbrm (pid=17654) from client client1230020: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification 10 May, 2020 7:19:46 PM - Info bptm (pid=17662) EXITING with status 90 <---------- 10 May, 2020 7:19:46 PM - Critical bpbrm (pid=17654) unexpected termination of client client1230020 10 May, 2020 7:19:47 PM - Info server0717a0.Site.domain.com (pid=17662) StorageServer=PureDisk:server0717a0.Site.domain.com; Report=PDDO Stats for (server0717a0.Site.domain.com): scanned: 3 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled 10 May, 2020 7:19:47 PM - Info bpbkar (pid=76600) done. status: 50: client process aborted 10 May, 2020 7:19:47 PM - end writing; write time: 0:00:07 client process aborted (50) C:\Users\ad_acharbha>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {5f357fd4-da83-4845-9d62-b4f906ec7caa} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {0bdee2ca-1f4a-49a0-8e18-49ae165c47c9} State: [1] Stable Last error: No error Writer name: 'DFS Replication service writer' Writer Id: {2707761b-2324-473d-88eb-eb007a359533} Writer Instance Id: {c3c0ec55-b351-4cb5-99ab-454b16e7fb03} State: [1] Stable Last error: No error Writer name: 'FSRM Writer' Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674} Writer Instance Id: {0ea27a80-1f79-41e5-84f1-81c3701f4856} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {ee7b977c-7f32-4141-94a5-1e75ddcd4141} State: [1] Stable Last error: No error Writer name: 'Dedup Writer' Writer Id: {41db4dbf-6046-470e-8ad5-d5081dfb1b70} Writer Instance Id: {372d7eb3-6fe4-41c1-90c9-719b4e8e0393} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {79d807c1-5184-4748-9594-c77fd3f03dcf} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {89abaa05-9cb6-4893-a709-a0766f588b99} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {238d1fa2-ba97-471c-9e2d-9c30977d541b} State: [1] Stable Last error: No error Writer name: 'Cluster Database' Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e} Writer Instance Id: {80577a73-5362-4ec7-b328-c1af2c833499} State: [1] Stable Last error: No error Writer name: 'Cluster Shared Volume VSS Writer' Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570} Writer Instance Id: {9f012b43-258e-4353-8bc3-2b28609c9fce} State: [1] Stable Last error: No error C:\Users\ad_acharbha> C:\Users\ad_acharbha>vssadmin list providers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 Microsoft Corp. Provider name: 'Microsoft CSV Shadow Copy Helper Provider' Provider type: Software Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d} Version: 1.0.0.1 Provider name: 'Microsoft CSV Shadow Copy Provider' Provider type: Software Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff} Version: 1.0.0.1 Provider name: 'Microsoft File Share Shadow Copy provider' Provider type: Fileshare Provider Id: {89300202-3cec-4981-9171-19f59559e0f2} Version: 1.0.0.1 Provider name: 'Microsoft Software Shadow Copy provider 1.0' Provider type: System Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5} Version: 1.0.0.7 C:\Users\ad_acharbha>1.3KViews0likes4Commentsfull backup failed with error code 26
Hi all Thanks in advance for reading this post. any tips\ideas\advices are highly appreciated environment setting - NBU 7.7.2 on Windows 2012 R2 - 1x master server which also act as media server - all clients are VMware, communicated via Virtual Center, snapshot backup using LAN @ NBD - all backups goes to disk - daily @ incremental backup from Monday to Friday - weekly\monthly\yearly @ full on Saturday - no scheduled backup on Sunday issue - no issue with daily backup - 50% of full backup will failed with EXIT STATUS 26 (client/server handshaking failed) - restart of the jobs in stages will eventually completed based on reading, error 26 related to network or communication error. when the issue occured, i would test the network (bpclntcmd) and it turned out ok. later on, restart of the jobs also turn out ok. if too many failure, i have to restart it in stages, else it will resulted the same; error code 26. it suggest congestion of bottleneck somewhere but i have no clear path to look to in worst case, jobs will stuck & bpup/bpdown has to be done. a case logged to Symantec & he suspected issue with network sockets which to me not very clear or have a good understanding on it. hopefully good folks out there can help me with it. Symantec advice to clear the network socket connections which i have to request from NW team to do it but no logs/eviden shared it was done. totally dependent on NW team. And reboot the server which i confirmed rebooted based on server uptime. And still the issue keep on occuring and ruined my lovely weekend. Thanks again in advance for reading this post. any tips\ideas\advices are highly appreciated3.4KViews0likes12Comments