Snapshots, y Veam backup

Similar Questions

• VEAM BACKUP error al eliminate snapshot

  Hola, he tenido a problema al realize una con replica veam una Máquina virtual backup. HA don't dado al WARNING United Nations no snapshot not eliminate el poder posterior to the replica. Lo he intentando manualmente desde el vsphere client eliminando el no snapshot pero no he could. Intentando nuevo realize her copia con veam backup ha dado error in esta ocasion. Editor los errores to see if someone can help me.

  Caution:

  Instant withdrawal
  Failed to RemoveSnapshot, snapshotRef 'snapshot-4536' timeout '3600000.
  Another task is already underway.
  Veeam Backup will attempt to remove the snapshot in the next cycle of work, but you can consider instantly deleting manually.
  Possible causes for lack of instant removal:
  -Connectivity problems, network or server vCenter Server is too busy to meet demand
  -Host ESX could not process the request for deletion of snapshot in a timely
  -Snapshot was already taken by another application

  Error:

  Initializing target session
  Failed to RemoveSnapshot, snapshotRef 'snapshot-4536' timeout '3600000.
  Another task is already underway

  
  Desde el vsphere client me ha dado el siguiente error: "another task is already underway.

  Ahora tengo the virtual machine only con a snapshot s than any I can eliminate. Tampoco puedo realize replica con el veam backup.

  Agradeceria una respond. MUCHAS gracias.

  Antonio

  Primero todo, of the reincia los del para ESX management agents that you release el pendiente task: http://kb.vmware.com/kb/1029041

  Eso Despues, fijate if hay algun en VM snapshot (if no hay en el no snapshot manager, igual fijate in el edit settings of the VM sober los discos, if no estan apuntando a alguna cosa nombre_vm - 000001.vmdk como - snapshots of hay estan TR). Hay of TR, crea otro desde el vsphere client, y luego hace UN "remove all" in el Manager of snapshots. ESO looks you delete all the snaps, con alguna suerte.

  Proba el clon of nuevo eso Despues a worm if works.

• not able to consolidate snapshots FRO WTP backup

  I had a backup operation failed WTP and now a certain vms snapshot needs consolidation but when I tried to consolidate. It says cannot access files sincce its coastline. Thne I tried folloing below kb for hanging the guest in another instant capture operating system then delete everything, but the virtual disk always points to another new vmdk. I tried to turn off the virtual machine and cnosolidate, but still the same error on file is locked. any IDE?

  VMware KB: Commit instant when there is no instant entry in the Snapshot Manager

  Okay, I like being able to consolidate with this kb

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2033537

  Thank you

• Using the feature 'snapshot' of tape backup?

  Ubuntu Server 10.04 LTS

  VMware-server - 2.0.2 - 203138.x86_64 patched with VMware-server-2.0.2-203138-update-2.patch you need to compile on Ubuntu.

  I wrote a script to stop the VMS gently before backup and raise them to the end.  I am backup on an NFS share so that encrypt a tape backup.  It takes about 6 hours.

  I would like to backup without having to go down the virtual machines.  Can I do this using a 'snapshot '?  I noticed after that I have create a snapshot of a virtual machine, the directory goes 256 files 62G in total size to 512 files of 65G in total size.  I just do upward 65G all on tape?  Is there some files (like maybe log files) that should not be backed up because they are constantly changing?

  Should what files I back up to make sure I have a complete backup I can restore.

  Thanks in advance for any advice.

  -Frank

  Yep,

  You are right!

  Copy all the files but this:

  Windows SBS 2003 R2-000001 - sXXX.vmdk

  Windows SBS 2003 R2 - 000001.vmdk

  Windows SBS 2003 R2 - Snapshot7.vmem

  Windows SBS 2003 R2 - Snapshot7.vmsn

  Don't forget that when you copy/save files, vdisk virtual machine (check in the Windows SBS 2003 R2.vmx file) pointing to Windows SBS 2003 R2 - 000001.vmdk, but it should point to Windows SBS 2003 R2.vmdk when a restore is performed

  Now, hope this helps definitely

  Best wishes / Saludos.
  Pablo

  Please consider awarding

  all useful or correct answer. Thank you!! -

  Por favor considered premiar

  any respuesta correcta o util. ¡¡MUCHAS gracias!

  Virtually noob blog

