We are running SME for Exchange 2010; we have a separate server for verification. The verification server has Exchange management tool installed.
Exchange 2016 has not got management tool like Exchange 2013/2010.
What is the requirement if we want to avoid running verification on a Exchange 2016  production server?

I have a FAS3140 CIFS share of around 30 TB , would like to copy it outside (synlogy same network).Initially I tried to copy it through windows share through desktop but the speed is 10 MB/s which may take 6 month to complete.

I have shell access to both synlogy & netapp filler, what command I can use to copy it fast ?sftp ? or should I mount netapp cifs share on synlogy ? or is there any other way ?I just need the data, there is no permission issue.

Please suggest


Note: My netapp02 is down(bcz of one of the disk shelf module got failed) which has all this cifs share & netapp01 has taken over the netapp02 & the respective cifs share.

DataOntap7.6

Good Day 

I used site recovery manager to failover my database server to another site using Vmware SRM , Country1 failed over to Country2 

Everything worked file except I cannot see my backups taken when the server was in Country1 

Snap Drive is showing the drives. but no backups on snap manager sql

opened case with netapp, but nothing so far. 

I can only see the new backups taken on Country2. 

Old snapshots are visible on the cluster. 

any ideas ?

Thanks

I am in the process of trying to get SnapCenter working (and what a fun journey that is!). Despite being far along in the process, I still have some questions about what SnapCenter is doing. Below are my questions; if anyone if willing to take a crack at them it would be very appreciated. I am seeking answers that are simple and avoid a lot of NetApp specific terminology. (Caveat: Everything in the environment is virtual machines. We are only backing up VM's and it is all local. All NFS. VCSA 6.0u3 + SnapCenter 3.0.)

1. Where is the data stored? You set up your resource groups, policies and connection to the SVMs. So, where are the actual backups stored? Are there individual snapshots for each server in an SVM? very confused on this point. 
2. What happens to NetApp snapshots? When the NetApp installers came we set up local snapshot policies on the NetApp as a stop gap solution. With SnapCenter being stood up, do we need to remove those old policies? Are they redundant? SnapCenter does not seem to 'see' them (as far as I can tell).  
3. Is it better to setup the Snapmirror policies with SnapCenter or in NetApp System Manager? What is this difference?
4. How come SnapCenter doesn't seem to 'see' anything that has been set up in system manager? Is this by design or am i doing something wrong? (Thinking about the snapshots, snapmirrors, and snapvaults that are already in place) 
5. How come, without resource groups, when I back something up in SnapCenter, I can see/restore from SnapCenter but vSphere doesn't see them. 

That's it for now. Overall feeling on the product is that it is not really convenient for people who are not NetApp professionals. We are a very small shop and as the sole ‘systems engineer’ products like this that have a higher learning curve are more difficult to integrate and use.  I think making the install easier and more guided, combined with a simple run down of what the heck SnapCenter does (from a logical, no acronyms, nothing specific sense) would be very helpful. (What I mean is that, after 2-3 weeks of diving through documentation and trying to setup SnapCenter, I couldn’t give you a simple explanation of how it works and too me, that is bad.)

Thanks for any help!

This seems like one of those "instructions not clear moments" for me. 

VSC 7 removes backup and recovery so at this time you have to manually migrate your backup jobs into SnapCenter which is fine I'm doing this in our lab to prep for production and understand the mechanics.

I am unable to get the vsphere plugin to install with the vcenter virtual appliance. What credentials should I be using? I should be targeting the vcenter server appliance for plugin installation right?

When I use root credentials it says invalid credentials, and when I use vcenter server admin credentials it says host not found, and when I use a domain account that has administrator roles in vcenter it says specify a valid run as account or verify credentials.

What are the proper steps to register the snapcenter plugin with vcenter?

Hello All,

We have issue adding Altavault and NetApp to SnapCenter 3.0.

Have any one sceen this error ?

SnapCenter

So...I'm quite confused about this bulletin

End of Availability: SnapManager for Microsoft SQL Server and SnapDrive for Windows

For your information and planning, this notice is meant to inform you about some NetApp® products that have come to the end of their availability and/or some products that are no longer available from our suppliers.

Data protection is a key challenge for IT organizations. The suite of NetApp SnapManager®, SnapDrive®, and Snap Creator® products has helped thousands of customers meet this challenge. We have consolidated many of these individual products into NetApp SnapCenter®, which provides a modern data protection solution for the hybrid cloud. This bulletin announces end of availability for all versions of SnapManager for Microsoft SQL Server and SnapDrive for Windows on all NetApp platforms as of the dates indicated later in this bulletin.

I've setup Snapcenter and have been playing with it, and I do see that within Snapcenter I can do alot of the functions of Adding/Connecting a disk which I've done locally on the local windows system previously however one of the interesting pieces is that they have announced end of availability, however Snapmanager for Exchange actually still requires Snapdrive.

So, I have a product thats not in Snapcenter (yet), but still needs snapdrive, but snapdrive is end of availability.  Anyone got any roadmaps when they are going to fix that glaring little issues?

Hi Guys,

when i try to add a Storage System, i get every time these Error

Failed: 401 not authorized

I tested it on diffent Systems such FAS, AltaVault, SVMs.

Any ideas?

Hi all.

I'm planning to migrate source and destination volumes of snapvault relationships to new filers, but all SnapVault relationships are being managed by DFM, and to add more complexity I have some Oracle servers running SMO with SnapVault relationships also being managed by DFM.

So, let's suppose my current source filers are old-src1, my current destination filer is old-dst1, my new source file is new-src1 and my new destination filer is new-dst1.

I don't have any problem to migrate primary volumes from old-src1 to new-src1, and also from old-dst1 to new-dst1. The steps below summarize what I'm doing:

1) Create new src and dst volumes in both filers (using the same original name);
2) Perform SnapMirror from old filers to new filers;
3) Break SnapMirror relationships;
>>>> NOW THE STEPS IN THE DFM STARTS <<<<
4) Set 'dpReaper' in the DFM to "Never". This is to make sure that during the migration, the conformance or reaper does not reap any relationship;
5) Suspend all DFM datasets that will have src/dst volumes migrated to new filers;
6) Relinquish the relationships in the DFM;
7) Remove the current primary vols/qtrees from the 'Primary data' node;
8) Remove the current snapvault destination volumes from the 'Backup' node;
9) Relinquish the primary qtrees from the DFM datasets;
10) Add the snapvault configuration information to the filer new-dst1 through the command snapvault start -r -S.

