netbackup 7.7.2

4 Topics

AD GRT - vmware snapshot
Hi, this must be a subject discussed countless of times- regardless I havn't quite found the answers I was looking for. I am trying to figure out if I can and should backup Active Directory using vmware snapshots, and if it is possible to use GRT with snapshots. this article firmly states against it: http://techgenix.com/dont-snapshot-domain-controllers-96/ however this old thread I found: https://vox.veritas.com/t5/Backup-Exec/Backing-up-AD-in-a-VMWare-VM-Using-GRT-Causes-Job-Warnings-Safe/td-p/529685 suggests it's fine to use snapshots to backup AD. moreover it suggest that with"active directory agent license installed on the media server" I will be able to use GRT. so I am left with two main questions: 1) can and should I backup AD with vmware snapshots? 2) what is this "active directory agent license installed on the media server"- does RahulG mean a regular netbackup client installed on the DC or is it an actual agent on the media server capable of expanding the snapshot to restore single users or etc.? thanks in advanced for the help
Solved
gkman
6 years ago Place NetBackup
3.8KViews
0likes
7Comments
NetBackup 7.7.2 client for RedHat 7/7.5
We have NetBackup 7.7.2 installed, i downloaded Linux client package for NetBackup 7.7.2 from support site, but it has NetBackup 7.7.2 client for Linux RedHat 6, from where i can download NetBackup 7.7.2 client for Redhat 7 or 7.5? Note:NetBackup 7.7.2 client for Linux RedHat 2.6.18 worked for Redhat 7 servers but i am looking for NetBackup client specific to Redhat 7.
Solved
sushilyadav088
7 years ago Place NetBackup
2.4KViews
0likes
4Comments
Import Images from a DiskPool
Hi, Greetings. I am new to VOX. The reason I have come to you as I need some help regarding importing data(backup images) from "MSDP(Windows) in old backup domain" to "MSDP(NBU Appliance) in new backup domain". Here is the plan I have.. 1. In New Domain, create Storage Server with the same naming convention as used in Old Domain 2. From Admin Console, open up the Storage Server properties within the Credentials section. Input the path to the MSDP pool, ex: M:\Msdp. Also input the Spalogin and Spapassword. Next create a diskpool with the same name as the original using the NetBackup Disk Pool Wizard 3. Then Initiate Import(Phase1 import) on this DiskPool 4. From Catalog, initiate Phase2 import What is your suggestion? Thanks, Ezra.
EKR
8 years ago Place NetBackup
1.9KViews
0likes
2Comments
sql backups are partially successful
Hi to all. I have an sql backup that partially succeeds (ends with status 1) . in the details of the job I can see a list of all the failed databases: 07/27/2016 12:19:21 - Info dbclient (pid=3868) INF - The following object(s) were not backed up successfully. 07/27/2016 12:19:21 - Info dbclient (pid=3868) INF - master 07/27/2016 12:19:21 - Info dbclient (pid=3868) INF - msdb 07/27/2016 12:19:21 - Info dbclient (pid=3868) INF - Profile_DB 07/27/2016 12:19:21 - Info dbclient (pid=3868) INF - Search_Service_Application_Hadassah_AnalyticsReportingStoreDB_d50fa820052f4ff58334c0d040c05852 07/27/2016 12:19:21 - Info dbclient (pid=3868) INF - Search_Service_Application_Hadassah_CrawlStoreDB_37844f58039d4b858632d9ef2ff5d471 07/27/2016 12:19:21 - Info dbclient (pid=3868) INF - Search_Service_Application_Hadassah_DB_9b4682c331a14d469030bcc49c13872f 07/27/2016 12:19:22 - Info dbclient (pid=3868) INF - Search_Service_Application_Hadassah_LinksStoreDB_12cf8a58253a4fac82e74c9347d96efe 07/27/2016 12:19:22 - Info dbclient (pid=3868) INF - Social_DB 07/27/2016 12:19:22 - Info dbclient (pid=3868) INF - Sync_DB 07/27/2016 12:19:22 - Info dbclient (pid=3868) INF - WSS_Logging which makes sense since they are all in simple recovery mode, however the database I am interested in is not listed as a failed database backup. I actually noticed I have afailed backup because the disk was getting full which led me to checkthe sql logs: 07/25/2016 12:06:58,Backup,Unknown,BACKUP failed to complete the command BACKUP LOG Mysite101. Check the backup application log for detailed messages. I checked themssql_backup_failures logs and found the error: INFO The api was waiting and the timeout interval had elapsed. so I increased the VDI timeout and since I have stopped getting any errors regarding the database in themssql_backup_failures logs, but the backup keeps failing. I moved on to check thedbclient logs: 11:39:17.992 [1260.4416] <4> CDBbackrec::ProcessAvailabilityGroupBackup: INF - Database <Mysite101> is not participating in an availability group. 11:39:17.992 [1260.4416] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b4290>. 11:39:17.996 [1260.4416] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b4290> 11:39:17.996 [1260.4416] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b4290>. 11:39:18.000 [1260.4416] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b4290> 11:39:18.000 [1260.4416] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b4290>. 11:39:18.004 [1260.4416] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b4290> 11:39:18.004 [1260.4416] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b4290>. 11:39:18.008 [1260.4416] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b4290> 11:39:18.008 [1260.4416] <4> Dbbackrec::PerformNBOperation: INF - BACKUP STARTED USING Microsoft SQL Server 2014 - 12.0.2000.8 (X64) Feb 20 2014 20:04:26 Copyright (c) Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\transaction.bch, Op# = 5 11:39:18.024 [1260.4416] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:18.024 [1260.4416] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60460 TO 132.64.227.44.1556 fd = 1060 11:39:18.104 [1260.4416] <4> InitPipeInfo: INF - Using backup image SP13-DB.MSSQL7.SP13-DB.trx.Mysite101.~.7.001of001.20160727113916..C 11:39:18.118 [1260.4416] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:18.118 [1260.4416] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60461 TO 132.64.227.44.1556 fd = 1060 11:39:18.210 [1260.4416] <4> Dbbackrec::CreateSQLcmdSyntax: INF - backup log "Mysite101" to VIRTUAL_DEVICE='VNBU0-1260-4416-1469608758' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 11:39:18.214 [1260.4416] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:18.214 [1260.4416] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60462 TO 132.64.227.44.1556 fd = 1208 11:39:18.230 [1260.1848] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:18.230 [1260.1848] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60463 TO 132.64.227.44.1556 fd = 1160 11:39:18.325 [1260.4416] <4> Dbbackrec::CreateSQLcmdSyntax: INF - Number of stripes: 1, Number of buffers per stripe 2. 11:39:18.375 [1260.1848] <4> DBthreads::dbclient: INF - Instance\Database is <MSSQLSERVER\Mysite101> 11:39:18.389 [1260.4416] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:18.389 [1260.4416] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60464 TO 132.64.227.44.1556 fd = 1208 11:39:18.502 [1260.4416] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x00bde640>. 11:39:18.508 [1260.4416] <4> CDBbackrec::InitDeviceSet(): INF - Created VDI object for SQL Server instance <SP13-DB>. Connection timeout is <300> seconds. 11:39:18.513 [1260.4416] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:18.513 [1260.4416] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60465 TO 132.64.227.44.1556 fd = 1276 11:39:18.682 [1260.1848] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:18.682 [1260.1848] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60466 TO 132.64.227.44.1556 fd = 1056 11:39:26.738 [1260.1848] <4> serverResponse: Not a candidate for alternate buffer method: shared memory is not in use. 11:39:33.794 [1260.3644] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b53c0>. 11:39:33.799 [1260.3644] <2> CDBbackcat::GetBackupWaitTimeFromCfg: DBG - Using a backup wait timeout from the BSA environment variable NBBSA_CLIENT_READ_TIMEOUT 11:39:33.799 [1260.3644] <2> CDBbackcat::GetSysBackupTime: DBG - Waiting for SQL Server to update it's backup history for up to 3600 second(s) 11:39:34.815 [1260.3644] <2> CDBbackcat::GetSysBackupTime: DBG - Succeeded in getting the backup timestamps from SQL Server after 1 retry(ies) 11:39:34.815 [1260.3644] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b53c0> 11:39:34.816 [1260.4416] <8> CODBCaccess::LogODBCerr: WARN - ODBC return code <1>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 11.0][SQL Server]100 percent processed.>. 11:39:34.816 [1260.4416] <8> CODBCaccess::LogODBCerr: WARN - SQL Message <4035><[Microsoft][SQL Server Native Client 11.0][SQL Server]Processed 10 pages for database 'Mysite101', file 'Mysite101_log' on file 1.> 11:39:34.816 [1260.4416] <8> CODBCaccess::LogODBCerr: WARN - SQL Message <3014><[Microsoft][SQL Server Native Client 11.0][SQL Server]BACKUP LOG successfully processed 10 pages in 0.006 seconds (11.881 MB/sec).> 11:39:34.816 [1260.1848] <4> DBthreads::dbclient: INF - Thread has been closed for stripe #0 11:39:34.832 [1260.1848] <2> vnet_pbxConnect: pbxConnectEx Succeeded 11:39:34.832 [1260.1848] <2> logconnections: BPRD CONNECT FROM 192.168.6.130.60483 TO 132.64.227.44.1556 fd = 1212 11:39:34.909 [1260.1848] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b4290>. 11:39:34.914 [1260.1848] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b4290> 11:39:34.914 [1260.1848] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b4290>. 11:39:34.919 [1260.1848] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b4290> 11:39:34.919 [1260.1848] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b4290>. 11:39:34.923 [1260.1848] <4> DBConnect: INF - Logging into SQL Server with DSN <NBMSSQL_1260_1956_11>, SQL userid <sa> handle <0x020b5a10>. 11:39:34.929 [1260.1848] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b5a10> 11:39:34.931 [1260.1848] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x020b4290> 11:39:40.047 [1260.4416] <4> DBDisconnect: INF - Logging out of SQL Server with handle <0x00bde640> 11:39:40.047 [1260.4416] <4> Dbbackrec::Perform: INF - OPERATION #5 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\transaction.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 24(1) seconds I can't figure out what the problem is and was hoping for help. my client, master and media servers are all version 7.7.2
gkman
9 years ago Place NetBackup
1.3KViews
0likes
2Comments