• VM continues to run on snapshot of assistance after the backup

  I use a third party software to backup my virtual machines on ESXi 4.1. the software uses the api VDDK.

  Store a few times before my VMs declined because all the spaces have been used on the data and the virtual machine will run on a snapshot of assistance... I have ssh was the box and found

  the size of this snapshot of assistance to be abnormally large size.

  Recently, I was about to meet the same problem, but fortunately, I noticed the instant helper over increasingly larger still. It was a great escape.

  So I stopped my program since the Snapshot Manager and backup, I consolidated the snapshot of assistance by clicking CLEAR ALL.

  The consolidation was completed and the virtual machine was no longer running on snapshot.

  It is more and more like a nightmare for me.

  I want to know why this is happening and what could be done to avoid this problem.

  Please advise me on this so that I can enjoy my weekend.

  .

  are its better to have a fresh virtual machine

  about the roles should not worry about this when you add this machine as a proxy in the machine of veeam roles will be automatically pushed.

  things are simple math to veeam proxy requires cpu, memory and network bandwidth for backup of treatment, so if you have a lot, you can host a non-critical application on the proxy computer.

  I recommend not to install any other application on proxy machine.

• What backup (on a budget) tool?

  I can there are a LOT of people ask similar questions, but have not found an answer that fits my needs. So here goes...

  I'm done with 3 physical hosts... and a vShpere Essentials Plus license

  HostA = ESXi4 + iSCSI SAN

  HostB = ESXi4 + iSCSI SAN storage Local - Physicallly 1-2km away hooked by direct fiber

  HostC = Win2K3 with vShpere top

  I know that I've got VCB somewhere in the present, and I started playing with GhettoVCB, but he found unreliable, I had to keep tweaking it works well. So I searched a commercial tool and handed around teams of consultants that came with a package of $30,000 (pft)!

  So I started watching Veam Backup, the demo on their site looked easy, but I couldn't get it installed and works here. Then I started watching Wrangeler VCB and other stuff, but nothing that seems to do what I want.

  My goal is simply to take a hot shot on HostA and then copy it from the SAN on a Local disk on the host b. The HostA and host b have access to the same SAN. If the building with HostA burns or is flooded, I'm leaving just the snapshot on host b and the machine is right when it was stopped.

  I want faf around tapes or other bullshit, we have no 3rd party backup of things, and we are not approved for vMotion or vStorage motion or anything.

  So what's the way to more simple maintenance and low, to do the job?  VCB will he leave HostC?

  Essentials plus you also have data recovery module.  You can get more information on that here - http://communities.vmware.com/community/vmtn/vsphere/datarecovery-vcb.

  Dave

  VMware communities user moderator

  New book in town - Start Guide quick vSphere -http://www.yellow-bricks.com/2009/08/12/new-book-in-town-vsphere-quick-start-guide/.

  You have a system or a PCI with VMDirectPath?  Submit your specifications to the unofficial VMDirectPath HCL - http://www.vm-help.com/forum/viewforum.php?f=21.

