Varyonvg on two servers without cluster

[AIXLogician]

Hello All,
I am curious about a the below.

I have two AIX DB servers (one DEV and other PROD), the DBA wanted to have a warm failover on Dev system incase of Disaster.

I have created file systems, and allocated same amount of disk space as in production,

Now the DBA wanted to move his archive logs to Dev system, My Suggestion was
> I will export a file system from DEV system to prod, and he will write his archive logs there. (Archive logs on disk is second option, currently he is directly writing his archive logs to TSM, using API utility).

I know by doing this, the network will be impacted, I am not 100% how the impact will be, so I thought another option.

> I mapped a new disk to both servers, created a file system, and on Prod server ran this # varyonvg -b -u vgname
on Dev I import the disk #importvg -y vgname -R <PVID>,
mounted the file system on both servers, and I can read/write from both servers.

Main question:
I know its not a best practice to use this, Data corruption chances are high.
But, what if I just use the DEV system as RO? will that still corrupt my data?
Is that a safe play, or should I proceed with NFS mount.

FYI,
OS version is AIX 7.1
DB is DB2 v9.7
Storage IBM SVC V7000.

Any help is appreciated.

 

[AIXLogician]

Never mind,
I figured out why GPFS is for, data corruption is always there and no company wants that.

 

[DSMARWAY]

Hi

If you have 2 x servers one for DEV and one for PROD and you are only copying the archive logs ,
why not just copy the archive logs over either as a cron job

or NFS mount the archive log directory from PROD on both servers ?

or even get the DBA to create a logical standby dbase ?

or even backup using RMAN and clone to the other server at night

Varyonvg -b -u as you are aware can cause issues , locks in volume groups , which may prevent filesystem from increasing , on;ly a reboot will
fix , since being PROD can you do it ?

Thanks