Drive V backup isn't being taken by Symantec in the schedule

Created: 14 Jan 2013 | 6 comments

Dears,

I have a backup configuration in which there's a windows policy with a full schedule policy with multi data streams and multiplexing enabled so in the activity monitor I cans see job per each drive of the backup being taken , the problem is when the scheduled begin a certain drive isn't being taken but when I do the manual backup I can see it being taken but it takes longer time and it shown more space being taken than its real space

It's Drive letter V

for me it's something very strange does any one have any thing to tell me and help me with ? Does any one have any suggestion ?

Thanks

Discussion Filed Under:

Backup and Recovery, NetBackup - 7.5, NetBackup

Login or register to post comments
Comments RSS Feed

Comments 6 Comments • Jump to latest comment

Nagalla Certified

Drive V backup isn't being taken by Symantec in the schedule - Comment:14 Jan 2013 : Link

hi,

could you provide the output of

bppllist <Policyname> -U

and also the bpmount command output in clinet

does that Drive is part of cluster Drive?

also enable the log of bpbkar and bpfis in client with multistream and let the backup run, and provide the logs as attachment.

Mahmoud El-Tanbouly Partner

Drive V backup isn't being taken by Symantec in the schedule - Comment:14 Jan 2013 : Link

I created the folders named bpbkar & bpfis under \Program Files\Veritas\Netbackup\Logs

is this how I enable both these logs ?

& here is the output you asked for

:\Program Files\Veritas\NetBackup\bin\admincmd>bppllis

-U

------------------------------------------------------

olicy Name: Windows-Full-Diff-AEFS1

Policy Type: MS-Windows

Active: yes

Effective date: 01/03/2013 15:43:47

Backup network drvs: no

Collect TIR info: no

Mult. Data Streams: yes

Client Encrypt: no

Checkpoint: no

Policy Priority: 5

Max Jobs/Policy: Unlimited

Disaster Recovery: 0

Collect BMR info: no

