To achieve High availability, we are installing Sybase Replication server on NAS drive shared by two servers. We can start and stop Replication server from node1 from where we have installed binaries but cannot start it from other node2 where NAS drive is shared. Howeve, we can access replication server through isql from both the node.
In logs it shows, that embedded sybase database ERSSD is not starting from other node.
Best Regards
Related
I'm beginning to think this is not possible but I have to ask. I have a Windows Server 2012R2 Datacenter server acting as a PDC and I have the Hyper-V role installed. This server has 15T of disk space but not a lot of CPU or RAM. I want to use it as a disk drive storage server for my VM Guest drives.
I also have a Server 2019 Core server that has more CPU power and 32G of RAM, but very little storage space. I want to use this server as my VM host machine, but I want to build all the storage on the 2012R2 server, but everything I have tried has failed. As expected, I can create VM guests if both the machine and disk is on this server, but if I try to create the disk on the other server it fails with an error similar to "Failed to create the virtual hard disk".
Is it just not possible to create the guest machine and disk on separate servers? Is this because of the 2012R2 and 2019 server differences? Is it possible and I just don't have the disk share setup properly?
Hyper-V is all new to me, it is a learning lab and I have a lot to learn. I've spent hours reading and going through articles but I just haven't found what I'm looking for yet. I think it's time I reach out to the experts and see it it is even possible first.
Thanks,
Tom
I can successfully create a guest if both the guest machine and disk are on the Host. When I try to create the disk on a a different host, I get the "Failed to create the virtual hard disk" error. I'm trying to maximize the use of the resources I have by splitting CPU/RAM on one host and Disk on another, but I am beginning to think it is not possible.
We are using SQL Server replication using RMO. We have SQL 2016 (Standard Edition) on the server acting as the publisher and SQL Server Express Edition as the subscriber.
Previously, the distributor and the publisher were on the same server and the replication was working.
We have a client application, the data needs to be synced with the server on a regular basis.
We have Transactional and merger replication set and rely on pull approach where the client application pulls the data on demand.
For security reasons, the client doesn't want to expose port 1433 (or any other port) on the publisher to the subscribers.
So, we decided to move the distributor on a remote server, so that the subscriber talks to the publisher via remote distributor. (The remote distributor can connect and talk to the Publisher.) However, I am getting an error when I try to sync.
Wanted to check if replication is possible when port 1433 is blocked for the subscribers?
If yes, can you provide me some sample code or pointers to it. If no, what are the different options that I can have?
I need help with this problems discussed as follows:
I have created Gen-1 Hyper-VM on Windows 10 Pro 64 and it is networked and shows all host PC and can connect to internet.
I installed SQL Server R2 on it with the idea of connecting to
databases residing on one of host partitioned (SSD)
I then configured that host PC partition drive with SQL databases on
it as Virtual Drive successfully and I tested it both way
communication successfully. (Figure-1)
Now, when I try to attach the database from VM to that drive, SQL
server does not show that drive in the list of drives (Figure-2)
I am scratching my head as to what am I missing here. I would appreciate any suggestion here.
Why do we need Azure site recovery when we have azure storage replication? One point that I understood is that you can manually failover in case of azure site recovery. Doesn't Azure storage replication replicate all kind of data including VHD?
Thanks In Advance
Azure Storage Replication: It is specifically for Azure Storage (data stored on storage) E.g vhds), it copies your data so that it is protected from planned and unplanned events ranging from transient hardware failures, network or power outages, massive natural disasters, and so on. You can choose to replicate your data within the same data center, across zonal data centers within the same region, and even across regions.
Whereas Azure Site Recovery contributes to your business continuity and disaster recovery (BCDR) strategy, by orchestrating and automating replication of Azure VMs between regions, on-premises virtual machines and physical servers to Azure, and on-premises machines to a secondary datacenter.
What can Site Recovery protect?
Azure VMs: Site Recovery can replicate any workload running on a
supported Azure VM.
Hyper-V virtual machines: Site Recovery can protect any workload
running on a Hyper-V VM.
Physical servers: Site Recovery can protect physical servers running
Windows or Linux.
VMware virtual machines: Site Recovery can protect any workload
running in a VMware VM.
What workloads can I protect with Site Recovery?
You can use Site Recovery to protect most workloads running on a supported VM or physical server. Site Recovery provides support for application-aware replication, so that apps can be recovered to an intelligent state. It integrates with Microsoft applications such as SharePoint, Exchange, Dynamics, SQL Server and Active Directory, and works closely with leading vendors, including Oracle, SAP, IBM and Red Hat. Learn more about workload protection.
Reference: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-faq
I have very limited access to the SQL Server at my ISP.
I have a very simple tool to create databases and execute SQL (which is enough most of the time) but now I also want to backup (and in the case of an accident, restore) a database from my own PC (or via a web application, if that's possible, both are ok)
Is there a tool which can do that auotmatically?
It's a SQL Server 2008 database.
I guess I can do it from my SQL Server Management Studio, but I'd prefer a tool that can do it scheduled.
Kind regards,
Michel
You can only backup (and restore) your database from local drives on the SQL Server machine - e.g. the machine at your ISP's location.
You cannot backup SQL Server and store the *.bak file on your local system, over the internet.
So what you need to do is create some kind of a process that stores the BAK file on the server machine at your ISP's location, and then copies or moves it to your home machine. For that, you need to have write access to some physical drive at your ISP on their SQL Server.