Good afternoon. There are remote NetApp devices that are not part of a cluster. Is it possible to implement copying snapshots from a NetApp appliance that is not part of a cluster to a NetApp cluster using SnapVault or SnapMirror. The model of the devices in the cluster is FAS8300. Maybe there are some other options(tools) to realize this task.
... View more
Hello All, Please a client has Snapmirror configured between Production and DR. Three of the relationships have failed with the following error: "the number of snapshot copies on destination volume has reached maximum supported count of 1019". Everytime the relationship needs to update as per policy which is HOURLY, it creates a Snapshot on those 3 DR Volumes which causes it to get filled up and eventually cause the relationship to Fail to an Unhealthy state. Please how can these be rectified?
... View more
Where can you find the housekeeping tasks in SnapCenter version 5 & 6 (on Windows). Several KB articles refers to Windows Tasks Scheduler, but that seems to a long time ago. You can also create a schedule using powershell and the syntax presented in the KB article but there is no apparent way to verify that the schedule is actually there, or if you have multiple entries of the same housekeeping task. Example of a housekeeping task: SnapCenter_RemoveSecondaryBackup
... View more
I have a very dynamic MSSQL environment and I don't want to miss a new DB instance in the GUI. What would be the best way to do a scheduled refresh of resources?
... View more
What is the impact of using the "-nodata" option when running an "isync"? For example, we had a partial copy of source data on a destination NetApp volume (a previously failed XCP copy due to stability issues on the source non-NetApp storage box. We had to use a different source box so couldn't reuse the previous copy catalog ID). We needed to establish a new catalog of the current state along with resuming the copy operation, so we opted to use isync rather than deleting all destination data and starting a fresh copy. (we're talking 250Tb over a 1Gb network link... ancient hardware with no option to improve the speed) Due to the slow 1Gb link, iSync was taking a long time because XCP was reading in all data over the 1Gb link from the source so it could do a byte-for-byte check. Things drastically improved when we used the -nodata option, but what impact could using this have on the isync process besides being faster? What are we loosing out on? The source data is live so changes can occur during each XCP run. Once the isync finishes I plan to use "sync" with the new catalog ID. Would this be ok? Why does sync not have a -nodata option compared to isync? How does a sync check if a source file has changed without reading the whole file into the XCP server to do a byte-for-byte comparison? Thanks in advance, Paul.
... View more