• The new Cluster of 5.5 ESXi backup solution.

  All,

  We have built a new Cluster on ESXi 5.5 with 2 servers DL380 G8 (hosts) and a HP Storevirtual 4330 connected via iSCSI to SAN storage. ISCSI all have 4 cards attached to an iSCSI network 1 GB Switch.

  The HP Storevirtual 4330 has 7 TB of space but will be 1-1, 5 to virtual machines and the data on it. processors Xeon 2 x 16 and 256 GB of RAM in each host.

  There are 10 VMs (2008 R2) server on the cluster.

  I also have a G8 DL360 with 5 TB of space on it and an autoloader CF HP 1/8 (I need to make the weekly and monthly strips for compliance requirements).

  I have 4 additional network adapters in the present to connect to the iscsi san network if it is an advantage.

  All my previous backups were backups on tape, but will have to be different.

  I was wondering what is the best solution for me compared to

  What types of backups are best (instant storevirtual, POS or software (Backup Exec and VEEAM are my options)

  Where to store data backups (SAN or a space on the backup win2008 server)

  What kind of backup gives less impact on the performance of the SAN, hosts or VMS running.

  Deduplication is assistance in the management of space, if so what should it be set up.

  If you use StoreVirtual as the underlying storage, no doubt, then take a look at Veeam that deeply integrates the device said, allowing you to use SAN snapshots during the backup process. This, in turn, considerably improves iterator and reduces the impact of the activities of backup from the production environment.

  Apart from him, you can install VB & R on the above mentioned physical server and connect the device to tape it. This deployment will allow you to archive the backup data in the midrange of tape on any basis you want, using special adhesive tape work.

  See you soon.

• Instant snapshot of VMWare and SAN

  How the instant different(or similar) snapshots SAN VMWare?

  Thank you

  The case of use as well as the method of snapshots is very different.

  As NuggetGTR says table instant base will take a snapshot of the entire lun/volume, but instant VM are just for each individual VM.

  How snapshots are created are very different and this determines the use case. EG Netapp table according to snapshots are very effective and take very little space, because (simplifying here) they mark all blocks in the volume in read-only - so you have an overview of the entire volume and because it is not copying all the data it is very fast and not take place.  As new data are written/modified/deleted it says new blocks and blocks alone reading in the snapshot are not deleted or modified.  This makes it very effective and good for backups long term.  However, as this is an array based snapshot is done at the block level and Netapp doent know what data are, could be a SQL database or the virtual machine.  honing to get application-consistent backups, to a plugin abreast of the API as Snapmanager for SQL or VSC for VMware.

  VMware based snapshots of a virtual machine are created by sleep (possibly) the guest operating system and then marking the. VMDK a new read-only. VMDK is created for the virtual machine that will handle the reads/writes new data and the original. VMDK will manage the readings for the old data.  This process is repeated for each snapshot that is taken.

  More the string of snapshots (and. VMDK) files the most impact on the performance of the virtual machine.  Also when you delete a snapshot must merge the. Files VMDK back together which can take a long time and have a performance hit of old clichés.  They will be also eats more space!

  These are intended to serve as a term 'safety nets' shot so that you can quickly return as any change - not as a long-term backup solution.

  They are a great tool to use in conjunction with array-based snapshots.  Using Netapp for example, you can install the VSC in vcenter and use it to plan the snapshots table in conjunction with the snapshots of VMware.

  This will fix a nice snapshot of each virtual machine with a consistent state Vmware hard, then the snapshot of the table will be instant volume/LUN with all these beautiful .vmdks suspended/static, then it will remove snapshots of Vmware.

  Some best practices:

  • The snapshots are not backup. A snapshot file is only a log of changes to the original virtual disk. Therefore, do not count on it as a direct backup process. The virtual machine is running on the most current snapshot, not the original disk vmdk files.
  • Snapshots are not complete copies of the original disk vmdk files. The take a snapshot does not create a complete copy of the original disk vmdk file, rather it copies only the delta records. The changelog in the snapshot file is combined with the original files from disk to be part of the current state of the virtual machine. If basic disks are removed, the snapshot files are useless.
  • Delta files can reach the same size as the original file of the basic disk that's why storage provisioned to a virtual machine grows an amount up to the original size of the virtual machine, multiplied by the number of snapshots on the virtual machine.
  • The maximum supported snapshots in a string is 32. However, VMware recommends you to use only 2-3 shots in a string.
  • Do not use any single snapshot for more than 24 to 72 hours. Snapshots should not be maintained for long periods of time for application or Virtual Machine version control purposes.
  • • This prevents snapshots to grow so large to cause problems when deleting / engaging them to the original virtual machine disks. Take the shot, make the changes to the virtual machine and delete / commit snapshot as soon as you have verified the condition of operation of the virtual machine.
    • Be especially diligent with use of the snapshot on the virtual machines, high-transaction, such as e-mail and database servers. These clichés can develop very quickly in size, filling data store space. Commit snapshots on these virtual machines as soon as you have verified the State of work appropriate to the process that you are testing.
  • If using a third party product that takes advantage of snapshots (such as backup of virtual machine software), regularly monitor systems configured for backups to ensure that no snapshots remain active for long periods of time.
    • Snapshots must be present for the duration of the backup process.
    • Photos taken by software of third party (called via API) may not appear in the Snapshot Manager vCenter. Check regularly for snapshots via the command line.

  Here is a good article on vmware snapshots:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=1015180

• Snapshots Veaam do not deleted

  Hi people,

  We use Veaam to back up our virtual machines, we used the VM of as well as Veaam proxy domain controller, guys seem to configure the Veaamto take a back up of this DC too! - do not ask me why am new to the company, but it's how they have it.

  one day this VM DC was turned off and he has refused to be turned, the error was on the CID conflict between snapshots, and the parent disk was changed after a snapshot was taken. I delete all snapshots and the snapshot nursery said that he didn't there is instant not now but it did not help - it was always snapshots in the data store. I managed to fix that by following a KB vmware site to correct the CID, the virtual machine has been lit successfully, and rear working well now.

  now my question is this, the Snapshot Manager shows some snapshots, but if I browse the data store I see two files VMDK-0002 and-0003, and the virtual machine has a warning that he requires a consolidation, when I look at the setting of the virtual machine that it points to one of the snapshots - that's all that scares me! see the screenshots.

  I have read through VMware and Veaam fuorms, and I have seen that this is a common problem and you need to do is create a snapshot can perform a delete all, but honestly not scared to do, basically cause the vmx file is pointing to one of the snapshot,

  So guys Expert can confirm if it is safe to do so and it will not harm the virtual of DC machine? any recommendations and suggestions?

  Good, you need to be really scared at all. I'm here to help you!

  The situation you are in is a common scenario when you have a backup that uses the technology of snapshot for taking backup.

  Please follow the steps below and I assure you that you will have a virtual machine with no snapshots and running with all the current data on it.

  Step 1: right click on the VM, change the settings. --> Disk hard 1--> make a note of the location of the hard drive. Also, take note of the size of the hard drive.

  for example: VMdatastore/testvmfolder/testvm-000003.vmdk.

  Here, the disc is pointing the 3rd snapsot in the chain.

  Step 2: Turning off the virtual computer.

  Step 3: Enable SSH and connect to the host using PuTTY.

  Step 4: Navigate to the folder of the virtual machine where the drive (see step 1 for location)

  CD/vmfs/volumes/VMdatastore/testvmfolder

  Step 5: create a test folder in the directory of the virtual machine.

  # mkdir test

  Step 6: copy the .vmx file in the test folder.

  testvm.vmx CP test

  Step 7: Identify a data store that has a free space as the size of the hard drive found in step 1:

  Step 8: Clone the drive to this place, start by creating a folder in the destination data store and then run the command to create a clone of the disc below:

  vmkfstools-i testvm - 000003.vmdk/vmfs/volumes/destination folder/cloned_disk.vmdk data/new store

  This would strengthen all snapshots in a single cloned_disk.vmdk file at the destination.

  This would require a downtime of the virtual machine.

  If you wish, you can also use a converter to convert the virtual machine on the same host. This would create a clone of the virtual machine.

  Make sure that it is not on the network

  Hope this is informative.

  See you soon,.

  Nitin

• Keep the session with Esx/Vcenter throughout the backup

  Hello

  When I trigger a backup of drive on a virtual machine, I have the following algorithm.

  1. log in to the host.

  2 take a snapshot of the virtual machine.

  3. for each disk in the virtual machine, the request for the block changed.

  4. take the backup of the disk.

  5. Repeat steps 3 and 4 for the entire disc.

  6. store the virtual machine configuration.

  7 remove the snapshot.

  8 disconnection.

  When I tested my code with a very large drive which took place for a 8hrs say for a diskbackup complete, when I get to step 6, the session appears to have expired. With the exception of the removal of the snapshot, I think I can work around the problem - since the snapshot is an object of the session, just confused how this can be managed. Is there a way to keep the session until I finish the backup - as it seems more natural to keep the session so that all operations are completed instead of trying to work around. Let me know your opinion.

  Thank you

  . / Siva.

  Hello Shiva!

  I couldn't find a way to get the object of snapshot based on the name. One of the recommended steps to do before taking a snapshot is to delete all the snapshots with the name that you use to take the snapshot - which are essentially snapshots of the backup failed. The virtual computer object provides a way that to remove all snapshots - which of course is false, but does not rely on the name of the snapshot. Any ideas on that?

  Sorry to be not been clear enough, I'll try one another: how to find a snapshot by name?

  I agree with you that it is not obvious at first glance. In my opinion the VirtualMachine managed object provides a property named 'snapshot '. This property is an instance of data object VirtualMachineSnapshotInfo. There is a property named "rootSnapshotList". This property is an array of data objects VirtualMachineSnapshotTree . And now comes the crucial point to the routine:

  To me, it seems that the hierarchy entire snapshot is represented by instances of VirtualMachineSnapshotTree of objects where each of them finally points to the successful VirtualMachineSnapshot Explorer they represent in fact. The tree object provides data in read-only snapshot represented, i.e. name, description, etc.

  In short:

  1. Download the roots of instant trees via VM.snapshot.rootSnapshotList
  2. Recursively browse through [VirtualMachineSnapshotTree.childSnapshotList]
  3. Identify your snapshot via VirtualMachineSnapshotTree.name
  4. Access to the managed VirtualMachineSnapshot object via VirtualMachineSnapshotTree.snapshot
  5. Remove the snapshot via the method RemoveSnapshot_Task

  I guess that should work :-)

