I have the same issue, we have about 1GB of database to be backed up. It tool 3 days for the backup tool to run the backup over the WAN link to the server in west coast. Once the backup got complete, and I checked the folder size, all files were not there and the folder was half in size of the origional on the east coast server.
What are the best practices in this type of situation.
what files were missing? Some are excluded by default, they are runtime and not needed in your backup (FDB files for example, namesx.dat..).
Change log following backups are the fastest for incremental use, but if your WAN is slow, then it will be slow regardless - there's no magic. I would replicate onsite, then offload over the WAN using some other less critical measure.
I am just copying the SBDATA folder. Do I need to copy anything else? I am working right now to copy the folder on our SAN locally locally located on site in west coast and then will move from there to the server.
SAN storage? urgh. I hope it's tier1 for performance...
You only really need SBData, but if you back up the EEM directory as well, you'll have everything needed to restore without starting from the CD again - the database does not include things like connector settings.
Don't forget, when your helpful posts earn a kudos or get accepted as a solution you can unlock perks and badges. Those aren't the only badges, either. How many can you collect? Click here to learn more.
Community Help Hub
New to the forums or need help finding your way around the forums? There's a whole hub of community resources to help you.