Correct. You can also make the clones mount as a drive letter and back
them up that way.
Doug Preston
Systems Engineer
Land America Tax and Flood Services
Phone 626-339-5221 Ext 1104
Email dlpreston AT landam DOT com
------------------------------------------------------------------------
------------
NOTICE: This electronic mail transmission may constitute a communication
that is legally privileged. It is not intended for transmission to, or
receipt by, any unauthorized persons. If you have received this
electronic mail transmission in error, please delete it from your system
without copying it, and notify the sender by reply e-mail, so that our
address record can be corrected.
------------------------------------------------------------------------
------------
-----Original Message-----
From: Justin Piszcz [mailto:jpiszcz AT lucidpixels DOT com]
Sent: Thursday, December 20, 2007 11:31 AM
To: Preston, Douglas L
Cc: veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Cannot backup files attached on SAN mount
point?
Unfortunately I do not control the Windows server, I will ping the guys
responsible and see what method they are using, also you are using Cross
Mount points correct? Without that option, no files get backed up.
Justin.
On Thu, 20 Dec 2007, Preston, Douglas L wrote:
> I have 2 servers, 2 clones each that I backup via attached clone
drives
> from a san. How are you attaching the clone drive to z: on your
server
> you are trying to backup?
> Are you running a hardware rescan after attaching them? Below is how
I
> do it and the clones are attaching under a subdirectory mount point
> like yours are.
>
>
> REM
> REM Fracture Cloned LUNS from Source LUN
> REM Attach cloned LUNS to BU01
> REM DAILY FRACTURE BATCH FILE
> REM
>
>
> REM ********* SQL *********
> navicli.jar -User user -Password password -Scope 0 -address 1.2.2.5
> snapview -fractureclone -name SQL_CloneGroup_LUN125_LUN124 -cloneid
> 0100000000000000 -o
> navicli -h clariion storagegroup -addhlu -gname bu01 -hlu 124 -alu 124
>
> navicli.jar -User user -Password password -Scope 0 -address 1.2.2.5
> snapview -fractureclone -name SQL_CloneGroup_LUN127_LUN126 -cloneid
> 0100000000000000 -o
> navicli -h clariion storagegroup -addhlu -gname bu01 -hlu 126 -alu 126
>
> REM ********* MSQL *********
> navicli.jar -User user -Password password -Scope 0 -address 1.2.2.5
> snapview -fractureclone -name MSQL_CloneGroup_LUN41_LUN43 -cloneid
> 0100000000000000 -o
> navicli -h clariion storagegroup -addhlu -gname bu01 -hlu 43 -alu 43
>
> navicli.jar -User user -Password password -Scope 0 -address 1.2.2.5
> snapview -fractureclone -name MSQL_CloneGroup_LUN42_LUN44 -cloneid
> 0100000000000000 -o
> navicli -h clariion storagegroup -addhlu -gname bu01 -hlu 44 -alu 44
>
> REM *** devcon.exe is available from Microsoft
> REM Next line causes windows to rescan hardware
> REM should be ran 5 to 10 minutes after the navicli command as windows
> is slow seeing the drives.
>
> devcon rescan
>
>
>
>
> REM
> REM Remove Cloned LUN from svcacibu1 and re-synchronize the clone LUN
> with its Source LUN
> REM DAILY SYNCHRONIZE BATCH FILE
> REM
>
>
>
> REM ********* SQL *********
> navicli -h clariion storagegroup -removehlu -gname bu01 -hlu 124 -o
> navicli.jar -User user -Password password -Scope 0 -address 1.2.2.5
> snapview -syncclone -name SQL_CloneGroup_LUN125_LUN124 -cloneid
> 0100000000000000 -o
>
> navicli -h clariion storagegroup -removehlu -gname bu01 -hlu 126 -o
> navicli.jar -User user -Password password -Scope 0 -address 1.2.2.5
> snapview -syncclone -name SQL_CloneGroup_LUN127_LUN126 -cloneid
> 0100000000000000 -o
>
>
> REM ********* MSQL *********
> navicli -h clariion storagegroup -removehlu -gname bu01 -hlu 43 -o
> navicli.jar -User services -Password r00tus3r -Scope 0 -address
1.2.2.5
> snapview -syncclone -name P-MSQL_CloneGroup_LUN41_LUN43 -cloneid
> 0100000000000000 -o
>
> navicli -h clariion storagegroup -removehlu -gname bu01 -hlu 44 -o
> navicli.jar -User user -Password password -Scope 0 -address 1.2.2.5
> snapview -syncclone -name P-MSQL_CloneGroup_LUN42_LUN44 -cloneid
> 0100000000000000 -o
>
> REM --- end of batch file
>
>
>
>
> Doug Preston
>
>
> -----Original Message-----
> From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Justin
> Piszcz
> Sent: Thursday, December 20, 2007 9:54 AM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Cannot backup files attached on SAN mount point?
>
> Does anyone here backup "cloned" or aka volumes via a host connected
to
> a
> SAN?
>
> I get this error using NetBackup 5.1MP4/MP6 and/or NetBackup 6.0MP5,
> both
> yield the same result:
>
> Here is what it looks like:
>
> 12/20/2007 05:00:00 - requesting resource MYSTORAGEGROUP
> 12/20/2007 05:00:00 - requesting resource
> master-server.com.NBU_CLIENT.MAXJOBS.client-name.com
> 12/20/2007 05:00:00 - requesting resource
> master-server.com.NBU_POLICY.MAXJOBS.MYPOLICY001
> 12/20/2007 05:00:01 - granted resource
> master-server.com.NBU_CLIENT.MAXJOBS.client-name.com
> 12/20/2007 05:00:01 - granted resource
> master-server.com.NBU_POLICY.MAXJOBS.MYPOLICY001
> 12/20/2007 05:00:01 - granted resource AB1234
> 12/20/2007 05:00:01 - granted resource Drive02
> 12/20/2007 05:00:01 - granted resource media-server.com
> 12/20/2007 05:00:02 - started process bpbrm (pid=10339)
> 12/20/2007 05:00:09 - connecting
> 12/20/2007 05:00:09 - mounting AB1234
> 12/20/2007 05:00:10 - connected; connect time: 0:00:00
> 12/20/2007 05:00:45 - mounted AB1234; mount time: 0:00:36
> 12/20/2007 05:00:45 - positioning AB1234 to file 3
> 12/20/2007 05:01:48 - positioned AB1234; position time: 0:01:03
> 12/20/2007 05:01:48 - begin writing
> 12/20/2007 07:59:20 - Error bpbrm (pid=10360) from client
> client-name.com:
> ERR - failure reading file: Z:\SAN\EXCHANGE\CLONE1\store1.edb (WIN32
21:
>
> The device is not ready. )
> 12/20/2007 07:59:21 - end writing; write time: 2:57:33
> the requested operation was partially successful (1)
>
> The actual problem: (WIN32 21: The device is not ready. )
>
> Does anyone have any idea how to fix this issue or has anyone run into
> it
> before?
>
> There are several mount points, for example:
> Z:\SAN\EXCHANGE\CLONE2\store2.edb
> Z:\SAN\EXCHANGE\CLONE2\store3.edb
> Z:\SAN\EXCHANGE\CLONE2\store4.edb
>
> They all fail with the same error, I have read the following
suggestions
>
> here:
>
https://forums.symantec.com/syment/board/message?board.id=21&message.id=
> 39090
>
> However, RSM is disabled and these errors persist.
>
> Any clues?
>
> Justin.
> _______________________________________________
> Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
