Dave
If you are uncomfortable with this, and its still sitting at 1%, then
possibly you may want to abort and just do full backups.
Its also possible, it may be sat on the 1% as its doing large files perhaps?
Simon Weaver
Technical Support
Windows Domain Administrator
EADS Astrium
Tel: 02392-708598
Email: Simon.Weaver AT Astrium.eads DOT net
-----Original Message-----
From: Dave Markham [mailto:dave.markham AT fjserv DOT net]
Sent: 01 February 2006 12:14
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] duplication speed
People i am moving an infrastructure from one site to the other. As part
of this we are splitting things between different trucks for resilience.
I performed a full backup of the infrastructure yesterday and today am
duplicating it.
I run solaris 8 Netbackup 5.0 mp5S2.
I am slightly concerned as it reckons the job is only 1% through on the
gui.
When i run iostat -xn |egrep "rmt/0|rmt/2" i can see around 5mb/s which
is about right for the DLT7000 drives i have in the L1000.
There are 32 images in total to duplicated and the backups took around 8
hours to complete 290 gig. I need the duplications to be finished by
tomorrow and as it has been nearly 2 hours now and saying only 1%
complete im worried it wont be done.
Looking in the bptm logs i can see entries like this :-
12:04:15.737 [307] <2> io_write_back_header: drive index 0,
clienta_1138722148, file num = 23, mpx_headers = 7, copy 2 12:04:15.737
[307] <2> io_write_back_header: drive index 0,
client2_1138722153, file num = 23, mpx_headers = 6, copy 2 12:04:15.738
[307] <2> io_write_back_header: drive index 0,
client3_1138722154, file num = 23, mpx_headers = 5, copy 2 12:04:15.739
[307] <2> io_write_back_header: drive index 0,
client4_1138722155, file num = 23, mpx_headers = 4, copy 2 12:04:15.740
[307] <2> io_write_back_header: drive index 0,
client5_1138722156, file num = 23, mpx_headers = 3, copy 2 12:04:15.741
[307] <2> io_write_back_header: drive index 0,
client6_1138722157, file num = 23, mpx_headers = 2, copy 2 12:04:15.741
[307] <2> io_write_back_header: drive index 0,
client7_1138722158, file num = 23, mpx_headers = 1, copy 2 12:04:15.742
[307] <2> write_data: completed writing backup header,
start writing data when first buffer is available, copy 2 12:04:15.742 [307]
<2> write_data: first write, twin_index: 0 cindex: 0
dont_process: 1 wrote_backup_hdr: 1 finished_buff: 0 12:04:15.742 [307] <2>
write_data: received first buffer (64512 bytes),
begin writing data
I am wondering what file num = Surely its not actually a file number
and its only written 23 files in 2 hours.
I used the below for the duplication as the backups are multiplexed.
bpduplicate -dp dupe_monthly -dstunit L1000 -hoursago 22 -sl Monthly
-mpx -L /var/log/move-dupe.log &
Is it worth be canceling and just doing another full backup or do people
think the duplication will complete?
Thanks
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or
otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
|
