Replication File System become RAW.
Updated: 31 May 2010 | 9 comments
This issue has been solved. See solution.
Hi all,
I was just wondering does anyone of you here have the experience that the file system of the secondary replication volume (Secondary RVG) turned RAW after the replication have commenced?
I am using the backup and restore method to do the initial sync for a pretty large volume across a region.
After the restoration of the volume, the file system for the secondary volume reflects as "NTFS" but the problem comes only after the replication have started. Once the replication have started, the file system becomes "RAW". And even though I have paused, enable data access and mount up the secondary volume, I still do cannot see or access the drive. The volume status is then reflected as "RAW".
May I check with the experts or gurus here that what could be the cause of the problem and is there any workaround or remedies to it?
Thanks...
Michael
Discussion Filed Under:
Comments
The same thing happened with me but i stopped replication and start replication again and the partition becomes NTFS or converted from RAW to normal.....(but after the Start/Stop replication the replication starts from zero again) but you can view the replicated volume
or try to import or deport the Disk Group
Thanks
ZAHID HASEEB
Any comment will be appreciated. Mark as Solution if your query is resolved
__________________
Thanks in Advance
Zahid Haseeb
zahidhaseeb.wordpress.com
VVR is block based
VVR is block based replication, so the secondary site is not accessible, unless you either: 1. stop replication (usually not what you want), or better: 2. migrate so that the Seconday takes over, or best: 3. take a snapshot of the secondary to temporarily access the data. Once that is done, you can now see the data on the volume correctly.
Accessing the file systems on both the Primary and Secondary simultaneously, while replication is going on, is a VVR no-no. Some replications solutions can do this: read "file-system based replication" like DFS, however they also have no support of applications like databases (VVR supports any application or file system types).
I suspect that the RAW thing on the Secondary while replication is going on (even paused, since replication is still in the picture) is expected.
Principal Learning Consultant with Symantec Education Course Development
Error while taking snapshot
HI,
After i make the snap prepare on the secondary voulme replicated for eg my c: , and then i click on snap shot then i get an error message "Error V-76-58657-13
"The specified volume(s) are not supported for the requested operation by VSS provider ".
When i click on the link i am routed to the knowledge base which indiactes that they do not have any such error in the knowledge base. Please help me correct my mistake if i am doing something wrong while taking a snap shot . Now , to overcome this error i have to stop replication at the primary then to go to secondary then take a snapshot of c: then a disk appears which has all the data replicated in it .
Please help me in understanding this procedure is this how SNAPSHOT feature works or am i doing something wrong .I would also like to add that i have added an additional drive thats separate from my replicated drives and this drive comes in harddisk2 and i have put this drive in the same group as primary .
Rishi Bhaskar
in replication secondary is
in replication secondary is inactive while replciation is goin on
In vvr secondary is inactive
In vvr secondary is inactive while replication is going on , so you can check the monitor to view how many bytes have been transferred . Secondly import to disk groups is usually required only if machine in which vvr is shutdown its nothing critical and you can do replication in raw also when raw is indiacted on ure Rep log volume .
Hi, I encountered this error
Hi,
I encountered this error from the event log everytime the replication was done,
1. "The system failed to flush data to the transaction log. Corruption may occur."
2. "{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere."
3. "Application popup: Windows - Delayed Write Failed : Windows was unable to save all the data for the file D:\. The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere."
Nothing was replicated to the secondary host from the primary host. I tried to stop the replication and dismount the drive with the command chkdsk /x and everything was replicated. kindly advise. thanks.
Different post?
Hi freshmeat, I'd post this as a new issue. You might also consider contacting support.
Principal Learning Consultant with Symantec Education Course Development
Hi Tomer Gurantz, Thanks for
Hi Tomer Gurantz,
Thanks for your reply. kindly set this issue severity as priority and urgent? Thanks.
completely different issue
freshmeat,
Tomer was advising you to post this as a new issue, since the existing post is over a year old, and also appears to be for a completely different issue/problem.
Re: opening a case with support, you need to do this yourself, so you could advise re: setting severity, etc, when you open the case with them.
If this post has helped you, please vote or mark as solution
Would you like to reply?
Login or Register to post your comment.