Note: After this command, filer new-dst1 recognizes all snapvault relationships coming from filer new-src1
11) Add the new snapvault destination volumes (in new-dst1) in the DFM;
12) Import the new external relationships (from new-src1 to new-dst1) to the dataset;
13) Resume the DFM datasets
14) Set 'dpReaper' in the DFM to "Orphans".

This procedure works fine but I have two "inconveniences":

A) Specific for SMO I have two commands to do (below) on the Oracle servers running SMO as last steps:
> snapdrive dataset changehostname -dn <DATASET_NAME> -oldname old-src1 -newname new-src1
> smsap storage rename -profile <SMO_PROFILE> -oldname old-src1 -newname new-src1

Finally, after the above steps I can run the following SMO operations using snapvault snapshots created before the migration:
-> Create backups (primary and secondary) with SMO;
-> I can mount primary snaps using SMO;
-> I can clone the DB using primary snaps through SMO;
-> I can restore the DB using primary snaps through SMO;

But I CANNOT perform Mount, Clone and Restore operations through SMO using snapvault snapshots created before the migration (it works when I use snapvault snapshots created after the migration). I receive a message saying "Could not locate remote snapshot". It seems that SMO is not being able to find the snapshots created before migrate the filers, BUT WHY?. See the full error message below:

--[ INFO] SMO-13036: Starting operation Backup Mount on host rhel65-oradb01
--[ INFO] SMO-13046: Operation GUID 402880745e052eac015e052eb47e0001 starting on Profile PROF_ORADB02
--[ INFO] DS-10001: Connecting mountpoints [/u02/oradb02/datafiles] from snapshot smo_prof_oradb02_oradb02_f_h_1_402880745dfd9eec015dfd9ef5ab0001_0 in copy 63 of backup 1503198695 of dataset smo_rhel65-oradb01_oradb02.
--[ERROR] FLOW-11019: Failure in ExecuteConnectionSteps: SD-10028: SnapDrive Error (id:2868 code:102) Could not locate remote snapshot or remote qtree for new-src1:/vol/vol_ora_datafiles02:smo_prof_oradb02_oradb02_f_h_1_402880745dfd9eec015dfd9ef5ab0001_0
--[ERROR] FLOW-11010: Operation transitioning to abort due to prior failure.
--[ INFO] SD-00016: Discovering storage resources for /opt/NetApp/smo/mnt/-u02-oradb02-datafiles-20170820004027188_0.
--[ INFO] SD-00016: Discovering storage resources for /opt/NetApp/smo/mnt/-u02-oradb02-control-20170820004027174_0.
--[ INFO] SD-00016: Discovering storage resources for /opt/NetApp/smo/mnt/-u02-oradb02-archives-20170820004027185_0.
--[ WARN] FLOW-11011: Operation aborted
--[ERROR] FLOW-11008: Operation failed: SD-10028: SnapDrive Error (id:2868 code:102) Could not locate remote snapshot or remote qtree for new-src1:/vol/vol_ora_datafiles02:smo_prof_oradb02_oradb02_f_h_1_402880745dfd9eec015dfd9ef5ab0001_0
--[ERROR] SMO-13032: Cannot perform operation: Backup Mount. Root cause: SMO-11007: Error cloning from Snapshot copy: FLOW-11019: Failure in ExecuteConnectionSteps: SD-10028: SnapDrive Error (id:2868 code:102) Could not locate remote snapshot or remote qtree for new-src1:/vol/vol_ora_datafiles02:smo_prof_oradb02_oradb02_f_h_1_402880745dfd9eec015dfd9ef5ab0001_0
--[ INFO] SMO-13039: Successfully aborted operation: Backup Mount
--[ERROR] SMO-13048: Backup Mount Operation Status: FAILED
--[ INFO] SMO-13049: Elapsed Time: 0:00:26.059

