Partial Backup of Solaris 11

[H_Sharma]

Hello Experts,

We are experiencing issue with partial backups of 4 solaris 11 clients. Pls help.

9/18/2014 1:08:12 AM - awaiting resource T Reason: Drives are in use, Media Server: T, 
     Robot Number: 0, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, 
     Volume Pool: S, Storage Unit: T, Drive Scan Host: N/A
    
9/18/2014 1:08:13 AM - awaiting resource T - No drives are available
9/18/2014 1:09:55 AM - granted resource T
9/18/2014 1:09:55 AM - granted resource T
9/18/2014 1:09:55 AM - granted resource T
9/18/2014 1:09:55 AM - granted resource Drive007
9/18/2014 1:09:55 AM - granted resource T
9/18/2014 1:09:56 AM - estimated 4291008 Kbytes needed
9/18/2014 1:09:56 AM - Info nbjm(pid=17528) started backup (backupid=e) job for client e, policy Weekl, schedule DailyIncr_ELD_DB on storage unit T
9/18/2014 1:09:59 AM - Info bpbrm(pid=3912) e is the host to backup data from     
9/18/2014 1:09:59 AM - Info bptm(pid=11296) using 65536 data buffer size        
9/18/2014 1:09:59 AM - Info bpbrm(pid=3912) telling media manager to start backup on client     
9/18/2014 1:09:59 AM - Info bptm(pid=11296) using 12 data buffers         
9/18/2014 1:10:03 AM - Info bpbrm(pid=7988) sending bpsched msg: CONNECTING TO CLIENT FOR e  
9/18/2014 1:10:03 AM - connecting
9/18/2014 1:10:04 AM - Info bptm(pid=11936) setting receive network buffer to 263168 bytes      
9/18/2014 1:10:05 AM - Info bpbrm(pid=7988) start bpbkar32 on client         
9/18/2014 1:10:05 AM - Info bpbkar32(pid=8013) Backup started           
9/18/2014 1:10:05 AM - Info bpbrm(pid=7988) Sending the file list to the client      
9/18/2014 1:10:05 AM - connected; connect time: 0:00:02
9/18/2014 1:10:05 AM - begin writing
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e ERR - Cannot lstat ce_um.dsc. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e ERR - Cannot lstat MGR0.rpt. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e ERR - Cannot lstat CE_UM0.rpt. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e ERR - Cannot lstat ce_um0.dsc. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e: ERR - Cannot lstat CP_UM.pce. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e-bkp: ERR - Cannot lstat CE_UM.pce. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e: ERR - Cannot lstat UM000304. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e ERR - Cannot lstat UM000305. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e: ERR - Cannot lstat UM000306. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e: ERR - Cannot lstat UM000307. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e: ERR - Cannot lstat UM000309. Errno = 5: I/O error

9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e ERR - Cannot lstat gglog-ggsci.dmp. Errno = 5: I/O error
9/18/2014 1:11:43 AM - Error bpbrm(pid=7988) from client e ERR - Cannot lstat CP.CE_UM.000000476. Errno = 5: I/O error
9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client e TRV - [/export/home/c60262] is in a different file system from [/export/home]. Skipping
9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client e TRV - [/export/home/e] is in a different file system from [/export/home]. Skipping
9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client e- [/export/home/admin] is in a different file system from [/export/home]. Skipping
9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client e - [/export/home/c60257] is in a different file system from [/export/home]. Skipping
9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client e: TRV - [/export/home/c60098] is in a different file system from [/export/home]. Skipping
9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client e: TRV - [/export/home/c60261] is in a different file system from [/export/home]. Skipping

9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client eTRV - [/export/home/e] is in a different file system from [/export/home]. Skipping
9/18/2014 1:11:44 AM - Info bpbrm(pid=7988) from client e: TRV - [/export/home/c60086] is in a different file system from [/export/home]. Skipping

9/18/2014 1:11:53 AM - Info bpbrm(pid=3912) media manager for backup id e_1410979195 exited with status 0: the requested operation was successfully completed
9/18/2014 1:11:53 AM - Info bpbrm(pid=3912) child done, status 1         
9/18/2014 1:11:53 AM - end writing; write time: 0:01:48
the requested operation was partially successful(1)

The job was successfully completed, but some files may have been
busy or inaccessible. See the problems report or the client's logs for more details.

[Will_Restore · Accepted solution]

from an old thread  https://www-secure.symantec.com/connect/forums/cannot-lstat-updown

Typically, the lstat or lstat64 message followed by an "Errno = 5: I/O error" indicates a file system or hardware error. Another potential cause is when a file is removed during the backup.

as for things like this

TRV - [/export/home/c60262] is in a different file system from [/export/home]. Skipping

that's not a problem, just a reminder

[jim_dalton]

What sort of data are these? Possibly transient maybe? You might want to look at the app running on the server and research how is it  supposed to be backed up. Use used "DB" in the log above suggesting its...a DB...so ...that supports my argument further. Right tool for the right job.

Jim

[H_Sharma]

Hi checked with Solaris team and found these are User ids those dont have any data but are being used for user access. They told us to exclude these files in Backup. But thats not the solution. I want to know why are these not getting backuped up.

[jim_dalton]

You have two issues as pointed out previously:-

1) a bunch of filesystem that arent part of the file selection. These are marked as "Skipping". They have no bearing on your real issue:

2) cannot lstat

and the solaris team have answered q1 (just as will restore did) but ignored q2.

My question was to address q2. And youve not answered my questions. This could be hard going.

Jim

[H_Sharma]

Hi Jim,

These are empty directories and i also found that other policy is taking the backup of these empty directory with the same attributes say Policy type standard etc and backups are not partial. This policy is also excluding these empty directories but not giving the Error bpbrm(pid=7988) from client e ERR - Cannot lstat ce_um.dsc. Errno = 5: I/O error 

[Marianne]

Why have the same data in 2 policies?

With empty folders in exclude list, it makes sense that there will be no errors.

[H_Sharma]

Hi,

Two server say Cluster 1 and Cluster 2 are in same policy with the same backup selection. Any issue with that?

[H_Sharma]

Hello Experts,

I was providing you information but somebody moved it to new thread.

https://www-secure.symantec.com/connect/forums/cluster-nodes-same-policy

[Will_Restore]

Hi, recent question does not seem to be related to this thread.  Please reply on the new thread.

[H_Sharma]

Hi All,

Find issue is with file system and needs to run fsck