Managing Backup Devices

4 Topics

Migrating to a new SAN
We're in the process of moving to new datacenters. All servers will be moved over but the SAN won't. The SAN will be replicated to a new SAN in the new datacenters by our SAN admins. That means, the LUNs in the new SAN will be identical to the old, also the LUN numbers. Example output from'vxdisk list' on the current host shows: c1t50050768014052E2d129s2 auto:cdsdisk somedisk01 somedg online This disk will get same LUN nr, but the target name will probably differ as it's new hardware in the new DC. Will this work with Veritas SFHA? If not, is there any way to do this the way the datacenter project wants to? If I could choose to do this my way, I would presentthe LUNs on the new SANto my servers so that I could do a normal host based migration. Add the new LUN to the diskgroup and mirror the data, then remove the old LUN. However, I'm told that the hosts in the current datacenter won't be able to see the new SAN.
Solved
Christian_Akess
10 years ago Place Storage Foundation
2.2KViews
2likes
3Comments
corrupted veritas file system
Dear Support I am facing the below issue whenever running the fsck,please find the below details--- **************************************************************************************************** [10:40am] root@dwse: # /opt/VRTS/bin/fsck -F vxfs /dev/vx/rdsk/storagedg/vardws_vol UX:vxfs fsck: ERROR: V-3-20005: read of super-block on /dev/vx/rdsk/storagedg/vardws_vol failed: No such device or address file system check failure, aborting ... Exit 1 Exit 34 [10:43am] root@dwse: # /opt/VRTS/bin/fsck -F vxfs /dev/vx/rdsk/storagedg/varoptbgw_vol UX:vxfs fsck: ERROR: V-3-20005: read of super-block on /dev/vx/rdsk/storagedg/varoptbgw_vol failed: No such device or address file system check failure, aborting ... Exit 1 [10:44am] root@dwse: # ********************************************************************* Due to which volumes cannot be able to mount,kindly suggest what need to do/ regards....Arup
Solved
ARUP_JYOTI_THAK
11 years ago Place Storage Foundation
4.1KViews
0likes
8Comments
urgent solutin needed
I am executing below command through script to restore volumes ssh -p 22 root@172.19.18.134 dd if=/dev/rmt/0n ibs=4096b | (cd /mnt; vxrestore -c -r -b 4096 -f -) after restoring thre or four volimes, its ending with below message ===> Verifying ossdg/JUMP 2013-05-09 09:15:48 Positioning tape at block 3 Creating ossdg/JUMP_verify (12288 MB) New vxfs FS on JUMP_verify vxrestore -c JUMP_verify Using vxrestore to receive root@172.19.18.134:/dev/rmt/0n to /mnt UX:vxfs vxrestore: ERROR: V-3-20068: cannot open /dev/tty: No such device or address and next volume restore doesnot start I have tried couple of times and it gave the same error for different volumes each time and it stucks randomly please suggest
symsonu
12 years ago Place Storage Foundation
891Views
0likes
6Comments
Disk Error
Dear All, Below is the error messages i am getting from my server root@gtsun3 # vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 sliced rootdisk rootdg online failing c1t0d0s2 sliced c1t0d0s2 rootdg online c9t0d0s2 sliced - - error c9t0d2s2 sliced - - error c9t0d3s2 sliced - - error c9t0d4s2 sliced - - error Could someone help me sort out this issue. Your prompt response will be very helpful. thanks in advanced.
Solved
Mamady123
15 years ago Place Storage Foundation
977Views
0likes
3Comments