B) When I delete the old filers (old-src1 and old-dst1) from the DFM, all backups created before the migration disappears from Protection Manager (Restore Wizard). I only can see backups created after migrate volumes to new filers. I'm only able to use Operations Managers to restore secundary backups (snapvault snapshots).

I really appreciate if someone can help me understand why it happens, and if there is an option to fix it, or even an workaround. The issue 'A' is my first priority.

Thanks a lot.

Flávio Onofre de Souza

Hi,

is there a comparsion between SnapCenter and Snap Creator. Ther was a link for SC vs, SMGR:

https://kb.netapp.com/support/s/article/ka41A000000XcVOQA0/feature-comparison-current-generation-snapmanager-products-vs-next-generation-snapcenter-plug-ins?language=en_US

But not for Snap Creator.

So what is differnt especially in restore of single files. Automatied provisioing of secondary volume.

Would be really helpfull.

Best wishes,

Markus.

Hi All

When I start the Restore Wizard the dropdown Menu "Restore volume name" cuts long volume names:

Could I change this UI behaviour somewhere (fe wider column)?

TIA

Thomas

In the online forum document https://community.netapp.com/t5/Technology/How-to-Install-and-Configure-Community-Plugin-in-Snap-Creator/ba-p/84591 it tells us that the community written and supported plug-ns are in the NetApp GitHub location https://github.com/NetApp 

How ever when you go look here you can't find any repostiory starting in SC-<plugin> has support for SnapCreator been dropped?

Should I be looking to migrate away from SC?

If the community plugins are still being maintained where are they?

Any help much appreciated.

Regards

Martin

Hi,

I have a brand new installation of SnapCenter 3.0 (not upgraded) and I have the vSphere plugin installed on a separate server, I have message queueing running on both the SnapCenter server and the vSphere plugin server.

