SRM restoration - DR-IP-customization - shadow vms

Similar Questions

• System Restore cannot create restore, point because the "shadow copy provider had an unexpected error." What can I do?

  Have a Dell Inspiron 1545 with Vista.  System Restore cannot create restore, point because the "shadow copy provider had an unexpected error."   What can I do?

  Hi JamesParwulski,

  Method 1
  I suggest you to scan SFC.

  How to use the System File Checker tool to fix the system files missing or corrupted on Windows Vista or Windows 7.
  http://support.Microsoft.com/kb/929833

  Method 2
  I suggest you perform a checkdisk.

  Check your hard drive for errors
  http://Windows.Microsoft.com/en-us/Windows-Vista/check-your-hard-disk-for-errors

• What shadow VMs are created?

  One of my 4 data warehouses associated with my vDC fills.  When shadow VMs come into play to allow my VMs fast provisioned to use my other data warehouses?  Is there a threshold?  If so is it configurable?

  Shadow VMs are disks to a computer virtual deployed "parent".  Threshold is located in your system vDC on the section data stores, to manage and monitor.  Set the 'Red' zone to a value greater than the amount of free space.

  When you use the quick Provisioning, we prefer the data store that has the existing string of linked Clone.  That's why a data store fills.

  Once we missed the minimum free space requirements, we will force the linked clone chaing to migrate the following data with more free space store.

  In the future, we have 2 warehouses of data with the chain of clone to deploy and can balance the load in this way.

  What I've seen, is when a data store is a bit bigger than the rest... only things makes a big awkward, given that the original records will be on the same volume, making the above less desirable scenario as the initial implementation uses more space as the choice.

  long story short, increase your red zone to force the data store selector to choose another.

• SRM 4.0 on coherence HDS9990 and VMs

  Hi all

  This message is an attempt to better understand the workings of the SRM 4.0 with respect to VMs consistency (which is our main goal).

  Our farm will be upgraded to vSphere ESX 3.5 Upd 3, and we do not need to implement a DR solution that will be entirely based on a HDS9990 storage solution.

  What is not clear to us, it's whether or not the SRM 4.0 is *THE* best product we can integrate into our environment in order to ensure consistency in machines virtual or not.

  The SRM 4.0 documentation, it seems that a SRM 4.0 based DR solution should suite our needs.

  Our question is: SRM always ensures the consistency of virtual machines?

  It is based on the mechanisms of replication storage HW? What is the role of the storage replication adapter provider?

  Would it not be better to rely on a snapshot solution (i.e. a build on technology VMware Consolidated Backup), instead?

  Thank you very much in advance for your help.

  Best regards

  Salvatore

  SRM is part of a recovery solution disaster that looks is the project that you are working.

  In a HDS / SRM element of data replication solution is managed by CONTINUOUS table level. The consistency of the data is determined by the replication schedules you apply to volumes on the table (sync / async) and all works at the block level.

  Many clients, ask questions about watching DR VM consistency / SRM solutions, but you need to think about the scenarios in which you would use SRM/HDS. If you have an event suddenly disaterous then you won't have time to do things consistent in almost all scenarios, you can consider as they are sudden and usually catastrophic. So if SRM has taken quiece points would not give you a realistic view of how things would happen in real life.

  One of the highlights of the SRM is that it allows you to conduct trials of DR no - disturb without affecting your production environment. SRM for this using replication storage (SRA) adapters to communicate with the table on the recovering site and to present a snapshot of the storage (containing the protected virtual machine) at the level of the table using the table feature. These snapshots of table are presented by MRS to the ESX host on the recovering site and the virtual machine is recovered and connected to the defined networks 'test '.

  If we hosted SRM to join something like VSS and ensure that all data has been the file system rather than consistent crash on the recovering site, that would give you a false confidence that your environment could be recovered in the case of an event suddenly Dr, for the simple reason if a plane or Meteor suddenley lands on your datacenter at 03:30 on Sunday how would you know? How would you have time to hang anything?

  For this reason, RS does NOT and simply uses the most recent copy of the data on the Bay of storage to test (and also for failovers). This is massively useful because you can now prove it to the company in the case of sudden unexpected failure you can prove that you can recover the cold environment and that all your operating systems and applications can crash recover themselves to the last known state. RDBMS systems are a good example. In a previous life, I was involved with a well known RDBMS for long. A feature he had (like most of them) was the ability to roll forward recording in the case of a system failure. Now even if you could always tell the company such protection was in place via transaction logs application that it was very difficult for the company to test yourself on your claims as it meant pulling the plug on the server. Now with MRS you can test this scenario VERY easily by simply running a recovery plan in test mode, raise the RDBMS on the recovering site and then prove the database gets as its configuration says he should.

  Remember that consistency with regard to storage devices for replication updates can be applied at the level of the table of logifcally, but the data blocks during any recovery with any table will always be the last copies. This means if you have multi levels of applications or applications that use a lot of records, then these are usually grouped on the table to ensure consistency during the replication update. During recovery recover the crash of the OS and applications, and in fact most if not all modern OS we know and love are more than capable to do.

  Your point around VCB is relevant who so as to have a solution like MRS. up with HDS continuous as in your example, there is always a place for VCB. Just because you have DR in place does not mean that you need not backup. Backups you give version control and should go hand in hand with any DR solution. Most of the clients will replicate their backup vaults to their sites of DR as well so that not only they have most recent data (provided by storage replication) but also have the backups available as well if they need never then to perform a collection version. Don't forget THAT VCB is a backup solution is NOT DR. In the case of a situation Dr. SRM will recover your environment after a scheduled recovery plan you created to make sure that everything happens in the right order and it requires input of small operator to do (a mouse click). If you base you backup for DR images you would be a long period of restoration, activation and sequencing and won't get in the majority of cases no where close to the RTO/RPO objectives, you may have set for yourself.

  Hope this helps,

  Lee Dilworth