• What is the use of snapshots of consolidation?

  I've read up, but I'm still not really what is the usefulness of this feature.

  Please can someone enlighten me?

  Also please correct if my train of thoughs is wrong:

  i. instant aren't really backups

  II. the Snapshots are supposed to be taken so that the virtual machine can be recovered at this point in time (for example, before the Windows Update)

  III. snapshots are "integrated" with dare the virtual machine (via VMware Tools), which means that we can make the Brownie when virtual machines are on the rise.

  -Windows 2008?

  -Microsoft SQL?

  IV. Snapshots would take place outside the VMs

  -The data store should be much larger then the VMS (for example if the virtual machine is 200 GB, datastore shd be 300 GB to VMDK + Snapshots)

  -Snapshot sizes would grow as time passes (eg. instant 100 days ago risked increasing from 10 GB to 20 GB according to the changes made to the virtual machine)

  v. recommendations (by VM)

  -Do not to keep snapshots to extend the periods of time

  -Do not keep too many clichés

  -"consolidate" snapshots

  So, what is the difference between "Consolidate" and "Delete All"?

  I think you may have the wrong idea of the snapshot...

  I would like to use Windows update + service pack installation for example.

  VM with MS svr 2003 running... you can install SP1, and then test, can install updates to Windows, and then test.

  -snapshot 1 (sn1): Win2003 Updates & SP

  -Install of Win2003 SP1 (with reboot etc.)

  -snapshot 2 (sn2): Win 2003 SP1

  -Install Windows updates current on Win2003 SP1

  -snapshot 3 (sn3): Win 2003 SP1 with updates

  -svr stable for 5 days (eg. installing Acrobat reader, Microsoft office)

  So u shd have 3 pictures... who all "grows" that you test your DVS.

  But your VM will be 4 types of main file (with respect to this context)

  1. basis of files of the virtual machine (vmdk, vmx, memory of the computer virtual, swp files etc.)

  2 VM snapshot file

  3 VM snapshot files swp (swap is maybe not correct name... but I do think that the proper name)

  In terms of logic...

  -'sn1' is the basis of the snapshot

  -"sn2" is "sn1" + "data1."

  -"sn3" is "sn1" + "data1" + data2.

  "- VM1 is sn1' + 'data1' + data2 ' + data unnamed swap

  The 5th day of test, the virtual machine will have files for

  ' '- sn1', "sn2", "sn3", 'data1', 'base VM,' data2 ' and unnamed swap data that are generated during the 5 days of tests.

  Then from the right 'consolidation' will convert the name in "data3" swap so that

  -'sn1' is the snapshot of base + 'data3 '.

  -"sn2' is 'sn1' + 'data1', 'data3 '.

  -"sn3" is 'sn1' + 'data1' data2' + 'data3 '.

  "- VM1 is sn1' + 'data1' + data2 ' + 'data3 '.

  In a way layman... Virtual machines with snapshot are VMs who have ΘtΘ divisΘs into multiple files.

  "" When you remove stereotypes (please do not try everything remove), what you do is merge sn1 "+"data1"+ data2 ' + data not named swap or 'data3' in a virtual machine.

  Sorry... I forgot to add... Please do not receive or keep snapshots VMware for long periods of time.

  The snapshots are not backup. They can line up while you have yourself photographed... soon...