When I try to run a backup it fails instantly with the error "An error occured while adding job to jobQ: Message Queue service is not available." in SnapCenter, the job logs aren't of any help and nothing in event logs on either server.

Any ideas where to look next, there's very little information around on the web given this is a new feature with SC 3.0

Edit: Upon further investigation I am also getting this same error when attempting to run newly configured SQL Backups via SnapCenter, which points to the issue being with Message Queueing directly on the SnapCenter server itself?

Dear Community,

When I start a BackupJob in the Snapcenter, the job takes infinite. I checked the NetApp-Filers, there are creating Snapshots.

"Unable to retrieve backups. Ensure that the catalog server is reachable."

I restarted the Services on the Linux, maybe anyone else has an Idea?

Best Regards

Fabian

Hi there,

Hoping someone can help me with what is likely a newbie mistake.  I setup storage connections using the domain snapcenter account via the UI when the DBA team logs into snapcenter to create their backup policies it gives them an error that no storage connection has been configured for them.  When the DBA team goes to look at storage connections they don't see any setup, when I go to storage connects as the snapcenter user I see 3 SVMs configured.  I also tried logging in using my domain admin account and also don't see any storage connections.  The DBA team accounts, my domain admin account and the snapcenter account are all added to the SnapCenterAdmin role.

I'm running Snapcenter 2.0P2.  My question is if I need to setup storage connections indvidually for every user that will be logging into Snapcenter to create backup policies?  I had thought setting it up as the snapcenter user these storage connections would be available to all users.

Thanks,

Matt.

What version and where can I download a supported SC PowerShell Toolkit that will successfully work with SC 4.3+?

SC PowerShell Toolkit version 4.1 failed testing with SC 4.3+

We are using SuSe Linux 12.1 which uses systemd for service daemons.

We need to start scAgent with the OS (reboot, auto restart on scAgent error)

For scAgent 4.3.0 there is only info available for sysvinit which doesn't match for systemd.

We have created the following script/usr/lib/systemd/system/ScAgent.service

[Unit]
Description=Snapcreator Agent

[Service]
ExecStart=/opt/snapcreator/scAgent4.3.0/bin/scAgent start
ExecStop=/opt/snapcreator/scAgent4.3.0/bin/scAgent stop

[Install]
WantedBy=multi-user.target

When we run the service it stops automatically:

Running:

scAgent.service - Snapcreator Agent
   Loaded: loaded (/usr/lib/systemd/system/scAgent.service; enabled)
   Active: active (running) since Mo 2017-09-11 08:25:17 CEST; 1s ago
  Process: 26190 ExecStop=/opt/snapcreator/scAgent4.3.0/bin/scAgent stop (code=exited, status=0/SUCCESS)
 Main PID: 26282 (scAgent)
   CGroup: /system.slice/scAgent.service├─26282 /bin/sh /opt/snapcreator/scAgent4.3.0/bin/scAgent start
           ├─26312 java -Xms32m -Xmx128m -XX:MaxPermSize=64m -classpath /opt/snapcreator/scAgent4.3.0/lib/scAgent-4.3-core.jar com.netapp.snapcreator.agent.nextgen.watchdog.external.ExternalWatchdogStarter start
           ├─26313 sleep 10
           └─26343 java -Xms64m -Xmx256m -XX:MaxPermSize=128m -DINSTALL_PATH=/opt/snapcreator/scAgent4.3.0 -classpath /opt/snapcreator/scAgent4.3.0/lib/scAgent-4.3-core.jar:/opt/snapcreator/scAgent4.3.0/lib/cxf-rt-tr...

Sep 11 08:25:17  systemd[1]: Started Snapcreator Agent.
Sep 11 08:25:17  scAgent[26282]: Starting scAgent:

Stopped (see timestamps):

scAgent.service - Snapcreator Agent
   Loaded: loaded (/usr/lib/systemd/system/scAgent.service; enabled)
   Active: inactive (dead) since Mo 2017-09-11 08:25:28 CEST; 6s ago
  Process: 26403 ExecStop=/opt/snapcreator/scAgent4.3.0/bin/scAgent stop (code=exited, status=0/SUCCESS)
  Process: 26282 ExecStart=/opt/snapcreator/scAgent4.3.0/bin/scAgent start (code=exited, status=0/SUCCESS)
 Main PID: 26282 (code=exited, status=0/SUCCESS)