• SRM - clean after planned migration

  This is likely to sound like a silly question. I'll ask anyway.

  Going to test our plan from Dr. Va recover our VMs to Site B, using migration planned in SRM option. Once recovered and all happy recovery was a success... are there disadvantages to just run the cleanup utility in SRM and then turn on the VMs back to Site without resecure? Know to throw in all the changes

  Or am I better run reprotect?

  Thank you

  Steve

  Steve

  As far as I know, you can run a 'clean' after a trial, not after a planned Migration or a complete restoration. The right way to bring the machines virtual live back on the original Site protected is to make a re - protect. This is a good exercise anyway and you can always do a Test before re - protect.

  I hope this helps!

• Removal of the specifications of customization with Dr.-ip-customizer

  Hello

  I have three scripts of customization in my DR environment:

  

  I would like to get rid of them, because one of the servers no longer exists, and there are two scripts for the other. What I've read, it seems that the removal of the GUI is not a good thing (don't know why), so I tried to use the command 'drop' of the to do.

  So I run the following command to create the. CSV:

  VMware vCenter Site Recovery Manager\bin D:\Program > Dr-ip-customizer - cfg... \config\vmware-Dr.xml - csv d:\prod.csv - cmd generate

  It then creates the. CSV which contains entries for all protected of the VM, but does not list any of the indications for STMTEST. I then changed to remove all the lines containing the entries outside these two virtual machines (so two entries left, one for the shadow-vm-6448 and one for the shadow-vm-11151), and save the file.

  I then ran the customizer again:

  VMware vCenter Site Recovery Manager\bin D:\Program > Dr-ip-customizer - cfg... \config\vmware-Dr.xml - csv cmd d:\prod.csv - drop

  Part of the output includes:

  Deleted CustomizationSpecs out shadow VMs on VC.

  Everything looks good, but my customization scripts are still there.

  I have also tried to manually edit the prod.csv file to add entries manually and re-run the command 'drop '.

  

  Still no joy, the scripts are just going.

  Has anyone encountered this?

  After playing a bit with custom specifications, there are my conclusions:

  1. drop command detaches and removes the custom plug attached to the existing placeholders

  2 drop command deletes the customized specifications that are not attached to any placeholder, but the placeholder with ID and name exists

  3. drop command removes renamed not care or care of non-existent placeholders

  4 command drop do not detach or remove the personalised if you provide a CSV file "base" which was created by 'generate' command. You must provide the CSV file that you use for the command 'create' (with all the properties at the breast).

• Returned to 28 FF because customization is paralyzed in 29 FF. Is there a workaround solutions that allow me to customize the FF29 so that it looks the way I got it with FF28?

  In FF28 everything I needed was on my menu bar. However, FF29 forces a new toolbar on the users - those under the tabs - and will not let me move all that I need off the coast of this new toolbar on the menu bar: the field used for the Show/edit URL is locked to this new toolbar, so I can't move it to the menu bar and then hide the new toolbar.

  Similarly, although it is easy to hide the menu bar, it is not practical to do it because I don't have the option of the first movement everything out of the menu bar on the new toolbar. Anyway FF29 means I'm stuck with two things (menus more new toolbar bar) while FF28 I got by with only one (the menu bar), thus saving valuable space on the screen.

  I attached a picture that shows what my FF28 menu bar looks like, but this form does not provide a way for me to do.

  Restorer Classic theme (Customize Australis)
  
  Restore the tabs squared, appmenu, modules, small display bar icons and more on Australis UI (Windows/MacOSX/Linux + Fx 29 +).

