Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Snapshot error encountered (status code 156) : ERR - Snapshot Error while reading file

Created: 08 Feb 2013 | 6 comments
Vivek Sahu's picture

Hello,

I configured backups for cluster servers, After writeing around 490 GB data job is failing with Snapshot error for Cluster Drive. Cluster nodes backups are running fine in other policy. We are taking backup of Cluster Drive K:\ using Virtual Cluster Server and IP. Please advise.

Master Server Ver : 7.1.0.2
Client OS : Windows 2003 R2 64 bit
02/07/2013 04:04:59 - estimated 0 kbytes needed
02/07/2013 04:04:59 - Info nbjm (pid=14502) started backup job for client m4msqlvs01, policy Metrix4media-s-win-cluster, schedule Weekly-Full on storage unit bu04_adv_01
02/07/2013 04:05:01 - started process bpbrm (pid=19783)
02/07/2013 04:05:05 - connecting
02/07/2013 04:05:07 - connected; connect time: 0:00:00
02/07/2013 04:05:16 - begin writing
02/07/2013 11:04:02 - Warning bptm (pid=19785) disk pool bu04_dp_01 volume /bu04d2d-14 is full: processing disk full condition
02/07/2013 11:09:52 - current media @aaaaE complete, requesting next media Any
02/07/2013 11:09:54 - granted resource  MediaID=@aaaaD;DiskVolume=/bu04d2d-13;DiskPool=bu04_dp_01;Path=/bu04d2d-13;StorageServer=backup04-dal;MediaServer=backup04-dal
02/07/2013 11:09:54 - granted resource  bu04_adv_01
02/07/2013 11:09:55 - begin writing
02/07/2013 17:31:37 - Error bpbrm (pid=19783) from client m4msqlvs01: ERR - failure reading file: K:\MSSQL\Backup\Metrix4MediaBackup.bak (WIN32 2: The system cannot find the file specified. )
02/07/2013 17:31:38 - Error bpbrm (pid=19783) from client m4msqlvs01: ERR - Snapshot Error while reading file: GLOBALROOT\Device\HarddiskVolumeShadowCopy240\MSSQL\Backup\Metrix4MediaBackup.bak
02/07/2013 17:31:38 - Critical bpbrm (pid=19783) from client m4msqlvs01: FTL - Backup operation aborted!
02/07/2013 17:31:40 - Error bptm (pid=19785) media manager terminated by parent process
02/07/2013 17:32:03 - Error bpbrm (pid=19783) could not send server status message
02/07/2013 17:32:04 - Info bpbkar (pid=8480) done. status: 156: snapshot error encountered
02/07/2013 17:37:49 - end writing; write time: 6:27:54
snapshot error encountered  (156)
 

Comments 6 CommentsJump to latest comment

RamNagalla's picture

02/07/2013 17:31:37 - Error bpbrm (pid=19783) from client m4msqlvs01: ERR - failure reading file: K:\MSSQL\Backup\Metrix4MediaBackup.bak (WIN32 2: The system cannot find the file specified. )

as you are using the cluser name to backup the K Drive, can you make sure that the Both cluster resources  K drive and Cluster IP are in Same Note.

some times it happens like K drive will be in one node and Cluster IP will failover to another node which leads to issue.

what is the backup selection for this cluster  policy ?

Vivek Sahu's picture

Hello Nagalla,

Thanks for you reply, Basically there are 3 IPs.

1 IP is for Virtual Cluster Name and 2 IPs are for their respective Nodes.

So here I have configured Cluster nodes in one policy with Backup Selection of "C:\ and System State,"
and Virtual Cluster in one policy with Backup Selection of "K:\"

I believe It has to do somthing from Client side, Please advise.

RamNagalla's picture

hi,

please try below.. 

1) make sure that you dont have any old Shadow copy images in client side

Vssadmin list shadows

if you find any old shadow copies , delete those,

2) make sure your  Shadow copies size is set to No limite in Drive Properites.

3)In the master server Properties select disable snapshot and continue.

 Host Properties -> Master -> Client Attributes -> <client name>

if you dont fine Client Name , add it and then select the option disable snapshot and continue.

Vivek Sahu's picture

Hello Nagalla, I have done the step 3 and triggered the backup again. it's in the progress. will keep all posted with the status.

Vivek Sahu's picture

Thanks for your reply Dyneshia, Please find bpfis logs 

AttachmentSize
020913.zip 21.94 KB