Sep 11 08:25:17  systemd[1]: Started Snapcreator Agent.
Sep 11 08:25:17  scAgent[26282]: Starting scAgent:
Sep 11 08:25:27  scAgent[26282]: Watchdog: Running
Sep 11 08:25:27  scAgent[26282]: Agent: Running
Sep 11 08:25:27  scAgent[26403]: Shutting down scAgent:
Sep 11 08:25:28  scAgent[26403]: Watchdog: Stopped
Sep 11 08:25:28  scAgent[26403]: Agent: Stopped

When we check the scAgent script directly with

scAgent status

it seems to run as long as the service ist running and then is stopped after the systemd service stops.

running:

#systemctl start scAgent.service
#./scAgent status

Checking Status of scAgent:
    Watchdog: Running
       Agent: Running

after a few seconds:

#./scAgent status

Checking Status of scAgent:
    Watchdog: Stopped
       Agent: Stopped

As long as we run 'scAgent start' dircectly/without systemd it is running fine...

Does anybody have a solution to this?

Are the scripts at /bin not intended to be used with s systemd script?

Hi!

We have installed SnapCreator FrameWork 4.3.1P1 and OnCommand Unified Manager 7.2 (as VM-appliance). When I add the data in the SnapCreator - Configuration and start a backup, an error message is logged.

When I set option ENABLE_SECURITY_PROTOCOL_TLS_V1 to Y than this message is logged:

[2017-09-12 11:20:51,455] INFO: STORAGE-05016: Creating a Operations Manager console event [script:information-event] on [ocunifiedmgr.oeamtc.at]
[2017-09-12 11:20:51,455] DEBUG: com.netapp.snapcreator.storage.executor.ZapiExecutorException: java.net.ConnectException: Connection refused (Connection refused)
	at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:50)
	at com.netapp.snapcreator.storage.executor.DfmExecutor.run(DfmExecutor.java:77)
	at com.netapp.snapcreator.storage.api.dfm.DfmImpl.executeRequest(DfmImpl.java:723)
	at com.netapp.snapcreator.storage.api.dfm.DfmImpl.createOMEvent(DfmImpl.java:640)
	at com.netapp.snapcreator.storage.StorageCoreImpl.omCreateEvent(StorageCoreImpl.java:1954)
	at com.netapp.snapcreator.workflow.task.ZAPITask.OMEventGenerate(ZAPITask.java:2127)
	at com.netapp.snapcreator.workflow.task.Success.successMessage(Success.java:103)
	at com.netapp.snapcreator.workflow.task.Success.execute(Success.java:55)
	at com.netapp.snapcreator.workflow.impl.SCTaskCallableBlocking.call(SCTaskCallableBlocking.java:49)
	at com.netapp.snapcreator.workflow.impl.SCTaskCallableBlocking.call(SCTaskCallableBlocking.java:18)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
	at java.net.PlainSocketImpl.socketConnect(Native Method)
	at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327)
	at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193)
	at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180)
	at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
	at java.net.Socket.connect(Socket.java:543)
	at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:614)
	at sun.security.ssl.SSLSocketImpl.<init>(SSLSocketImpl.java:430)
	at sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:125)
	at netapp.manage.http.HTTPClient.<init>(HTTPClient.java:597)
	at netapp.manage.NaServer.getSession(NaServer.java:353)
	at netapp.manage.NaServer.invokeHTTP(NaServer.java:950)
	at netapp.manage.NaServer.invokeElemForXML(NaServer.java:780)
	at netapp.manage.NaServer.invokeElem(NaServer.java:696)
	at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:45)
	... 14 more

If I set this option to N than this is logged:

