Hey,
does anyone know if the storage plugin at the automation store is planned to support management of replications for flexgroups?
thanks!
Hey,
does anyone know if the storage plugin at the automation store is planned to support management of replications for flexgroups?
thanks!
Hey,
SnapCenter 4.3.1 was released a few days ago on the support site but no docs are available.
what does it fix? are there any new features?
I couldn't find any release notes or documentation that would explain.
Thanks
Hi All.
Have an issue with SnapCenter 4.1.1 on vSphere 6.7. The User ID that was used to tie in SnapCenter and VSC to vSphere had the Password expire. It was noticed after 3 days. I got the Password re-enabled, and VSC is working OK. SnapCenter has an issue where the Resource Group list is now empty. If I try recreate the Resource Group using the same name it is telling me that the Resource Group with that name already exists. Does anyone know how to get the Resource Group List to re-populate.
I have rebooted both the VCSA and Snap Center server.
Thanks
Mahmood
At my company we are backing up SQL Server by implementing SnapVault against a secondary storage system. We are not able to clone a database with logs from secondary storage if the logs have exceeded the retention time. But we have several snapshots in the secondary storage that contain these logs.
Someone did this?
After updating our CentOS servers the SnapCenter Plug-in Loader service (spl daemon) could no longer be contacted on port 8145. After running some tests it seems that the daemon is not compatible with Java svm 1.8.0_242, the deamon does not start a listening port on tcp/8145 so there is no communication possible with the SnapCenter server and backups stop working. No errors are being logged locally, the only thing noticable in spl_init.log is that Jetty cannot be initialized properly - Logging initialized @-1ms to org.eclipse.jetty.util.log.Slf4jLog. After downgrading to jvm 1.8.0_232 everything starts working again, until the next update cycle ofcourse. These problems are reproducible with plugin versions 4.2 and 4.3.
Anyone else experiencing this and/or has a workaround for this issue?
I backup up a volume to a file using SMTape backup on Ontap 9.1P20 but can not restore it to Ontap 9.7P2 as the restore fails. Is there a way around this issue or am I doing something I should not be doing?
The event logged says:-
Event: smtape.rst.fail: SMTape restore session 11 to /vserver/vol from /cifs-vserver/vol/file failed with error
The image you are trying to restore is not supported in the current version (current version [10. 0] backup image version [4. 0]) 14:1727.
Message Name: smtape.rst.fail
Action: Check for error details in the log file at /mroot/etc/log/backup. Retry the command after resolving the error reported.
I had a look at /mroot/etc/log/backup but it more or less says the same as above.
The restore and backup works OK when both are done using Ontap 9.1
Hi Pro’s!
I am confused regarding source and destination storage efficiency. What is best practice?
In my case, we have server data volumes nfs mounted in vmware. These volumes have:
Compression: true
Inline Compression: true
Constituent Volume: false
Inline Dedupe: true
Data Compaction: true
Cross Volume Inline Deduplication: true
Cross Volume Background Deduplication: true
The total savings are 33% (dedupe 10%, compression 23%)
Snapshot retention is 10 days
The primary volume above is setup to snapmirror its data to a vault volume once every night and store its snapshots for 90 days.
The secondary has no storage efficiency turned on at all.
I want to save as much storage as possible.
Will my primary storage system dedupe/compress all data in both primary and secondary storage, even if the snapshot retentions are different or will it only dedupe/compress data in my primary system?
This can present being a decrease in self-confidence, problems come to feel just as if they are able to be deteriorating, you really may possibly commence to come to feel on your own, or query yourself along with your ambitions. Alter is How To Manifest Money - don't resist it. The world won't give you and in addition your household what accurately you actually want till you expand to a completely new level.
We have Snapcenter setup to backup a MSSQL instance. There is one backup that we want to keep longer than the normal retention period. Is there any way to mark the backup as a 'keep longer'. The reason is, there were major changes to a test database and we've been asked to restore that test database a couple times already. We don't want the snapshot to be deleted at the end of the retention period until it's owners say all is good and then we can delete.
Thanks,
Ray
I want to backup SMB shares using a client. Now, this client lives in a different domain and it would be preferred if the data is encrypted. However, other traffic to this server need not be encrypted. So, is there a way to selectively encrypt the data for a share? Can the client force server to encrypt the data.
I successfully upgraded my plugin servers from 4.1.1 to databroker plugin 1.0.1 but i'm not getting any updates on jobs snapcenter server.
How do i tell snapcenter server to update or pull the jobs from the databroker plugins. The plugins are working properly as i can do automated restores and i'm getting emails from them but yet snapcenter server shows last backup as the morning before the upgrade.
Please and thank you for any help!
Hi,
A backup process has failed creating the SnapVault relationship to secondary storage. This relationship was later created by the next backup but the failed backup is not reflected in the SnapCenter GUI.
Is it possible to refresh this backup from the secondary storage to appear in the GUI?
Thanks!
Hello,
I am trying to create a LUN in a Windows Failover Cluster for the first time using SnapCenter after having used SnapDrive for years. I'm running across two very confusing elements and wondered if someone could provide insight. Specifically:
I did read in NetApp documentation (below) the line "You need only create the disk on one host in the failover cluster." Does that indicate I should only connect to one of the initiators in the Map LUN screen and select the matching initiator group in the Group Type screen? If so, does the wizard automatically add mapping to the additional nodes?
Any help will be appreciated!
Guys, moving from SMO to SnapCentre to keep within support for our Oracle DBs. Currently, we run SMO scripts locally on the hosts to backup our DBs and these scripts are triggered by a central batch scheduling utility that's in a HA config. As such, the script definitions are stored on the hosts and simply triggered form the batch scheduling software which is in HA so no production issues if we have to take a node in the scheduler down for patching etc. I'm wondering, if we move to SnapCentre where are script definitions stored and triggered from? Does SnapCentre have to be up for the schedules to run? If so, can it exist in a HA pair?
We have to move to SnapCenter from SMO due to compatibility issues with our SMO/Oracle estate going forward. Do the products have feature parity? Is this documented anywhere?
learning SnapCenter with SQL, a few questions you may help. thanks in advance.
1. when we restore SQL database from a snapshot, will all blocks/whole database or only changed blocks be copied back?
2. when we make a snapshot on an individual SQL database, is the snapshot only made on this database or the original volume?
3. can the SQL restore also be run on SQL server or only allow on SnapCenter?
4. what is the difference between database migration and clone? I thought the clone is a way of migration.
5. will a database clone process actually map the snapshot to a new host?
6. can snapshots be allocated to different volumes or always have to stick with original volumes?
7. is the backup verification really a need? seems a different host will be needed.
Snapcenter 4.1.1.
Host is a Windows 2019 datacenter, i check and this should be supported.
I have one question i installed successfully remote plugin over GUI. All services are installed on host and running(2 plugin,core service) I can restart it. I see also under instances th databases.
After installation i want to config the plugin but i canot do it. first services are running. after 5 minutes host ist down and i restart all 3 services on host. i also restart the snapcenter server . but still host is down. under details i see snapcenter host core service is unreachable.
Can someone help me?
Hi,
we are running the Data Broker 1.0.1D for our vCenter backups. All fine except of a restore from secondary.
During the restore, the snap shot gets cloned and a export policy conaining all IP adresses of the vCenter is created and attached to the volume clone.
Data Broker discovers all storage interfaces.
Now it takes the first useable lif and modifies the mount parameter:
But the export policy does not contain the IP that fits to the export of 192.*
I also this entry in the logs:
Is there a way to influence the lif selection?
Marcus
Any VSC product specialists know if there is a new VSC version going to land anytime soon which supports VMWare 7 and SRM 8.3, currently VSC\SRA 9.7 does not. Just after a rough timeline if possible.
Thanks
FIrst, some background: we are migrating from SnapDrive/SMSQL to SnapCenter, however SC has numerous bugs <related to failover clusters and mount points> that requires us to keep SnapDrive (but not SMSQL) on a few servers until the bugs are patched. We are running OnTAP 9.3 because SnapDrive isn't supported in OnTAP 9.4 and above. I am aware there are special bundled versions of SnapDrive with certain SnapManager products (such as Hyper-V) that are supported in OnTAP 9.4 and above, but SMSQL isn't one of them.
Now my question: what if I installed one of the special SnapManager/SnapDrive bundled products on the SQL Servers where I need SnapDrive, and just didn't use the SnapManager component? Would that be a legitimate way to get a supported version of SnapDrive on those servers so we can upgrade to OnTAP 9.5? It would be even simpler, of course, if installing the latest SnapDrive patch as a standalone would be compatible (see below), but everything I've seen so far indicates it is not.
Would love to hear anyone's insight! Thanks in advance.
SnapDrive 7.1.5P3