• Snapshot TIME?

  Are there features of snapshot for vApps in vCloud Director?  What happens if I wanted to test something with a group of virtual machines or a single VM in a vApp, go back, and I had no access to the vSphere Client?  Is there a similar functionality as that of snapshots in vSphere?

  Unfortunately not. I hope that it will be available in a future release. The only option and it's not great, I can think of is to make a hot clone via the use of the API. There is a guide to the conduct of this orchestrator which should point you in the right direction but this isn't really a snapshot than a backup http://www.vcoteam.info/learn-vco/vcloud-director-vapp-hot-clone.html.

• How to take snapshots on a global scale

  We use virtual disks supplied thickness in VMware but use thin volumes put into service on our SAN (known as thin thickness).

  We back up our virtual machines using Backup Exec, which creates a snapshot for VMware backup of the snapshot and then removes it.

  When if failed backups can leave the snapshot behind which uses more disk space on the SAN until we notice and delete it.

  Thin provisioned SAN volumes cannot grow, not shrink, then the extra space that has been used so that grew the snapshot is now wasted in the SAN.

  It is therefore an easy way to monitor snapshots without entering the Snapshot Manager for each virtual machine, just a place that would be would be list of all pictures in our cluster.

  Any ideas?

  Thank you

  You can create an alarm in the VC, there is a default a VM Snapshot size available (GB) who customize to the size warnings and the alert message.

  Or use powercli to run a script every day to send a list or instant operation, there are a few scripts autour already that you can use (Chris Uys made one).

  Mark