[2017-09-12 13:05:25,957] INFO: STORAGE-05016: Creating a Operations Manager console event [script:information-event] on [ocunifiedmgr.oeamtc.at]
[2017-09-12 13:05:25,957] DEBUG: com.netapp.snapcreator.storage.executor.ZapiExecutorException: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
	at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:50)
	at com.netapp.snapcreator.storage.executor.DfmExecutor.run(DfmExecutor.java:77)
	at com.netapp.snapcreator.storage.api.dfm.DfmImpl.executeRequest(DfmImpl.java:723)
	at com.netapp.snapcreator.storage.api.dfm.DfmImpl.createOMEvent(DfmImpl.java:640)
	at com.netapp.snapcreator.storage.StorageCoreImpl.omCreateEvent(StorageCoreImpl.java:1954)
	at com.netapp.snapcreator.workflow.task.ZAPITask.OMEventGenerate(ZAPITask.java:2127)
	at com.netapp.snapcreator.workflow.task.Success.successMessage(Success.java:103)
	at com.netapp.snapcreator.workflow.task.Success.execute(Success.java:55)
	at com.netapp.snapcreator.workflow.impl.SCTaskCallableBlocking.call(SCTaskCallableBlocking.java:49)
	at com.netapp.snapcreator.workflow.impl.SCTaskCallableBlocking.call(SCTaskCallableBlocking.java:18)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
	at java.util.concurrent.FutureTask.run(FutureTask.java:166)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:701)
Caused by: javax.net.ssl.SSLException: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
	at sun.security.ssl.SSLSocketImpl.checkEOF(SSLSocketImpl.java:1484)
	at sun.security.ssl.AppInputStream.read(AppInputStream.java:84)
	at sun.security.ssl.AppInputStream.read(AppInputStream.java:69)
	at netapp.manage.http.HTTPMessage.readLine(HTTPMessage.java:245)
	at netapp.manage.http.HTTPResponse.read(HTTPResponse.java:74)
	at netapp.manage.http.HTTPClient.doRequest(HTTPClient.java:827)
	at netapp.manage.NaServer.invokeHTTP(NaServer.java:962)
	at netapp.manage.NaServer.invokeElemForXML(NaServer.java:780)
	at netapp.manage.NaServer.invokeElem(NaServer.java:696)
	at com.netapp.snapcreator.storage.executor.ZapiExecutorImpl.run(ZapiExecutorImpl.java:45)
	... 14 more
Caused by: javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
	at sun.security.ssl.Alerts.getSSLException(Alerts.java:154)
	at sun.security.ssl.SSLSocketImpl.recvAlert(SSLSocketImpl.java:1902)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1074)
	at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1320)
	at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:698)
	at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:119)
	at java.io.OutputStream.write(OutputStream.java:75)
	at netapp.manage.http.HTTPMessage.write(HTTPMessage.java:345)
	at netapp.manage.http.HTTPClient.doRequest(HTTPClient.java:826)
	... 18 more

Hostname and user-credentials are correct. As protocol HTTPS is chosen and port 443 is set.

SnapCreator is installed on a host with RHEL 6.8 64bit, Java version is 1.8.0.45-b14

Both SnapCreator and OCUM have installed HTTPS-certificates signed by our CA... And both hosts are VMs on the same ESX-cluster an are connected to the same network...

What am I missing?

Thanks in advance for every hint!

BTW: all other things like backup, and so on are all working correctly. OCUM is connected to WFA - so it should be accessible...

Hello.

We are using snapcreator Version 4.3.1 tool

currently we have installaed new HANA 2.0 sps 02, when i tried configre the backup in snapcreator i have an error tenant database not supported 

how can i schedule a backup for MDC database? 

Thanks

SAPDB

My user have ESX environment, he install the VSC plug-in for snapshot backup purpose. Later he install and integrated with Snap Center. After few months usage, he want to drop the Snap Center at this moment and decide to use VSC for backup. Is there any detail procedure on how to remove the integration between Snap Center & VSC? Also the backup record is store in the MySQL in Snap Center. Is there any way to get those backup record from Snap Center and update in VSC? He try to stop the VSC MySQL and find VSC will lost all snapshot backup record. Anyone know how to solve this?