VCS new volume created. Need to add up under existing Resource Group under 2 node clustered Solaris 10 Server...Important..please assist
Hi, I am newbi to VCS. OS is Solaris10. Two node cluster env. New filesystem already created and mounted with dedicated Vertual IP and is already under VCS. We have added two more Vol's (Vol03 & Vol04) in the existing Resource Group say 'node1_rg' Guys, please help me out to know the sequential and step by step procedure with commands to take the newly created Volumes under existing Resource Group......and how to carry out the Failover Test. this is a test server on which we need to do the task. Oracle Database is also there and we can coordinate with App & DBA team to do this activity...... Pleaseeeeeeee help. this is first time I had been to this forum seeking the help... Thanks, Rinku, Pune- IndiaSolved3.3KViews2likes9CommentsVM backup failing after installing SF Basic on Hyper-V Core server
Hi all, We have Hyper-V server with 10 virtual machines. We are using NetBackup 7.1.0.4 as backup software. Before installing SF Basic 6.0 , backup of all VM's was going fine. Now the backup of all VM's that are in running state is failing with error: Snapshot error encountered (156). Backup of VM's that are not running is going fine. I've installed SF Basic on a second Hyper-V server and I got the same situation. After that I've uninstalled SF Basic from this server and all backups are working fine. In the VEA console I can see the snapshots for the VM volumes created and after 2 minutes they are deleted. (screenshot in attacment) This is the error in the bpfis log from the NetBackup client: 10:58:01.940 [996.2672] <2> onlfi_vfms_logf: INF - snapshot services: vss:Thu May 10 2012 10:58:01.940000 <Thread id - 2672> VSS API ERROR:- API [QueryStatus] status = 42309 [VSS_S_ASYNC_PENDING] 10:58:31.332 [996.5336] <2> send_keep_alive: INF - sending keep alive 10:59:32.174 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:00:33.017 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:01:33.860 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:02:34.702 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:03:35.544 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:04:36.385 [996.5336] <2> send_keep_alive: INF - sending keep alive 11:05:17.632 [996.4896] <2> onlfi_vfms_logf: INF - snapshot services: vss:Thu May 10 2012 11:05:17.632000 <Thread id - 4896> VssNode::getSelectedWriterStatus: GetWriterStatus FAILED for Selected writer [Microsoft Hyper-V VSS Writer], writer is in state [5] [VSS_WS_WAITING_FOR_BACKUP_COMPLETE]. hrWriterFailure [800423f4] [-2147212300] 11:05:17.632 [996.4896] <2> onlfi_vfms_logf: INF - snapshot services: vss:Thu May 10 2012 11:05:17.632000 <Thread id - 4896> VssNode::make getSelectedWriterStatus FAILED 11:05:17.632 [996.4896] <2> onlfi_vfms_logf: INF - vfm_freeze_commit: vfm_method_errno=[38] 11:05:17.632 [996.4896] <32> onlfi_fim_split: FTL - VfMS error 11; see following messages: 11:05:17.632 [996.4896] <32> onlfi_fim_split: FTL - Fatal method error was reported 11:05:17.632 [996.4896] <32> onlfi_fim_split: FTL - vfm_freeze_commit: method: Hyper-V, type: FIM, function: Hyper-V_make Does someone know what could be the problem? Are there any debuglogs in Storage Foundation to help me with this problem and where can I enable/find them?2.7KViews0likes3CommentsVVR support ON AIX 6.1
Hi, I am planning to implement Veritas Volume Replication from DC to DR on IBM AIX 6.1. Curently I am having VCS_SF5.1 including VxVm. As per IBM they are saying implementing VVR on AIX 6.1 will slow down server performance. Appreciate if any one can clarify the doubt. Rupesh2.3KViews1like2CommentsVeritas cluster issue
Hi We have a VCS of two node. Two file systems are under VCS configured from VXVM. One file system got 100% full.Now we have rebooted the cluster node & the mount points started to show,but after some time that file system got disappear,Checked with concerned DG that also got disabed,we tried to manually import & got succeded.But after starting the volumes we tried to mount the filesystem under the specified mount point. But the below error giving--- # mount /dev/vx/dsk/bgw1dg/vol01 /var/opt/BGw/Server1 mount: /dev/vx/dsk/bgw1dg/vol01 is not this fstype # Kindly suggest what could be the cause. regards...ArupSolved2.2KViews4likes5CommentsMigrating 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.Solved2.2KViews2likes3CommentsWindows 2008 R2 Backup failing since VSF 5.1 SP2 is installed
We have a Windows 2008 R2 failover cluster.We installed Storage Foundation 5.1 SP2 to provide dynamic disks to the cluster. We are trying to run a BMR backup on the active node but we have the folowing error: The shared restore point operation failed with error (0x81000101) The creation of a shadow copy has timed out. Try this operation again. We adjusted the timeout parameters to 20 minutes than to 30 minutes: "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\SPP" - Create a new Registry value of type DWORD with name "CreateTimeout" - Change value to 12000000(2*10*60*1000 = 20 mins) in decimal Interestingly the backup is failing again and again: The backup operation stopped before completing. Detailed error: ERROR - The shared restore point operation failed with error (0x 81000101) The creation of a shadow copy has timed out. Try this operation again. Windows Backup timed-out before the shared protection point was created. ERROR - The shared restore point operation failed with error (0x81000101) The creation of a shadow copy has timed out. Try this operation again. Is there any reason why the windows backup cannot access the SF disks to make VSS snapshots? Before installing SF everything was working like a charm.1.9KViews0likes7CommentsEnable Deduplication on NetBackup 7.5
Hi, We have got NetBackup 7.5.0.6 running on Windows Server 2008 and currently backing up data on SAN Storage. I want to enable deduplication on it. Couldyou please provide me the best practice procedure to do so ? Where the deduplication should be enabled on client or Server level and how it will be reflected on SAN storage? Please adivse Regards, --Tarek--1.5KViews0likes1CommentI have mirrored the data in between two sotrage
Hi, I am using Storage Foundation for windows HA, Now i wan to replace my old HP storage with new NetApp storage for this i mirrored the data of Exchange servers 2007. before removing the HP storage i just want to make sure the my mirrored data is consistent. Is there any tool or option in the SFWHA to check the data conssitency. I am also using VVR between two sites for teplication the DATA Sajid1.4KViews1like14Commentsvxconfigbackup warning
Whenever I try to backup the configuration, warning is shown as below. Also when i try to restore it, the operation fails. /etc/vx/bin/vxconfigbackup -l /opt/configbackup Start backing up diskgroup abcdg to /opt/configbackup/abcdg.1294657147.185.sys1_01 ... VxVM vxconfigbackup WARNINIG V-5-2-3608 On disk diskgroup configuration for diskgroup abcdg is invalid, please check this dg VxVM NOTICE V-5-2-3100 Backup complete for diskgroup: abcdg ls /opt/configbackup: abcdg.1294657147.185.sys1_011.4KViews0likes14Commentsreallocate the /etc/vx/cbr/bk , vg config backup file without any service restart ...
1. Create the directory to copy the vg config backup file . # mkdir -p /tech/vgconfigbackup/bk ( please must create the "bk" directory ) 2. Take the backup of scripts " /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh " # cp /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh /usr/lib/vxvm/voladm.d/lib/vxcbrlib.sh_bkp<date> 3. Made the required change care fully in below script . # vi /usr/lib/vxvm/voladm.d/lib/vxcbrlib comment the existing line "CF_BKUP_BASE_PATH" and change CF_BKUP_BASE_PATH to point to a new location. 4. Delete the all old vg configuration file backup from default location . 5. Take the new vg configuration backup and test 6. Check the new vg configuration file backup in new location .1.4KViews4likes3Comments