https://community.hpe.com/t5/hpe-simplivity/simplivity-vm-backup-replication-failure/m-p/7020149#M107 <P>Thanks! for your help!</P><P>&nbsp;</P> Mon, 01 Oct 2018 14:10:12 GMT werner.zeller 2018-10-01T14:10:12Z https://community.hpe.com/t5/hpe-simplivity/simplivity-vm-backup-replication-failure/m-p/7017161#M95 <P>Hi,</P><P>can it be if the the name of the datastore is renamed that the backup is not more working?</P><P>&nbsp;</P><P>Thanks!</P><P>regards</P> Wed, 05 Sep 2018 14:29:59 GMT https://community.hpe.com/t5/hpe-simplivity/simplivity-vm-backup-replication-failure/m-p/7017161#M95 werner.zeller 2018-09-05T14:29:59Z https://community.hpe.com/t5/hpe-simplivity/simplivity-vm-backup-replication-failure/m-p/7017243#M96 <P>Hi <a href="https://community.hpe.com/t5/user/viewprofilepage/user-id/1158747">@werner.zeller</a>,</P><P>When you are defining backups, you are actually directing them to a cluster, not a datastore. The way to think about it is that backups work at the layer below vCenter and therefore below the datastore, i.e. they are point-to-point between one OVC and another.</P><P>In this case it sounds like you may be having a network issue. Are all backups from the same source affected, or to the same destination for example? Either way, I would suggest that a support case is your best course of action here and we will sort this out for you.</P><P>Thanks,</P><P>Scott</P> Thu, 06 Sep 2018 05:59:57 GMT https://community.hpe.com/t5/hpe-simplivity/simplivity-vm-backup-replication-failure/m-p/7017243#M96 scott_svt 2018-09-06T05:59:57Z https://community.hpe.com/t5/hpe-simplivity/simplivity-vm-backup-replication-failure/m-p/7020149#M107 <P>Thanks! for your help!</P><P>&nbsp;</P> Mon, 01 Oct 2018 14:10:12 GMT https://community.hpe.com/t5/hpe-simplivity/simplivity-vm-backup-replication-failure/m-p/7020149#M107 werner.zeller 2018-10-01T14:10:12Z