Infoscale Enterprise Upgrade
Hello Team, We have an Infoscale cluster hosted Veritas Enterprise Vault. This cluster consists of two nodes in the main site and one node in the DR site, configured with VVR replication. We are planning to upgrade IS from version 7.4.2 to 8.0.2. What is the best approach to minimize downtime during the upgrade process? Option 1: Stop replication, upgrade all nodes simultaneously, and then restart replication. Option 2: Upgrade the DR node first (without stopping services or replication from the HQ), fail over to the DR site, and then upgrade the HQ nodes. Option 3: Upgrade the DR node first (without stopping services or replication from the HQ), stop replication, and then upgrade the HQ nodes. Thank you.
Where install VIOM: on Windows? or on Linux?
Hi every one: I want to install VIOM, I never do it before, and my first question is: Where I should do it? In Windows envioroment? or in Linux Envioroment? All my clusters are in Linux Envioroment: Infoscale 8.0 on Red Hat 8.9. Other question: Is it posible install Cordination Point Service in the same server? All my clusters have 2 nodos: node one in one CPD (site 1) and the node two in other CPD (site 2). I think that the new server (VIOM+CP) shultd be another CPD (site 3). Correct? Thanks Jaime.(CEP-19095) InfoScale Usage & Experience
Interaction Date: April 24 - May 8, 2024 Interaction Type: Online Survey The Veritas Product Management team is interested in getting some information about the use of InfoScale in your environment and your feedback on your overall InfoScale experience. If you are interested in getting more details about this opportunity or in participating in other exciting interactions and are not currently a member of our CPEP program, you can register here: https://cpep.veritas.com then contact us at customer.engagement@veritas.com.
DRL not working on mirrored volumes in VVR - RVG (Mirrored volume doing full resync of plexes)
I think I am hitting a major issue here with a mirrored volume in RVG. SRL is supposed to provide the DRL functionality . Hence DRL logging is explicitly disabled when a volume is added to RVG. However my testing shows that DRL is not working and in the case of a mirror plex out of sync due to a server crash etc, full resync of mirror plexes is happening. (not just the dirty regions). Here is a quick and easy way to recreate the issue: My configuration: Infoscale 8 Redhat 8.7 I have a mirrored volume sourcevol2 (2 plexes) which I created like below: #vxassist -g dg1 make sourcevol2 1g logtype=dco drl=on dcoversion=20 ndcomirror=1 regionsz=256 init=active #vxassist -b -g dg1 mirror sourcevol2 I wait for the synchronization to complete #/opt/VRTS/bin/mkfs -t vxfs -o nomaxlink /dev/vx/rdsk/dg1/sourcevol2 # mount /dev/vx/dsk/dg1/sourcevol2 /sourcevol2 I create SRL as below: #vxassist -g dg1 make dg1_srl 1g layout=concat init=active I create primary rvg as below: #vradmin -g dg1 createpri dg1_rvg sourcevol2 dg1_srl Verified dcm in dco flag is on. #vxprint -g dg1 -VPl dg1_rvg |grep flag flags: closed primary enabled attached bulktransfer dcm_in_dco Added secondary #vradmin -g dg1 addsec dg1_rvg primarynode1 primarynode2 Started initial replication #vradmin -g dg1 -a startrep dg11_rvg primarynode2 Verified replication is uptodate #vxrlink -g dg1 -T status rlk_primarynode2_dg1_rvg VxVM VVR vxrlink INFO V-5-1-4467 Rlink rlk_primarynode2_dg1_rvg is up to date Here is the actual scenario to simulate mirror plexes out of sync : On primary: Run a DD command to put some IO on sourcevol2 #dd if=/dev/zero of=/sourcevol2/8krandomreads.0.0 bs=512 count=1000 oflag=direct In another terminal , force stop the sourcevol2 while dd is going on. #vxvol -g dg1 -f stop sourcevol2 #umount /sourcevol2 Start the sourcevol2 #vxvol -g dg1 start sourcevol2 #vxtask -g dg1 list -l Task: 160 RUNNING Type: RDWRBACK Operation: VOLSTART Vol sourcevol2 Dg dg1 Even though I only changed only few regions on the sourcevol2 (sequential writes of 512b), the volume goes through a full plex resync (as indicated by the time to start the volume). Summary: DRL on a Volume added to an RVG is not working . Hence mirrored volumes are going through a full plex resync as opposed to only resync of dirty regions.Does Infoscale Storage (VVR) support cascaded space-optimized snapshot?
Configuration: Infoscale Storage 8.0 on Linux Infoscale storage foundation supports cascaded snapshot using vxsnap infrontof= to do cascaded snapshots Infoscale storage (with Volume replicator) documentation doesn't describe cascaded snapshot. I checked manpage for vxrvg. Does not have an infront of attribute. Does that mean cascaded space-optimized snapshots are not supported/permitted on RVG?Does VVR support cascaded space-optimized snapshot?
Configuration: Infoscale Storage 8.0 on Linux Infoscale storage foundation supports cascaded snapshot using vxsnap infrontof= to do cascaded snapshots Infoscale storage (with Volume replicator) documentation doesn't describe cascaded snapshot. I checked manpage for vxrvg. Does not have an infront of attribute. Does that mean cascaded space-optimized snapshots are not supported/permitted on RVG?(CEP-18352) Veritas InfoScale – Application Mobility Portal
Interaction Date: January 3 – January 13, 2023 Interaction Type: Usability Study Are you a Veritas InfoScale customer interested in migrating on-premise applications and data to the cloud? Veritas is working on a migration tool that aims to help customers move their data and application from on-premise to the cloud. The Veritas Customer Experience (CX) Research team would like to get your feedback on the early stage InfoScale Application Mobility Portal prototype that can help customers easily and efficiently migrate applications from on-premise to the cloud. We are inviting you to participate in a 60-min user research session over Zoom video/audio conference call. We would like to learn about your thoughts as you interaction with the migration tool prototype. Your participation will help us improve the tool and create a better application/data migration experience. If you are interested in participating other exciting interactions, and are not currently a member of our CPEP program, you can register here: https://cpep.veritas.com then contact us at customer.engagement@veritas.com.
fencing driver fail after storage firmware
In emc unity 380, fencing disk abnormal after firmware. So the b port doesn't go up. Do you have any why this is? https://sort.veritas.com/public/documents/sf/5.0/solaris64/html/sf_rac_install/sfrac_error_messages5.html Does this problem occur when the serial number of the disk is changed?