Residence: (specific storage unit not requi

Volume Pool: NetBackup

Server Group: *ANY*

Keyword: (none specified)

Data Classification: -

Residence is Storage Lifecycle Policy: no

Application Discovery: no

Discovery Lifetime: 28800 seconds

SC Application and attributes: (none defined)

Granular Restore Info: no

Ignore Client Direct: no

nable Metadata Indexing: no

ndex server name: NULL

Use Accelerator: no

HW/OS/Client: Windows-x86 Windows2003 aefs1

Include: ALL_LOCAL_DRIVES

Schedule: Full-Thu

Type: Full Backup

Maximum MPX: 32

Synthetic: 0

Checksum Change Detection: 0

PFI Recovery: 0

Retention Level: 3 (1 month) 3 (1 month)

Number Copies: 2

Fail on Error: 0 0

Residence: - ae-bkp-hcart2-robot-tld-2

Volume Pool: WINDOWS-FULL-THU WINDOWS-FULL-

Server Group: *ANY* *ANY*

Calendar sched: Enabled

Allowed to retry after run day

Thursday, Week 1

Thursday, Week 2

Thursday, Week 3

Thursday, Week 4

Thursday, Week 5

Residence is Storage Lifecycle Policy: 0

Schedule indexing: 0

Daily Windows:

Thursday 17:00:00 --> Sunday 08:10:00

Schedule: Diff-Mon

Type: Cumulative Incremental Backup

Maximum MPX: 32

Synthetic: 0

Checksum Change Detection: 0

PFI Recovery: 0

Retention Level: 3 (1 month) 3 (1 month)

Number Copies: 2

Fail on Error: 0 0

Residence: - ae-bkp-hcart2-robot-tld-2

Volume Pool: WINDOWS-DIFF-MON WINDOWS-DIFF-

Server Group: *ANY* *ANY*

Calendar sched: Enabled

Monday, Week 1

Monday, Week 2

Monday, Week 3

Monday, Week 4

Monday, Week 5

Residence is Storage Lifecycle Policy: 0

Schedule indexing: 0

Daily Windows:

Monday 17:00:00 --> Tuesday 08:00:00

Schedule: Diff-Sun

Type: Cumulative Incremental Backup

Maximum MPX: 32

Synthetic: 0

Checksum Change Detection: 0

PFI Recovery: 0

Retention Level: 3 (1 month) 3 (1 month)

Number Copies: 2

Fail on Error: 0 0

Residence: - ae-bkp-hcart2-robot-tld-2

Volume Pool: WINDOWS-DIFF-SUN WINDOWS-DIFF-

Server Group: *ANY* *ANY*

Calendar sched: Enabled

Sunday, Week 1

Sunday, Week 2

Sunday, Week 3

Sunday, Week 4

Sunday, Week 5

Residence is Storage Lifecycle Policy: 0

Schedule indexing: 0

Daily Windows:

Sunday 17:00:00 --> Monday 08:00:00

Schedule: Diff-Tue

Type: Cumulative Incremental Backup

Maximum MPX: 32

Synthetic: 0

Checksum Change Detection: 0

PFI Recovery: 0

Retention Level: 3 (1 month) 3 (1 month)

Number Copies: 2

Fail on Error: 0 0

Residence: - ae-bkp-hcart2-robot-tld-2

Volume Pool: WINDOWS-DIFF-TUE WINDOWS-DIFF-

Server Group: *ANY* *ANY*

Calendar sched: Enabled

Tuesday, Week 1

Tuesday, Week 2

Tuesday, Week 3

Tuesday, Week 4

Tuesday, Week 5

Residence is Storage Lifecycle Policy: 0

Schedule indexing: 0

Daily Windows:

Tuesday 17:10:00 --> Wednesday 08:00:00

Schedule: Diff-Wed

Type: Cumulative Incremental Backup

Maximum MPX: 32

Synthetic: 0

Checksum Change Detection: 0

PFI Recovery: 0

Retention Level: 3 (1 month) 3 (1 month)

Number Copies: 2

Fail on Error: 0 0

Residence: - ae-bkp-hcart2-robot-tld-2

Volume Pool: WINDOWS-DIFF-WED WINDOWS-DIFF-

Server Group: *ANY* *ANY*

Calendar sched: Enabled

Wednesday, Week 1

Wednesday, Week 2

Wednesday, Week 3

Wednesday, Week 4

Wednesday, Week 5

Residence is Storage Lifecycle Policy: 0

Schedule indexing: 0

Daily Windows:

Wednesday 17:00:00 --> Thursday 08:00:00

:\Program Files\Veritas\NetBackup\bin\admincmd>

------------------------------------------------------------------------------

bpmount output

--------------

C:\Program Files\Veritas\NetBackup\bin>bpmount

local: Shadow Copy Components:\ on Shadow Copy Components:\

CDROM: A:\ on A:\

local: C:\ on C:\

local: E:\ on E:\

local: F:\ on F:\

local: G:\ on G:\

local: H:\ on H:\

local: I:\ on I:\

local: J:\ on J:\

local: K:\ on K:\

local: L:\ on L:\

local: M:\ on M:\

local: N:\ on N:\

local: Q:\ on Q:\

local: S:\ on S:\

local: T:\ on T:\

local: V:\ on V:\

local: W:\ on W:\

local: X:\ on X:\

local: Y:\ on Y:\

EXIT STATUS 0: the requested operation was successfully completed

Mahmoud El-Tanbouly Partner

Drive V backup isn't being taken by Symantec in the schedule - Comment:14 Jan 2013 : Link

It's worth mentioning that when I tried to create the shadow copy enabled on Drive V

It gives this error

Insufficient storage available to create the shadow copy even though there's 14 GB free out of 393 GB

Nagalla Certified

Drive V backup isn't being taken by Symantec in the schedule - Comment:14 Jan 2013 : Link

hi,

use the below T/N to configure the another Volume for shadow copy

use the Drive which have the enough space

http://www.symantec.com/business/support/index?pag...

lets see how it goes...

Yasuhisa Ishikawa Partner Accredited Certified

Drive V backup isn't being taken by Symantec in the schedule - Comment:15 Jan 2013 : Link

Please check exclude list of this machine. Someone in backup admin team(or you) might have added V:\ in to exclude list.

Second point - check if compression is enabled on V:\. Total amount of acutual file size become larger than the esed space displayed in drive properties.

Authorized Symantec Consultant(ASC) Data Protection in Tokyo, Japan

Mahmoud El-Tanbouly Partner

Drive V backup isn't being taken by Symantec in the schedule - Comment:15 Jan 2013 : Link

This message was shown beause the backup was already still going on on this drive

so I think this wasn't the problem

the strange thing that even when I do the manual backup this drive specifically takes so much longer time which is very weird and when I open the properties dialog box I can see the transfer rate is so low , It was only 47K which is also very strange and today during the backup job was taken Its state turned unknown

Thanks so much for your help

Drive V backup isn't being taken by Symantec in the schedule

Comments 6 Comments • Jump to latest comment

Would you like to reply?

Links