Looking for UniData expertise in deploying and optimizing storage performance in Azure. I have not found any official Rocket technical documentation to support.
------------------------------
Ralpha Labarta
CTO
Engage PEO
St. Petersburg FL US
------------------------------
Page 1 / 1
Looking for UniData expertise in deploying and optimizing storage performance in Azure. I have not found any official Rocket technical documentation to support.
------------------------------
Ralpha Labarta
CTO
Engage PEO
St. Petersburg FL US
------------------------------
------------------------------
Ralpha Labarta
CTO
Engage PEO
St. Petersburg FL US
------------------------------
------------------------------
L Iveblues
Retired
Rocket Forum Shared Account
------------------------------
Looking for UniData expertise in deploying and optimizing storage performance in Azure. I have not found any official Rocket technical documentation to support.
------------------------------
Ralpha Labarta
CTO
Engage PEO
St. Petersburg FL US
------------------------------
------------------------------
Ralpha Labarta
CTO
Engage PEO
St. Petersburg FL US
------------------------------
- Inside the VM it's the same as a standalone server.
- Optimise the disk subsystem for a large volume of small random accessed data rather than a small volume of large streamed data.
- Benchmark and manage the cost of the required IOPS
See:
- https://azure.microsoft.com/en-us/products/storage/disks/ - I recommend looking under NoSQL databases as a start,
- https://learn.microsoft.com/en-gb/azure/virtual-machines/disks-performance
- https://learn.microsoft.com/en-gb/azure/virtual-machines/disks-types
You don't mention whether a 'green screen', SB/XA or RESTful-service based application - each has its own connectivity and persistence requirments.
And for general VM usage - whoever the supplier:
- Check the backup and failover strategies
- If taking snapshots, please pause the database for the snapshot duration to ensure database integrity,
- Consider using RFS for resilience and warmstart recovery in the event of a forced switchover to another zone. Ideally with transaction semantics,
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
We are heading down the same path. I will be keeping an eye on this thread.
------------------------------
L Iveblues
Retired
Rocket Forum Shared Account
------------------------------
------------------------------
L Iveblues
Retired
Rocket Forum Shared Account
------------------------------
------------------------------
Barry Green
Director
CAPITOL BUSINESS SERVICES
Mawson Lakes SA AU
------------------------------
We are also looking at this, we run Unidata with SB+ and SBClient in GUI mode.
------------------------------
Barry Green
Director
CAPITOL BUSINESS SERVICES
Mawson Lakes SA AU
------------------------------
------------------------------
Barry Green
Director
CAPITOL BUSINESS SERVICES
Mawson Lakes SA AU
------------------------------
In both CUI and GUI mode, SB_ is effectively a 'green screen' (i.e. telnet-based) application. You might want to consider running SBClient in a Terminal Server environment and using low cost PCs to access the TS environment. Optionally the TS could be cloud-based as well, though please remember to benchmark and factor in the cloud residency, failover strategy and IOPS of the TS itself if considering this option,
Also - don't forget to secure and encrypt your cloud server access, you would be amazed how many cloud-based servers have been left without basic protections.
Regards
JJ
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
I can offer general guidelines if of help?
See:
You don't mention whether a 'green screen', SB/XA or RESTful-service based application - each has its own connectivity and persistence requirments.
And for general VM usage - whoever the supplier:
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
- Inside the VM it's the same as a standalone server.
- Optimise the disk subsystem for a large volume of small random accessed data rather than a small volume of large streamed data.
- Benchmark and manage the cost of the required IOPS
See:
- https://azure.microsoft.com/en-us/products/storage/disks/ - I recommend looking under NoSQL databases as a start,
- https://learn.microsoft.com/en-gb/azure/virtual-machines/disks-performance
- https://learn.microsoft.com/en-gb/azure/virtual-machines/disks-types
You don't mention whether a 'green screen', SB/XA or RESTful-service based application - each has its own connectivity and persistence requirments.
And for general VM usage - whoever the supplier:
- Check the backup and failover strategies
- If taking snapshots, please pause the database for the snapshot duration to ensure database integrity,
- Consider using RFS for resilience and warmstart recovery in the event of a forced switchover to another zone. Ideally with transaction semantics,
------------------------------
John Jenkins
Thame, Oxfordshire
------------------------------
For those going down the same road, the most challenging element has been performance of the storage. For our application deployment on Azure, only Ultra appears to offer a viable solution.
------------------------------
Ralpha Labarta
CTO
Engage PEO
St. Petersburg FL US
------------------------------
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.