• Shadow copies?

  There is an option in the "Disk Cleanup" where we can also delete old restore the system and "shadow copies".

  What are the "Shadow Copies"? And where are they to be considered. A person may open these files and watch them.

  A person can delete snapshots without removing the system restore points?

  Also:

  How can I open 'Windows Explorer'?

  I can't do it. Always there is the old "Windows Explorer" in Win7?

  I try and all that opens looks that the folder 'My Documents '.

  Is there a 'Run' command to get there?

  The date of your user folder creation (in the Properties tab of cases) usually coincides with the date of installation of the current operating system, if you use a custom / non - OEM (DELL, HP, etc.) build the machine.

  -Or...

  Open the command prompt and type - systeminfo | find/i 'date' (include the quotes).

  Note that if Windows had a "repair" reinstall the date of the repair reinstall, that's what will show,

  as if it were an original 'clean' reinstall, and if the OS was cloned migrated to a new machine it

  will show again that this is the date from the previous machine.

  - Speccy - Standard -try this for the installation date and a whole bunch of other system information.

  -You make a new System Restore point after 'cleaning up' by the 'old', Yes?

  .

• BlackBerry software restore backup after repair

  I sent my BlackBerry Z10 for repair aas the SIM reader was faulty.  Before that, I did a full backup, resulting in a 3.29 GB file against the BlackBerry ID of the handset.  When the handset is returned from repair a new ID had been affected.  So I couldn't do a restore, as the handset ID does not match the ID of backup.  I changed the ID of the handset at the time of the backup, but was not yet able to restore for the same reason.  Is this something to do with the PIN code?  If so, how could change that?  I need to be able to restore the data customization and media.  on my computer the folder is empty, so I hope that this backup of 3.29 GB is on a BlackBerry server in the cloud.

  How to restore from my backup?

  Another thing, BlackBerry link indicates a newer version of the OS being available and yet I have later on the handset.  A screen saying I need to update and another saying the my current is the same as the update available?

  RBOONE wrote:
  Thanks for coming back. How do you do a thorough cleaning of security? I did a factory reset before sending it in for repair.

  Settings > Security > Security Wipe.

• How to designate VM as not critical in 6.1 SRM

  As in earlier versions of SRM, it was possible to designate VMS in recovery site as non-critical, how this can be done in srm 6.1?

  Hello

  Recovery test plan steps step 3 is suspends criticism VMs on recovery site. Right-click on it and you can call the dialog box add the VM not critical. By recovert not necessary step is number 8. See the screenshot.

  Kind regards

  Nik

• Cannot recover replicated VMs

  I have two clusters of vSphere 5.5 to different places and vSphere 5.8 configured replication to replicate VMs from Site A to Site B. replication does not work normally and all virtual machines have a status of OK. I want to move a virtual machine currently in Site A to Site B.

  I tried to follow the instructions below the link to retrieve the virtual machine in question to Site B:

  http://pubs.VMware.com/vSphere-55/index.jsp#com.VMware.vSphere.replication_admin.doc/GUID-356D2357-67A5-42CD-91A7-BDEDDCEDA662.html

  The problem I'm having is that when I right click on any virtual machine on the tab inbound replication to Site B, of "valorisation" is greyed out and I can't select it.

  I run a command 'sync' on the virtual machine, I am trying to recover, and synchronization completed successfully, but which resulted in no change.
  

  I also rebooted vSphere replication device to Site B, but that did not change either.

  I have recovered VMs previously and have not encountered this problem, so this question is a recent development.

  I tried to recover with the Site A virtual machine so turned on and turned off the power and recovery option is grayed out in both cases.
  

  I need help to understand why I can't recover virtual machines.
  

  You use the standalone version of VR, or you have installed top SRM? When replicated with VR VMs are included in SRM protection groups, the Recover option is grayed out in vSphere IU of replication. What is your case?

• Problems with rendering shadows and gradients in folios Android

  Does anyone have experience or solutions on how to solve a problem with damaged feathers, transparency and shadows in the "renditions" Android/folios?

  In the interpretation of the iPad (1024 x 768), there are several frames scrollables, multi-state objects with transparencies and gradients etc. When it is seen on Android devices, if specific rendering of the iPad or Android rendered, it restores transparency, gradients and shadows as a white tone and that he is not rich somehow.

  Is this a known problem or there at - there a way around this?

  Is this problem resolved when you change vector to Raster (or vice versa)?

  Edit: To add a color to this, we have an old bug that we decided to not no difficulty last year titled: "Display of MSO with transparency applied is different with 'Pixelated' and 'Signifying' at the discretion of MSO." Looking at the details of this bug, it seems to be exactly what you are light (whiteness in transparency on vector), so I hope that my question above translates a work around.

  Thank you

  Dave

