How to copy backup images from one media to different
Today we will discuss in this blog how can we copy backup images from one media to different. Suppose we have had backup image of some data on a SAN drive and we want it to have at different SAN drive DSU/volume pool. In this blog we imagine that we have backup image on DSU1 and we will make a copy of this backup image in to DSU2.How Netbackup takes flat files backup which constantly open
Today i will discuss the problem happened with my flat files which contineously open and i had to take the backup but the backup was not being able to completed successfully. i always found it completed partially. in my scenerio i have Veritas Netbackup 6.5 with MS windows2003. Go to the exact location as shown in the below figure of Veritas Netbackup ServerNetwork Connection Timed Out(41)
Today we discuss in this BLOG "Network Connection Timed Out(41)" in the Activity Monitor of Veritas Netbackup Server with the restore failed to recover the requested files(5) In our case we have a environment of : Windows2003 server Veritas Netbackup 6.5. MS SQL Server 2005
Windows 7 Support Information on Symantec.com
We've had numerous questions regarding Windows 7 and which Symantec products will support the new OS and when. In effort not to duplicate information and keep updates as current as possible we are providing this link to the Symantec.com site: http://www.symantec.com/business/theme.jsp?themeid=windows7
Symantec Survey Reveals SMB Disaster Preparedness Perception and Reality At Odds
While no one wants a disaster to occur, the reality is that they happen. What if your business was hit with a disaster – a virus, hacker attack, power outage or even a fire? Are you prepared with a recovery plan to revive critical customer, financial and business information?
network read failed (42)
hi i am facing some problem in veritas netbackup 6.5.2 i have 3 servers which are configured as media server. now one server with windows platform is not getting backed up from past 2 days and giving error code 42 network read failed i checked network settings and host files ping test from host to server and vice versa.Netbackup activity monitor show backup successful but client shows partially successful?????
My Environment OS # Windows2003 Server Netbackup Version # VERITAS Netbackup 6.5 Client # MS SQL Server 2005 Activity Monitor Details 8/17/2009 6:00:26 AM - begin Restore 8/17/2009 6:00:33 AM - restoring image server-sec_1250391155 8/17/2009 6:00:33 AM - requesting resource Fibre Transport 8/17/2009 6:00:33 AM - Warning nbjm(pid=2496) NBU status: 800, EMM status: Fibre Transport resources are not available 8/17/2009 6:00:33 AM - Warning nbjm(pid=2496) NBU status: 800, EMM status: Fibre Transport resources are not available 8/17/2009 6:00:46 AM - connected 8/17/2009 6:00:46 AM - started process bptm (6128) 8/17/2009 6:00:46 AM - started process bptm (3604) 8/17/2009 6:00:48 AM - begin reading 8/17/2009 6:01:00 AM - restored image server-sec_1250391155 - (the requested operation was successfully completed(0)); restore time 00:00:27 8/17/2009 6:01:03 AM - end Restore; elapsed time: 00:00:37 the requested operation was successfully completed(0) View Status Restore started Mon Aug 17 05:14:30 2009 INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]10 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]20 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]30 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]40 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]50 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]60 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]70 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]80 percent processed.>. INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Native Client][SQL Server]90 percent processed.>. INF - Thread has been closed for stripe #0 INF - OPERATION #1 of batch C:\Documents and Settings\abc.xyz\Desktop\Restoration150809.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 2754(2702) seconds INF - RESTORE STARTED USING Microsoft SQL Server 2005 - 9.00.3200.00 (X64) Oct 2 2007 12:23:02 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2) Batch = C:\Documents and Settings\abc.xyz\Desktop\Restoration150809.bch, Op# = 2. INF - Using backup image server-sec.MSSQL7.SQL-CLUSTER.inc.Dotnet111.~.7.001of001.20090816075227..C INF - restore database "Dotnet111" from VIRTUAL_DEVICE='VNBU0-8904-7564-1250470822' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery INF - Number of stripes: 1, Number of buffers per stripe 2. INF - Created VDI object for SQL Server instance <DOTNET-SERVER>. Connection timeout is <300> seconds. DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3013><[Microsoft][SQL Native Client][SQL Server]RESTORE DATABASE is terminating abnormally.>. DBMS MSG - SQL Message <0><[Microsoft][SQL Native Client]Unspecified error occurred on SQL Server. Connection may have been terminated by the server.> ERR - Error found executing <restore database "Dotnet111" from VIRTUAL_DEVICE='VNBU0-8904-7564-1250470822' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, replace , norecovery>. ERR - Error in VDS->Close: 0x80770004. CONTINUATION: - An abort request is preventing anything except termination actions. INF - OPERATION #2 of batch C:\Documents and Settings\abc.xyz\Desktop\Restoration150809.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 43(43) seconds. INF - Results of executing <C:\Documents and Settings\abc.xyz\Desktop\Restoration150809.bch>: <1> operations succeeded. <1> operations failed. INF - Thread has been closed for stripe #0 Work Around When restoring a Microsoft SQL server database using the VERITAS NetBackup (tm) SQL Server agent, the restore finishes successfully, but the recovery of the database fails, and the database appears as "Suspect" in the SQL Enterprise Manager. 1.) MS SQL Server .LDF file must/might be grown enough, should compact the .LDF file of MS SQL Server. 2.) if the problem comes in MS SQL 2000 Server, read the below suggested document http://support.microsoft.com/kb/891585/ http://support.microsoft.com/kb/916287 Some Thing Important in the end of View Status Details you can find something like below <1> operations succeeded. <1> operations failed. This means that operation succeeded 1 and 1got failed, total operations=2 Note:- This might be that the 1operation which got successful is backup restoration and the 1 operation which got failed might be that the MS SQL got stuck in recovering/(replaying logs) database <2> operations succeeded. <0> operations failed. This means that operation succeeded 2 and 0/nothing got failed, total operations=2 Note:- This means that the backup restore successful
Recovery Point Objective – How much data can you afford to lose?
Nowadays, probably not so much. There was a time where a day or two of outage didn’t make a huge difference to businesses - unfortunately that was over 20 years ago. We now live in a “NOW” world where every second counts. Somehow, no matter what your size, you have to consider how to ensure that business-critical data is always protected and always available.
