With vSphere 5.5 replication disaster recovery test

I have a few virtual machines in our site of DR using a 24-hour RPO.  We will test by recovering virtual machines remotely, without affecting the production of virtual machines on our local site by selecting the option 'recover with the latest available data.  My question is after the replication can I 'pause' instead of 'stop' the task of replication during this test, so that after our test, I can resume the replication tasks?  This would cause a problem?  I don't want something to happen to the production of virtual machines on the side of the source.

Hello

Currently Failover Test + Test cleanup function, without having to make a break or stop replication only works in VR, if using MRS. above it.

RV without SRM, after failover, the only possible option is to stop replication. Perform the failover consolidates replica records in the target data warehouses and prepares the virtual machine configuration files.

Yet after the replication is stopped, you can:

-power off the virtual machine on the recovery after done with the test site

-Remove the vCenter site recovery, leaving records in the target VM data stores

-set up replication again and that it points to the existing disks in the warehouses of data target

Although the UI will display 'Initial full sync', really VR calculates checksums and only changed disk blocks are transferred from the protected site.

Kind regards

Martin

Tags: VMware

Similar Questions

  • Can we create a Vlan without SRM for disaster recovery testing

    We are working on plans for our recovery after disaster in our VMWare environment.  We have a recovery Site which has a NETAPP file server we reproduce our VM data warehouse and SQL data.   We have no RS, but must be able to test if possible disaster recovery with Production upwards.   Is it possible to configure a VLAN and do a test isolated Dr. without SRM?   Thank you

    Welcome to the VMware communities forum.

    You can create a VLAN without SRM.  You will need to properly set up your network hardware, and then you add new virtual machine port groups to your ESXi hosts.  You can then save the virtual machines by giving them a different name and starts in isolation.  When you attempt to save the virtual machines they will always have a reference for the port VM production group so you'll want to make sure you update you turn on.

  • can I add additional VMDK virtual machine that is already protected with vSphere 5.1 replication?

    Hello

    We're uaing SRM 5.1 to protect a virtual computer by using the replication of vSphere. now, we want to increase the size of one of the vmdk dirve. can we increase the size of the disk? and if we don't, then, can we add an another VMDK to this virtual machine?

    What is the procedure to protect that additional newly added VMDK?

    Thank you

    Hello

    Please see the following topics in vSphere replication 5.1 documentation (replication reconfiguration).

    Yes, you can add an another VMDK to a replicated VM. Replication goes into an error state, and you must reconfigure replication and include the newly added to replicate disk.

  • Disaster recovery with replication for VSphere

    Am just test VSphere 5 of replication. with a couple of test VMs

    The replication process works very well

    What I want to know is the process to recover a VM replicated to new hardware in the case of the complete failure of the original host and/or data store

    In essence, disaster recovery.

    Are there other parts (software), that I need to take the replica VMDK and files related to re - create a new virtual machine on a new host

    Steve

    Yes, because it will be all your hard and .vmx files.

  • With vSphere test/recovery replication all while keeping the main site online.

    Hi guys. niot sure if I'm missing something really obvious.

    From what I can understand tha base "recovery process" in vSphere Replication5.1 implies the following workflow

    However, our profession demands that we test the ability to recover the VMs selected the site of DR then than DO NOT impact main site.

    Is this possible without SRM / table to database replication / replication of VEEAM?

    Our installation program

    VCenter PROD (dedicated VLAN x)

    VR PROD device (including VLAN, dedicated)

    PROD-HA and DRS Cluster

    Guest PROD networking (VLAN z)

    DR VCenter (dedicated Vlan X)

    VR PROD device (including VLAN, dedicated)

    PROD-HA and DRS Cluster

    PROD comments Networking (VLAN, isolated, cannot drive to the main site)

    No RS and no possibility to use the replication table according to preverred, no Budget for VEEAM replciation.

    MUST BE DONE, while the primary site remains fully alive >

    Basic procedure to test recovery to DR and come back if I understand correctly >

    1 tasks replication setup (fact)

    2 access to the web in VCENTER DR > Pause/Stop replication on the virtual machines, we want to retrieve.

    3 web access in VCENTER DR > retrieve DR virtual machines using 'recover with the latest changes' (Show stop as primary/Source VM needs to go down)

    3 assuming that it is a path last step 3, we intend to move guests picked up at DR VLAN, one port groups and reconfigure the Ips using Powershell process mass

    4 active Directory and DNS will be changed to Dr. TEST Site to make usable salvaged customers.

    test to DR on revovered VMs in DR VLan 5 users, so this should be route back or affect the site of PROD.

    6 not recovered VMs to the main site. This required once more primal VMs being to low or EVEN be removed from the inventory!

    Procedure here

    VMware vSphere 5.1

    Looks like so there is no way to use vSphere replication to TEST the abilty to toggle, unless you can share the secrets with me.

    If you are using vSphere replication without SRM above it, recovery Test is not available. The process, you can follow in case you do not want your main Web site:

    (1) perform a recovery using the second option (retrieve by using the latest available data). In this way you will not have to power off of the VMs source and your main site will be online.

    (2) when the recovery is complete, stop the replications (which will be in a State of recovery)

    (3) power off VMs recovered, unsubscribe them inventory of VC, but keep the files of disk intact.

    (4) manually configure all repetitions using disks that have been left in the form of initial seeds. This will cause the changes to synchronize.

    In step 4 of ease, you can use the multi-vm replication configuration wizard vSphere. Just make sure that the data store target each disk that will be used as initial copy is put in the folder with the name of the virtual computer. Then, you could try to configure all virtual machines at once, performing the search of seeds and confirming to use.

  • vCloud Air Disaster Recovery - vSphere replication of specific records

    In the most recent documentation for vSphere replication, the ability to select specific disks when you replicate a single workload is described:

    Documentation Centre of vSphere 5.5

    However, in the videos of vCloud Air DR, this option is not currently available. Is - this specific to Air DR vCloud or some videos of previous versions?

    vCloud Air Disaster Recovery: configuration of the Virtual Machine replication - YouTube

    Answer: No.

    http://vjourneyman.com/replicating-to-vCloud-air-Dr

  • In vSphere 5.5 replication recovery scenario

    Hi guys,.

    I use vSphere replication device 5.5 (no SRM). I came across the following during my recovery problem VM;

    I have reproduced a VM of the target Site-2 Site-1 test. The replication went well through "Complete initial synchronization" and then the status changed to OK green. RPO has been set at 15 minutes.


    To call the DR on the target Site-2 site, I deleted the virtual Test on Site-1 machine. The issue began as soon as I deleted VM on Ste - 1. He also stopped replication and also removed from the warehouses of data in both Sites.

    This does not seem right to me... The replicated data (vmdk files) must not be removed by deleting the virtual machine from source Site. If removal of VM also remove the replicated date, there is no point Dr.

    Can someone help me please.

    Concerning

    Hello

    It's behavior in all editions of vSphere replication, but it may be surprising.

    If there is connectivity between the two sites and the VM source is removed from the vCenter inventory (or transitively - cluster/host on which the virtual computer runs is removed from the vCenter inventory), vSphere replication automatically cleans everything related to replication on both sites. If initial seeds had been used during replication has been configured, then the site basic disks target will not be deleted.

    If the source virtual machine disks are lost, or disaster comes the source host or the entire source, but source VM site is not removed the vCenter inventory, vSphere replication will not affect not the data on the target site replication and recovery activity can be performed.

    Kind regards

    Martin

  • Problem with different ASM disaster recovery start - new

    Hello together,

    I had an old net here about it but now will not solve the problem with the points in the old thread. Here's the old: https://community.oracle.com/thread/3608049?start=0 & tstart = 0

    I'm doing a disaster recovery with the 'apex11A' on a new server database, which has an another ASM starts. The old man starts is '+ DGA112_1' and '+ FRA112_1', newcomers are called '+ DATA_QUM169' and '+ FRA_QUM169 '. I changed the settings in the spfile restored by writing in a pfile file and creating the spfile from pfile.

    I tried in several ways. First lay the new ASM with RMAN to the course:

    run
{
SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

    Then I tried it in RMAN by defining the new ASM for each data file:

    run
{
SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

    Then I tried the bot in one:

    run
{
SET NEWNAME FOR DATABASE TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 1 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 2 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 3 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 4 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 5 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 6 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 7 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 8 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 9 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 10 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 11 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 12 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 13 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 14 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 15 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 16 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 17 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 18 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 19 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 20 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 21 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 22 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 23 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 24 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 25 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 26 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 27 TO '+DATA_QUM169';
SET NEWNAME FOR DATAFILE 28 TO '+DATA_QUM169';
restore database until LOGSEQ 24286;
switch datafile all;
switch tempfile all;
recover database until LOGSEQ 24286;
}

    Whenever I get one

    Starting restore at 03-FEB-16
using channel ORA_DISK_1


creating datafile file number=1 name=+DATA_QUM169
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 02/03/2016 16:20:41
ORA-01180: can not create datafile 1
ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'

    The backuppiece which I bring are correctly defined with

    RMAN> catalog backuppiece '/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1', '/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1';


cataloged backup piece
backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1 RECID=3779 STAMP=902851052
cataloged backup piece
backup piece handle=/usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1 RECID=3780 STAMP=902851052


RMAN> list backup;




List of Backup Sets
===================




BS Key  Size       Device Type Elapsed Time Completion Time
------- ---------- ----------- ------------ ---------------
3779    52.61M     DISK        00:00:00     03-FEB-16
        BP Key: 3779   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145340
        Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m4qt0mnk_1_1


  List of Archived Logs in backup set 3779
  Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
  ---- ------- ---------- --------- ---------- ---------
  1    24285   11073415926066 03-FEB-16 11073416327345 03-FEB-16
  1    24286   11073416327345 03-FEB-16 11073416678326 03-FEB-16


BS Key  Type LV Size       Device Type Elapsed Time Completion Time
------- ---- -- ---------- ----------- ------------ ---------------
3780    Full    813.86M    DISK        00:00:00     03-FEB-16
        BP Key: 3780   Status: AVAILABLE  Compressed: YES  Tag: TAG20160203T145042
        Piece Name: /usr/local/oracle/product/11.2.0.4/dbs/m3qt0mi2_1_1
  List of Datafiles in backup set 3780
  File LV Type Ckp SCN    Ckp Time  Name
  ---- -- ---- ---------- --------- ----
  1       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/system.1423.788355253
  2       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/sysaux.1422.788355259
  3       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/undotbs1.1359.788355263
  4       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/users.1362.788355273
  5       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4.1369.788356305
  6       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex4_files.1366.788356317
  7       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms_archiv.1358.788357229
  8       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/planwerte.1357.788357243
  9       Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_prod.1352.788456613
  10      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais.1353.788456763
  11      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mms.1354.788456995
  12      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/externe_wirk.1355.788457525
  13      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2mt.1356.788458151
  14      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/btdb_read.1351.788458291
  15      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329
  16      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657
  17      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/macmon.1340.788458691
  18      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais_read.1339.788458725
  19      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/mais2srm.266.788458799
  20      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859
  21      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/quickcheck.1338.788458887
  22      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/switch.1337.788459139
  23      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/veit_r.1333.788459167
  24      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/test-btdb.1298.795097725
  25      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11dev.986.874230931
  26      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/apex11devbt.985.874230963
  27      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/hrbew.1083.851007823
  28      Full 11073416676796 03-FEB-16 +DGA112_1/apex11a/datafile/optimadata.1032.865951029

    I also tried to put the new ASM SQL:

    SQL*Plus: Release 11.2.0.4.0 Production on Wed Feb 3 16:04:05 2016


Copyright (c) 1982, 2013, Oracle.  All rights reserved.




Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Automatic Storage Management and OLAP options


SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/system.1423.788355253' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 1 - new file '+DATA_QUM169' not found
ORA-01110: data file 1: '+DGA112_1/apex11a/datafile/system.1423.788355253'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/sysaux.1422.788355259' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 2 - new file '+DATA_QUM169' not found
ORA-01110: data file 2: '+DGA112_1/apex11a/datafile/sysaux.1422.788355259'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 3 - new file '+DATA_QUM169' not found
ORA-01110: data file 3: '+DGA112_1/apex11a/datafile/undotbs1.1359.788355263'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/users.1362.788355273' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 4 - new file '+DATA_QUM169' not found
ORA-01110: data file 4: '+DGA112_1/apex11a/datafile/users.1362.788355273'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4.1369.788356305' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 5 - new file '+DATA_QUM169' not found
ORA-01110: data file 5: '+DGA112_1/apex11a/datafile/apex4.1369.788356305'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 6 - new file '+DATA_QUM169' not found
ORA-01110: data file 6: '+DGA112_1/apex11a/datafile/apex4_files.1366.788356317'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 7 - new file '+DATA_QUM169' not found
ORA-01110: data file 7: '+DGA112_1/apex11a/datafile/mms_archiv.1358.788357229'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/planwerte.1357.788357243' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 8 - new file '+DATA_QUM169' not found
ORA-01110: data file 8: '+DGA112_1/apex11a/datafile/planwerte.1357.788357243'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 9 - new file '+DATA_QUM169' not found
ORA-01110: data file 9: '+DGA112_1/apex11a/datafile/btdb_prod.1352.788456613'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais.1353.788456763' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 10 - new file '+DATA_QUM169' not found
ORA-01110: data file 10: '+DGA112_1/apex11a/datafile/mais.1353.788456763'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mms.1354.788456995' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 11 - new file '+DATA_QUM169' not found
ORA-01110: data file 11: '+DGA112_1/apex11a/datafile/mms.1354.788456995'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 12 - new file '+DATA_QUM169' not found
ORA-01110: data file 12:
'+DGA112_1/apex11a/datafile/externe_wirk.1355.788457525'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 13 - new file '+DATA_QUM169' not found
ORA-01110: data file 13: '+DGA112_1/apex11a/datafile/mais2mt.1356.788458151'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 14 - new file '+DATA_QUM169' not found
ORA-01110: data file 14: '+DGA112_1/apex11a/datafile/btdb_read.1351.788458291'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 15 - new file '+DATA_QUM169' not found
ORA-01110: data file 15: '+DGA112_1/apex11a/datafile/hwdb2acs.1343.788458329'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 16 - new file '+DATA_QUM169' not found
ORA-01110: data file 16: '+DGA112_1/apex11a/datafile/hwdb2sccm.1341.788458657'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/macmon.1340.788458691' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 17 - new file '+DATA_QUM169' not found
ORA-01110: data file 17: '+DGA112_1/apex11a/datafile/macmon.1340.788458691'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais_read.1339.788458725' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 18 - new file '+DATA_QUM169' not found
ORA-01110: data file 18: '+DGA112_1/apex11a/datafile/mais_read.1339.788458725'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/mais2srm.266.788458799' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 19 - new file '+DATA_QUM169' not found
ORA-01110: data file 19: '+DGA112_1/apex11a/datafile/mais2srm.266.788458799'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 20 - new file '+DATA_QUM169' not found
ORA-01110: data file 20:
'+DGA112_1/apex11a/datafile/outdating_sap_user.267.788458859'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 21 - new file '+DATA_QUM169' not found
ORA-01110: data file 21: '+DGA112_1/apex11a/datafile/quickcheck.1338.788458887'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/switch.1337.788459139' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 22 - new file '+DATA_QUM169' not found
ORA-01110: data file 22: '+DGA112_1/apex11a/datafile/switch.1337.788459139'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/veit_r.1333.788459167' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 23 - new file '+DATA_QUM169' not found
ORA-01110: data file 23: '+DGA112_1/apex11a/datafile/veit_r.1333.788459167'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 24 - new file '+DATA_QUM169' not found
ORA-01110: data file 24: '+DGA112_1/apex11a/datafile/test-btdb.1298.795097725'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11dev.986.874230931' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 25 - new file '+DATA_QUM169' not found
ORA-01110: data file 25: '+DGA112_1/apex11a/datafile/apex11dev.986.874230931'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 26 - new file '+DATA_QUM169' not found
ORA-01110: data file 26: '+DGA112_1/apex11a/datafile/apex11devbt.985.874230963'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/hrbew.1083.851007823' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 27 - new file '+DATA_QUM169' not found
ORA-01110: data file 27: '+DGA112_1/apex11a/datafile/hrbew.1083.851007823'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form




SYS@apex11A> ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169';
ALTER DATABASE RENAME FILE '+DGA112_1/apex11a/datafile/optimadata.1032.865951029' TO '+DATA_QUM169'
*
ERROR at line 1:
ORA-01511: error in renaming log/data files
ORA-01141: error renaming data file 28 - new file '+DATA_QUM169' not found
ORA-01110: data file 28: '+DGA112_1/apex11a/datafile/optimadata.1032.865951029'
ORA-17503: ksfdopn:2 Failed to open file +DATA_QUM169
ORA-15045: ASM file name '+DATA_QUM169' is not in reference form

    But my new database will not set the new ASM and I have no why.

    The db_create_file_dest parameter is set correctly, so I think that:

    NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_create_file_dest                  string      +DATA_QUM169

    I forgot something? Would be nice to get help ...

    A big thank you and best regards,

    David

    Your data checkpoint SCN file are in the LOW and HIGH range of the SNA for SEQUENCE 24286.

    Therefore, your UNTIL clause should be 24287 SEQUENCE up to THAT.

    Hemant K Collette

  • I have a compaq presario cq60 with vista which was able to start after the installation of windows updates. HP recovery failed with error code 100a and bios self-test gave error fail #1-07. What can I do?

    I have a compaq presario cq60 with vista. Could not start after the installation of windows updates. HP recovery failed with error code 100a and bios self-test gave error fail #1-07. I took the hard drive and installed in my office. Windows Explorer displays the main and recovery partitions.

    The primary partition has the following folders (including hidden & system)

    The recovery partition has the following (including the language files more)

    Someone at - it ideas why my laptop does not work?

    Thank you

    Greg

    Hello

    You press F11 on startup with a HP Compaq to start the recovery process.

    For problems with the recovery process, you will need to contact HP.

    BIOS problems:

    There are messages for the HP Forums for posters with similar errors:

    http://h30499.www3.HP.com/T5/notebook-HP-ProBook-EliteBook/notebook-HDD-problems-TEst-status-1-07-fail/TD-p/658902

    http://h30499.www3.HP.com/T5/notebook-PCs-pavilions-Presario/HP-Pavilion-dv8000-getting-1-07-fail-error/TD-p/883284

    http://h30499.www3.HP.com/T5/notebook-PCs-pavilions-Presario/HP-Pavilion-notebook-dv6000-1-07-fail/TD-p/1069457

    All the answers it point to a drive about to fail

    See you soon.

  • VSphere 6.0 backward compatible with vCenter 5.5 replication is?

    At one point, the vSphere replication 6.0 compatibility matrix said that it is compatible with vCenter 5.5.  I think it was around mid-March.  Now, he seems to have changed and says vSphere 6.0 replication is only compatible with vCenter 6.0.  Is this true?  Are there plans to make vSphere replication 6.0 backward compatible with vCenter 5.5?

    Bill,

    A decision was made not to support backward compatibility between replication 6.0 vSphere and vCenter Server 5.5 going forward.  This is the result extended and careful considerations affecting the provision of quality and consistent user experience for our customers using vSphere 6.0 replication.

    Thus, vSphere 6.0 replication is officially supported with vCenter Server 6.0 only (SSO 6.0, 6.0 PC, Web Client 6.0).  This resulted therefore in the interoperability of public VMware product matrix.

  • Problems with vSphere replication

    Hello

    Ive been with vSphere for about a week now and I'm faced with the logic of the replication tool V.

    I've been creeping (don't not trolling) forums and web trying to find a good source that can explain this plugin which is visible in my Web client installation method. I also license MORE.

    This is probably the only one I can find so far: -.

    http://vknowledge.NET/2012/09/12/vSphere-5-1-getting-started-with-vSphere-replication-5-1/

    What I want to achieve is to reproduce all the virtual machines on one of my servers to another identical server of the G8.

    Two questions if you could help please?

    1. someone any good tutorials on it.

    2. I went and made a schoolboy error, I think, I gave the vSphere replicaiton appliance the same IP address as my ESXi host. (This is how I am wrong) and now I can not access the host because of this machine. Can someone tell me how I can reconnect to this machine without a comprehensive resettlement and reconstruction of 50 guests or more.

    Thanks in advance if you can help.

    It is difficult to explain the internel operation of the SRM, vsphere replication etc... in this little time...

    the basics are simple... How it works... ?

    There are 2 types of replication replication 1-vsphere 2-array based replication

    vpshere replication is a basic agent - it's a VR agent will be there inside the esxi hosts this monitor of the agent running the virtual machine inside this host and replicates data binding if WAN remote site.

    the main PR\648606FR here is - once the replication of the entire virtual machine that's happened, after that only the blocks changed the VMFS will be launched on the... which is the only the modified virtual machine data will be replicated. It's called CBT, VR agent follows the blocks inside the VMFS, if any block of virtual machine data is changed it will get replicated.

    dosent it replication vsphere require no support from the underlying storage Bay...

    the second is the table of a function... where the entire replication is managed by the matrix of storage... and it works with the MRS.

    See the post for more details... http://communities.VMware.com/message/2175005#2175005

    now to your questions.

    1. someone any good tutorials on it. -the best method is to read the official docs...

    http://www.VMware.com/files/PDF/Techpaper/introduction-to-vSphere-replication.PDF

    http://blogs.VMware.com/vSphere/2012/08/SRM-5-1-and-vSphere-replication-as-a-standalone-feature.html

    http://www.yellow-bricks.com/2012/09/17/back-to-basics-install-configure-and-use-vSphere-replication/

    http://thesaffageek.co.UK/2012/08/27/vSphere-5-1-announced-with-enhanced-vSphere-replication/

    2. I went and made a schoolboy error, I think, I gave the vSphere replicaiton appliance the same IP address as my ESXi host. (This is how I am wrong) and now I can not access the host because of this machine. Can someone tell me how I can reconnect to this machine without a comprehensive resettlement and reconstruction of 50 guests or more.

    If the esx host is clustered, using the ILO and esxi shell put the host in maintenance... mode and reset the esxi

    To switch to maintenance mode, run the following command

    VMware-vim-cmd/hostsvc/maintenance_mode_enter

    and

    To exit the maintenance mode, run the following command

    VMware-vim-cmd/hostsvc/maintenance_mode_exit

    then restart the esxi host and give IP, or power off of the VR device and give IP

  • Requirements for vSphere remote site replication

    I run 3 Enterprise 5.5 x vSphere hosts in A Site with vCenter.   I want to add a new host in a remote site and configure vSphere replication between them.  Issues related to the:

    • Do I need to vCenter in slot 2?
    • If vCenter Site of A is the Site management and hosts of the Site B and Site A goes down, vSphere replicated VMs can be restarted to Site B without problem?
    • Is there a risk to not have a vCenter dedicated to Site B on the changeover plan?

    Thank you

    -Matt

    Hello

    (A) If you have vCenter in slot 2, you will need to deploy device VR and match two VR UI sites.

    In the case where something happens to site A, losing vCenter and/or VR device, you can use vCenter and VR device to site B to perform a recovery after disaster and put in place the VMS to site B, inside of vCenter inventory B.

    (B) If you have no server vCenter in slot 2:

    1. There is no need to deploy handset unit of VR (embedded DB for server VRMS + VR + VRMS) for site B.

    2. you can deploy additional device VR-server only for site B, so that the replication traffic goes directly from the source ESXi to the correct server in VR.

    3. If the disaster arrives at the site, you must have vCenter Server and VRM in the combined unit of VR upward and running order to use the VR UI to perform a disaster recovery. If vCenter Server or VRMS manage warehouses of data target is corrupted/lost, the only way to recover after a disaster is to consolidate recovery replica logs manually rename and replicated configuration files and hope that consolidated records represent a coherent source VM instance. This procedure is subject, not officially supported, and care must be taken when building the redo logs, in order to ensure the consistency of the data in the disks of the virtual machine, not some partial block updates.

    Kind regards

    Martin

  • error recovery testing

    Hello!

    Docs on SRM 6:

    of the installation guide

    If you use replication of vSphere, do not select a placeholder data store that you already use

    as the target for replication data store.

    of the Administrator's guide:

    The replicavirtual of the machine as vSphere, replication creates and the placeholder virtual machine that

    Site Recovery Manager creates the two may reside on the same data store on the recovering site because they are

    created in different data store files. When VMS reply and the placeholder is in the same

    data store, Site Recovery Manager creates the machine name of virtual space by using the virtual replica

    the name of the machine with the suffix (1). Site Recovery Manager applies the mappings of the inventory to the

    placeholder virtual machine on the recovering site.

    so, I guess the best practice is mentioned in the installation guide

    Yes, you can examine the suggestion in the installation as "Best practice" guide Using the same data store for fictional settings and replication target is supported, but may create confusion with several folders that are created for the same VM.

    Best regards

    Stefan Tsonev

  • Physical-TO-virtual disaster recovery

    Hi, what would you do in this scenario?

    • A heterogeneous set of physical servers (with Linux or Win) owned and operated by several customers in different locations.

    • A vSphere on a centralized site infrastructure.

    I wish I had in my infrastructure, a VM power off to each of the remote servers in physics and to keep the image of VM in phase with the remote disks.

    In the case of a remote site explodes, the corresponding virtual machines are started (automatically or manually) as a quick and effective disaster recovery solution...

    Forget the problems of network/IP of this scenario, is there a way or a 3rd party software to keep a VM'd synch with a remote server physical?

    Thank you!

    PlateSpin Protect will be repeated. You place the platespin on the physical server agent and you can replicate the server to an image file or a virtual machine. You can update the image or VM file on a regular basis. It comes from platespin powerrecon product.

    Check it out.

    http://www.PlateSpin.com/products/protect/

    Don't forget to leave some points for messages useful/correct.

  • OBIEE Disaster Recovery can be configured without CARS and shared storage?

    Hi people,

    As say the topic, I'm looking for advice on disaster recovery. What I find in the docs pointing me to the high availability configuration, or maybe I'm simply not find the docs I'm looking for. And it always points to the RAC, etc. of shared storage. My database is already configured to Dataguard and I want to do things this way, with a recovery site which isn't always upwards and a part of a cluster (although it's very well as long as the CAR is not involved), I'm looking for some feedback on how people do things. I have 11.1 now, but will be upgrading to 12.2 soon.  Just a straight stitch to the documentation would be useful if I'm missing just that.

    Thank you

    -Adam

    Since you have already configured Dataguard and in a DR situation, you will be switching/switch on your course in standby mode and it will active db. All this is fine. You can do the same with instances of weblogic OBIEE. You can clone your binaries installed using tools provided by Oracle cloning, or build binaries from weblogic with the accurate determination of drive on your Dr. use the pack of weblogic server and then unzip tool to archive your entire weblogic domain and it Unarchive in your prepared DR server.

    Now, you have to just challenge the hostname (s) of your domain to point to your database JDBC data sources and weblogic.

    To facilitate the task, you can change the host name used by weblogic to host alias that can be remapped in DNS during DR. Similarly, you can change the JDBC connection string so that it can automatically select the active database as long as you use a database instead of a SID service name in the connection string.

    You will need to regularly make a pack on your weblogic domain in order to maintain an up-to-date backup of your domain proximity. Similarly, if you have reports that are stored on the file system, they must also be backed up regularly so that they can be restored.

Maybe you are looking for

  • G7 Pavilion: Pavilion g7 won't boot afyer routinr 8.1 update

    I can't start my conputer, I was prompted to restart for the installation of the update and now stuck on a white background screen of purplr.  I need to keep my posting attached external display, my screen is broken on my computer laptop andhas Bern

  • How to find the location of a bookmark.

    Sometimes, they are transferred somehow. If I get the name I gave the bookmark, it rises, but does not tell me when it is filed, my many bookmark folders, so I can bring it back here where they. This can happen to a folder and can take FOREVER to fin

  • disabled user continues to appear at the beginning

    Hello I recently installed the operating system after replacing the hard drive, so the installation was completely new to using the Internet.  Every time turn on the laptop, I get the user to choose two: Mine and comments. I went into the menu in sys

  • Need driver for on Equium A100-549 sm bus controller

    I need a file to install the sm bus controller Please help, im using XP SP2, I don't have my original disc I lost when I moved it, used a XP disc base with my serial number, all happened in execpt the sm bus controller and WIFI doesn't connect, there

  • creation of polynomial

    Hi all I'm working on a VI and I'm stuck. How can I create a second order polynomial in general Ax ^ 2 + Bx + C, being able to use A, B, and C in the form of controls on the front panel. Sorry, this may sound simple for the most part, as I am a newbi