• backups system state backups vs vm

  Hello

  There are a lot of practical documentation on system state backups, but what's the point of system state backups, if you are running backups of virtual machine using the vstorage api.  I know that for the AD, a backup of the system state is better that one vm, backup, but other than that, has no useless system state backup is a backup of virtual machine (I was going to say redundant).

  I am trying to develop a strategy for which use.  My preference is to make backups of VMS (no file level) and use sparingly system state backups.  Do both adds to planning of backup with more, that there is less tolerance for a backup window and more an expectation of off-host backups.

  falcone1

  DSTAVERT wrote:

  For a domain controller you need to make backups of system state. Without them, you may lose AD. According to the recommendations of Microsoft at least twice a day.

  This isn't a very good statement. As always, 'it depends' - depends on your image-level backup solution. With Veeam, you have not had do this - unless you want to have redundancy on the backup of the same data twice.

  However, with the image at the level of backup solutions which are not multi-application and do not treat virtual computers running some applications in a special way on the backup and restore, you certainly to do that. Otherwise, in case of DC for example, you will end up with a USN restoration on the restoration, and it will screw up your ad.

  In addition, just to cover some other points above:

  If you try to restore a DC from backup of image based (i.e. a backup to the current no AD) in a multi domain controller environment, you will almost certainly encounter problems of replication synchronization after restoring as the AD database was restored in a way not supported.

  That's right, unless you use the image-level such as Veeam backup solution, which performs backups multi-application and – most importantly – multi-application restorations.

  Also, image based backups not serve to an Exchange Server transaction logs, so it will continue to grow until a backup of the information store.

  It is also an accurate statement of many image-level backup solutions. Most of them do not at all cut the Exchange transaction logs. Some will be plum them immediately to the creation of the snapshot (before the backup is completed successfully) - which is actually worse than not not their pruning at all - because you find yourself without reliable backup and logs are gone too. And only a few image-level backup solutions (for example, Veeam) will do it properly, pruning Exchange connects after successful only backup.

  I would definitely test any solution backup abundantly in the test environment with applications, before making decisions on the backup strategy. There are too many marketing of nowadays. Many image-level backup providers tend to make a big deal of features without importance and features of the product, while being silent to not have more basic, core features that are expected of any backup solution - as above - correctly handles backup and restore applications.

  I hope this helps. Warning, I work for Veeam.

• Snapshot LUN

  Buenas,
  conoce a what is refiere el concepto ¿alguien LUN snapshot?

  Gracias.

  Hola, segun tengo understood son LUN that son una "foto" otra LUN, unalterable there generally is obtienen por medio snapshot mechanisms o backup of some cajas/cabinas of disco.

  VMware reconoce estas LUN como lo son, UN, no permite write instant sober las premium y por lo as recuerdo con some cabinas IBM habia as hacer UN will del volumen of datos para poder each.

  No soy UN expert in el tema pero todo lo puedo than escucho.

  Saludos,

  Nicolas