• After removing a LUN from a host iSCSI it removed itself from VMs, lost?

  Hi all

  I think I need a little help,

  I have an iSCSI SAN DELL MD3000i configured to work with a dell R710 server using vmware iSCSI initiator sw.

  the problem is that when I added another host, it recognized the LUN 2 I created but I wanted to use only one of these LUNS so I deleted from the client vmware one of these data stores and he disappeared also from the dell R710 host and now when I try to add the data still store once it says that I can not recognize the partition table thrpwing an error and tells it to reformat the LUN... but I got VMs in this logic unit number, what can I do to restore the LUNand GET the VMS in return?

  Thanks to you all

  Mattia

  It seems to me that your VM disappeared.  How do you delete your data store? You right-click the Bank and click on delete? It warns you that it will remove all the files associated with the virtual machines on the data store.  At this point, all you can do is reformat the data store.  In the future, you will need to use some type of lun masking on your San to keep your ESX Server to be able to see all your data warehouses.

  I'm sorry.

• Tearing the ESXi and VM live hosts to 4.1 and falling in vCenter environment 5.1

  Hello

  Can I please perform the following before the people here to get opinions on how you think it may be...

  Basically, I'm planning a 5.1 vCenter vCenter 4.1 facility upgrade, but I'm not eager to upgrade in place due to my being uncomfortable with the 4.1 - > 5.1 upgrade instability.

  Instead, I built an environment vSphere fresh 5.1, including:

  SSO
  The inventory service
  UU.
  vCenter
  Web client
  SRM

  And he works with the internal certificates.  SRM has been integrated, data centres have been created, OS customizations are in place, empty clusters have been created with the same level of CVS, licenses have been imported and everything looks good to go.

  The next part is to import all hosts ESXi 4.1 of their existing DRS, HA, cluster EVC, which is also protected by SRM.

  However, the problem is that this must be done without interruption for the hosts or virtual machines running.  All NFS stores running the virtual machine.

  So my plan is:
  Unprotect all SRM protected virtual computer (to remove SRM placeholders in NFS and placeholder VMS in vCenter)
  Reconfigure the deactivation DRS clusters, HA (with CVS)
  Remove the cluster (guests will return to autonomous? VM will continue to operate?)
  'remove' host of the old vmware vcenter
  Add a host new vCenter
  Add the host to the cluster again
  Configure the SRM

  I can see from google, that other people have already done, but this doesn't sound sane?

  I want to avoid at all costs, downtime for the VM to place guests esxi in maintenance mode is not really an option.  So I need to check that the above is possible, and that the removal of the cluster will not stop the running virtual machine or to force some kind of hardware installation/panic on the virtual machine because of the VCA mode not more be applied. The VCA mode would be a big problem trying to admit the host/vm to the new cluster if the virtual machine have re-detected hardware of newer CPU...

  Thanks in advance,
  Rob.

  You don't need to remove clusters or move the hosts off the clusters before you attach them to the new vCenter Server!

  We have made the migration in the past (to a vCenter server to another) without this step and it worked fine.

  In the new vCenter server, you can also directly add hosts to the cluster.

  It works very well... unless you use the distributed switches! It is still possible, but requires additional steps.

  -Andreas

• What happens to the Ip of the server when occurs a migration

  Hello

  If our main site which has 192.168.93.x fails, Manager how to site another site with a 192.168.91.x know that the other site has failed?

  Site manager server has a few heartbeats between the two sites?

  Also even when he missed more to come all the vm on a different subnet with all servers configured with static ip, how vmware is dealing with this situation?

  Or how the site manager which manages?

  > If our main site which has 192.168.93.x fails, Manager how to site another site with a 192.168.91.x know that the other site has failed?  Site manager server has a few heartbeats between the two sites?

  SRM is a heartbeat that ping between sites and fires an event if the connection is lost.  If you do an event alarm, this can trigger an e-mail or a SNMP trap.

  What will not make SRM is to trigger the failover.  Two reasons for that (a) we are not false positives want in a "Split Brain" scenario and (b) DR failover is an important business decision which guarantees a manual opening by a person with appropriate authority.  The recovery itself is composed of hundreds of markets that are automated, AFTER that the person clicks the run button.

  > Also even when he missed more to come all the vm on a different subnet with all servers configured with static ip, how vmware is dealing with this situation?  Or how the site manager which manages?

  SRM will change the IP settings of recovery of the VMs for you at first startup (IP, subnet, gateway, DNS servers).  SRM exporting a spreadsheet that describes all of the information you provide to the networking of the virtual computer.  After completing the worksheet with the correct values for virtual machines when they recover in the second site, you import the worksheet to SRM that creates the customization specifications and are associated with the recovery of the VMs.  When a failover occurs, the IP settings are changed on first boot.  This enables to save the minutes of manual labor by VM - a considerable saving if you are recovering from hundreds of workloads.