Is it possible to upgrade a 2020 (single head) to a 2040(HA), if so what is the process (new controllers)? Also, can the existing 2020 licenses be transferred to the2040?
... View more
All tenants on the same hosts so each host would connect to each vfiler - I think your right, multiple vfilers dont really make sense here... BTW - Looking forward to your MultiStore sessions @ insight..
... View more
We have an environment in which multistore is used when each customer has their own sets of hosts based on iSCSI. We would like to investigate how multistore could be used in an environment in which the hosts are also shared (VMware ESX), however, the only approach we can assume is having these hosts connected via iSCSI many many times to vfilers. With multiple subnets / ip’s for loadbanacing etc this would result in many iSCSI sessions which would become difficult to administer (not to mention very quickly hitting maximums!) I took a brief look at the “Deploying Secure Multi-Tenancy into Virtualised Data Centres” paper which seems to be using NFS within tenant vfilers which are then exported to the ESX servers. Tenant VMs are then placed on their respective vfiler....... I am looking for thoughts / advice pls.
... View more
Is there a tool / script which can re apply CIFS shares once data has been migrated from a file server onto a filer? Also, if you snapvault a cifs volume to a secondary filer which subsequently needs to be made read-writeable in a disaster what can be used to re apply shares (or do these shares already exist)??
... View more
Looking for an RPO of 30 / 60 seconds for SQL - What would you do? RTO is not as tight as RPO so this is not an issue and we have this covered. Do you have the TR# re SQL Sync as I can't seem to find it...
... View more
So how can you protect databases real time if they will always be crash consistent? Scripts or SM products are executed at scheduled times so seconds after this time the data has exceeded the RPOs? Also, does sync and semi sync also transfer snapshots like async? Thanks
... View more
Is it fair to say that SME / SMSQL etc would not be needed with snapmirror if using snapmirror sync or semi-sync as replicas are not async point-in-time snaps. With sync or semi sync writes to disk are affectively captured on the destination disk... ???? This is assuming SME etc is only being used to provide consistent replicas and is not used as a backup product...
... View more
Ok, I added a snapdrive license once more to the destination filer - Removed the default transport protocol settings from within the snapdrive MMC - Added all filers individually within transport protocol settings and all works well now. So yes, you do need a snapdrive license at the destination for snapdrive to request a snapmirror update.... Not great!
... View more
I have tested with an eval and no it is not. I am trying to setup snapdrive to talk to snapmirror destination filers for the purpose of executing snapmirror updates - When providing details of the destination filers via the Transport Protocol Setting page I receive the error "Failed to verify login credentials for the storage system. The requested operation is not permitted since this functionality is not licensed". I have tired both HTTP & HTTPS, not using RPC as the local creds are not the same as the destination. On the local site I am using filer based licensing....
... View more
Can anyone explain what this means. Note: After the transfer, the non-qtree data can only be a SnapMirror source, never a destination. Although you can copy data from the non-qtree data to another qtree, you cannot copy data to the non-qtree data from another qtree. Does this mean I can only snap mirror once and after this I can not update or schedule?
... View more
Hi Peter 1.In your example you use snapvault - It this also the case with snapmirror? 2.Will this still be file based replication? 3.Can the destination be the root of the volume rather then a qtree, i.e /filer2:/vol/vol 4. Can this be included in a schedule Thanks
... View more
I need to use qtree snapmirror due to it's file basedreplication, however some data sits in the root of the volume which is cifsshared. I also need to replicate this data but not using VSM. I have read aboutnone qtree data replication using a "-" within the source name. Will this method satisfy my requirement? I am notinterested in system data / files, only user data. Also, is this method pureQSM as I will also be replicating other qtrees into this volume.
... View more
Ok. So within the first snapmirror relationship (original source > unique vfiler) I give the destination vol a different name, then I can name the flexclone of the destination the same as the original volume then move this into vfiler0 which should maintain the original path names?
... View more
Ok. flexclone looks like the best option for disk space, howerver if I create a flexclone can I maintin the same name as the parent volume in an attempt to keep the same name / path so when I move the flex clone into vfiler0 (the test environment) all links / mount / shares continue to work? Or does the flexclone need a unique name from the parent vol? If this is not possible we will need more disk space and mirror from the unique vfiler into vfiler0 as this will not break my volume names / paths. In this senario can I mirror from "original source > unique vfiler > vfiler0"?
... View more
To allow for a testing environment I am thinking of using mulitstore. So I would create a vfiler on the same networks as the existing filers and give them unique names / IPs then configure vfiler0 in an identical fashion to the existing filers, including name , IPs, exports, shares, usermap, hosts etc etc. I would attach the cloned vfiler0 to a segregated network which would also contain a cloned test environment which includes active directory, NIS and relevant hosts etc. Snapmirror would replicate volumes / qtrees to the unique vfiler, to allow for testing I would break off the snapmirror relationship, then move the volume / qtree to vfiler0, re apply shares / exports which will allow a cloned environment to mount / share without having to deal will all the host mappings etc. The main reason for this approach is to allow me to clone then segregate the active directory, delete the computer accounts (names) of the real existing filers the rename vfiler0 to that of the real existing filers which will allow all exports / mappings to work in a test environment. 1, Is this a good approach ? 2, When volumes / qtrees are moved between vfilers will security (ntfs acls / unix perms) also move? Obviously this is key to the whole approach
... View more
I have answered this myself - I was naming the datastore within ESX the same as the path, i.e. /vol/volume/qtree I changed the name to a single label name and all is well.. Thanks for the quick reply, again!
... View more
Hi Scott I am having issues with NFS within a vfiler – I always receive the error “The operation failed because the specified directory path in incorrect” from an ESX server. I have check the exports file and exportfs against other non mutistore filers for config errors – I have checked the file via cfis and rdfile for syntax errors – NFS is running also. I did try a trace with “options nfs.mountd.trace on” within the vfiler, however there is no messages log to check? Am I missing something relevant to vfilers with NFS? Regards
... View more
Hi Scott It now seems the filers are members of the windows domain which is good. During this migration the new filers will be given free IPs on the same subnet as the existing filers. Once migration is complete the networks will be separated and the existing IPs of the old filers will be applied to the new. At this point the names of the filers would also be migrated, to do this would I need re run cifs setup and change the filers name? Would this cause an issue with security etc? Can I migrate the names another way with an alias or something? The idea behind the same names is to ensure that shares / exports map without re configuration of the clients etc.
... View more