Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people, just like you, are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
Solved

Netbackup Restore Partially Successfull

Posted on 2013-06-12
5
1,278 Views
Last Modified: 2013-06-30
Hi Experts


I have done a big restore and it partially successfully completed.
when I checked the progress log file, I found below .
/usr/openv/netbackup/logs/user_ops/<userid>/logs/

I want to understand how many files I have missed in real or how many files were not restored.

I am confused about below output.

Note: All below TAR output has been gathered from one restore job


TAR EXITING WITH STATUS = 0
21:55:09 (9630975.001) INF - TAR RESTORED 86937 OF 86937 FILES SUCCESSFULLY
21:55:09 (9630975.001) INF - TAR KEPT 0 EXISTING FILES
21:55:09 (9630975.001) INF - TAR PARTIALLY RESTORED 0 FILES




21:59:23 (9630975.002) INF - TAR EXITING WITH STATUS = 0
21:59:23 (9630975.002) INF - TAR RESTORED 521 OF 521 FILES SUCCESSFULLY
21:59:23 (9630975.002) INF - TAR KEPT 0 EXISTING FILES
21:59:23 (9630975.002) INF - TAR PARTIALLY RESTORED 0 FILES



22:01:34 (9630975.003) INF - TAR EXITING WITH STATUS = 0
22:01:34 (9630975.003) INF - TAR RESTORED 773 OF 773 FILES SUCCESSFULLY  
22:01:34 (9630975.003) INF - TAR KEPT 0 EXISTING FILES
22:01:34 (9630975.003) INF - TAR PARTIALLY RESTORED 0 FILES


22:05:33 (9630975.004) INF - TAR EXITING WITH STATUS = 0
22:05:33 (9630975.004) INF - TAR RESTORED 514 OF 514 FILES SUCCESSFULLY  
22:05:33 (9630975.004) INF - TAR KEPT 0 EXISTING FILES
22:05:33 (9630975.004) INF - TAR PARTIALLY RESTORED 0 FILES



22:18:10 (9630975.005) INF - TAR EXITING WITH STATUS = 0
22:18:10 (9630975.005) INF - TAR RESTORED 2520 OF 2520 FILES SUCCESSFULLY  
22:18:10 (9630975.005) INF - TAR KEPT 0 EXISTING FILES
22:18:10 (9630975.005) INF - TAR PARTIALLY RESTORED 0 FILES


22:22:16 (9630975.006) INF - TAR EXITING WITH STATUS = 0
22:22:16 (9630975.006) INF - TAR RESTORED 479 OF 479 FILES SUCCESSFULLY    
22:22:16 (9630975.006) INF - TAR KEPT 0 EXISTING FILES
22:22:16 (9630975.006) INF - TAR PARTIALLY RESTORED 0 FILES


22:26:49 (9630975.007) INF - TAR EXITING WITH STATUS = 0
22:26:49 (9630975.007) INF - TAR RESTORED 239 OF 242 FILES SUCCESSFULLY  
22:26:49 (9630975.007) INF - TAR KEPT 3 EXISTING FILES
22:26:49 (9630975.007) INF - TAR PARTIALLY RESTORED 0 FILES


22:31:39 (9630975.009) INF - TAR EXITING WITH STATUS = 0
22:31:39 (9630975.009) INF - TAR RESTORED 506 OF 506 FILES SUCCESSFULLY  
22:31:39 (9630975.009) INF - TAR KEPT 0 EXISTING FILES
22:31:39 (9630975.009) INF - TAR PARTIALLY RESTORED 0 FILES



23:09:38 (9630975.010) INF - TAR RESTORED 265 OF 265 FILES SUCCESSFULLY  
23:09:38 (9630975.010) INF - TAR KEPT 0 EXISTING FILES
23:09:38 (9630975.010) INF - TAR PARTIALLY RESTORED 0 FILES
23:09:38 (9630975.010) INF - TAR PARTIALLY RESTORED 0 FILES


23:16:23 (9630975.012) INF - TAR EXITING WITH STATUS = 0
23:16:23 (9630975.012) INF - TAR RESTORED 2062 OF 2109 FILES SUCCESSFULLY  
23:16:23 (9630975.012) INF - TAR KEPT 47 EXISTING FILES
23:16:23 (9630975.012) INF - TAR PARTIALLY RESTORED 0 FILES


23:31:40 (9630975.013) INF - TAR RESTORED 0 OF 2229 FILES SUCCESSFULLY    
23:31:40 (9630975.013) INF - TAR KEPT 2229 EXISTING FILES
23:31:40 (9630975.013) INF - TAR PARTIALLY RESTORED 0 FILES



23:35:24 (9630975.014) INF - TAR EXITING WITH STATUS = 0
23:35:24 (9630975.014) INF - TAR RESTORED 0 OF 851 FILES SUCCESSFULLY  
23:35:24 (9630975.014) INF - TAR KEPT 851 EXISTING FILES
23:35:24 (9630975.014) INF - TAR PARTIALLY RESTORED 0 FILES


23:35:54 (9630975.011) INF - TAR RESTORED 0 OF 60024 FILES SUCCESSFULLY
23:35:54 (9630975.011) INF - TAR KEPT 60024 EXISTING FILES
23:35:54 (9630975.011) INF - TAR PARTIALLY RESTORED 0 FILES



23:38:05 (9630975.015) INF - TAR RESTORED 0 OF 4073 FILES SUCCESSFULLY  
23:38:05 (9630975.015) INF - TAR KEPT 4073 EXISTING FILES
23:38:05 (9630975.015) INF - TAR PARTIALLY RESTORED 0 FILES


23:59:22 (9630975.016) INF - TAR RESTORED 34713 OF 44196 FILES SUCCESSFULLY  
23:59:22 (9630975.016) INF - TAR KEPT 9483 EXISTING FILES
23:59:22 (9630975.016) INF - TAR PARTIALLY RESTORED 0 FILES
0
Comment
Question by:MSGK161091
  • 3
  • 2
5 Comments
 
LVL 62

Accepted Solution

by:
gheist earned 500 total points
ID: 39242811
There is no error in restore. 0 files missed during incremental restore of full backup sets.
0
 
LVL 1

Author Comment

by:MSGK161091
ID: 39242821
Ok thanks. but when it says

TAR RESTORED 34713 OF 44196 FILES SUCCESSFULLY  
TAR KEPT 9483 EXISTING FILES

 and likewise in other logs

what that means in real.

Are those 9483 files were already available at destination?

Just trying to understand in detail.
0
 
LVL 62

Expert Comment

by:gheist
ID: 39243071
just that file on the disk was same as you tried to restore...
0
 
LVL 1

Author Comment

by:MSGK161091
ID: 39243092
Can you please clarify more on your above reply
0
 
LVL 62

Expert Comment

by:gheist
ID: 39243535
It is described in deep detail in "man vxlogview" on your system
man -k vx will show you more documentation
0

Featured Post

NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

VM backup deduplication is a method of reducing the amount of storage space needed to save VM backups. In most organizations, VMs contain many duplicate copies of data, such as VMs deployed from the same template, VMs with the same OS, or VMs that h…
Finding original email is quite difficult due to their duplicates. From this article, you will come to know why multiple duplicates of same emails appear and how to delete duplicate emails from Outlook securely and instantly while vital emails remai…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
In a previous video, we went over how to export a DynamoDB table into Amazon S3.  In this video, we show how to load the export from S3 into a DynamoDB table.

860 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question